Privacy Policy

This policy explains what data AppConnect handles, why, how long it is kept, who it is shared with, and how to withdraw its access.

Applies to: AppConnect, at getappconnect.com, and the third-party account connections it makes on behalf of the workspaces that use it.
Last updated: 26 September 2026.

AppConnect connects several kinds of third-party account, and the providers are not interchangeable: each one exposes different data and each connection is described separately below. Section 3 covers Google user data in full, section 5 covers signing in with an existing account, section 6 covers the other providers, and section 7 covers importing records from another business system. Only some of these connections are available today, and the service overview states which.

1. Who operates AppConnect

AppConnect is operated by Velocity Automation Corp ("we", "us"). AppConnect is the integration service used by the business software platforms Velocity Automation Corp operates, and by the customer workspaces running on them.

Registered address: 1111B South Governors Ave, STE 40280, Dover, DE 19904, United States
Place of incorporation: a corporation incorporated under the laws of the State of Delaware, United States (Delaware file number 10358665)
Privacy contact: privacy@getappconnect.com

2. What AppConnect does

A user of a business software workspace connects an account they hold with a third-party provider to that workspace. AppConnect requests permission from that provider, holds the resulting authorisation, and uses it only for the job the connection was made for. Depending on the kind of account, that job is one of these and nothing else:

• Calendars — list the calendars on the account so the user can choose one; write appointments booked in the workspace to that calendar and update or remove them when they change; read the busy periods already on it so the workspace does not offer a time the user is committed to.
• Messaging and social channels — list the pages or channels the account controls so the user can choose which to use; publish the posts and replies the workspace is asked to send; receive the messages and comments people send to those channels so they can be answered in the workspace.
• Advertising accounts — read spend, performance and campaign status; change a campaign's status when the workspace is used to pause or resume it.
• Business records — read contacts, companies, deals, tasks and notes out of another business system so they can be imported into the workspace. This is read-only.
• Signing in — confirm the name and email address on an account so its holder can sign in to a workspace without a separate password. See section 5.

AppConnect acts only on what the user selected — the one calendar, the chosen page, the named advertising account — on the account they authorised. It is not a product of its own, stores nothing on its own behalf, and has no interest in the data beyond doing that job.

3. Google user data: what is accessed and why

When a user connects a Google account, AppConnect asks Google for the user's permission using the two OAuth scopes below. Google shows the user what is being requested before anything is granted.

• https://www.googleapis.com/auth/calendar.events

  Purpose: to create, update and remove calendar events that correspond to appointments booked in the user's workspace. This is the write access that makes a booking show up on the user's calendar, moves it when it is rescheduled, and removes it when it is cancelled.

• https://www.googleapis.com/auth/calendar.readonly

  Purpose: to list the calendars on the account so the user can choose which one to connect, and to read the busy and free periods on that calendar so that times the user is already booked for are not offered to anyone else.

What is stored from the connected calendar

For each event AppConnect reads from the connected calendar, it stores only what is needed to know that a time is taken:

• the event's identifier as issued by Google;
• the event's title;
• its start time and end time, and whether it is an all-day event;
• when it was last synchronised.

Event descriptions, attendee lists, locations, attachments, conferencing details and guest email addresses are not stored. For events AppConnect itself creates from a workspace appointment, it also keeps the identifier Google returns, so that the same event can later be updated or removed rather than duplicated.

To act on the user's behalf until they disconnect, AppConnect also stores the access token and refresh token Google issues for the connection, and the identifier of the calendar the user selected. Both tokens are encrypted before they are written, as described in section 8.

What is not requested

AppConnect does not request access to Gmail, Google Drive, Google Contacts, or any Google data outside the calendar scopes listed above.

Where a Google account is used to sign in to a workspace rather than to connect a calendar, the only permissions requested are openid, profile and email. Those permissions give no access to any calendar, and no token from a sign-in is stored. Section 5 describes exactly what is kept.

4. Google API Services User Data Policy and Limited Use

In practice that means:

• Data received from Google APIs is used only to provide and improve the user-facing features described in this policy — connecting a calendar, keeping appointments in sync, and not double-booking the user.
• Data received from Google APIs is not transferred to anyone else, except as needed to provide those features with the user's consent, for security purposes such as investigating abuse, to comply with applicable law, or as part of a merger, acquisition or sale of assets, in which case we would give notice before Google user data became subject to a different privacy policy.
• Humans do not read data received from Google APIs, except with the user's explicit agreement (for example when they ask us to look into a specific problem with their connection), where necessary for security purposes, where required by law, or where the data is aggregated and de-identified for internal operations.
• Data received from Google APIs is not used for advertising of any kind, and is not sold or transferred to data brokers, advertising platforms or information resellers.
• Google user data is not used to develop, improve or train non-personalized AI and/or ML models. We do not use Google Workspace APIs, or any data obtained through them, to develop, improve or train generalised or non-personalised artificial-intelligence or machine-learning models. AppConnect uses AI features in the wider product; Google user data is not sent to them, and is not used as training data of any kind.

The commitments in this section apply to Google user data however it reaches us — through a calendar connection or through a Google sign-in — and to every Google API scope AppConnect requests: https://www.googleapis.com/auth/calendar.events, https://www.googleapis.com/auth/calendar.readonly, openid, https://www.googleapis.com/auth/userinfo.email and https://www.googleapis.com/auth/userinfo.profile.

5. Signing in with an existing account

Instead of creating a password, a person can sign in to a workspace using an account they already hold. This is an identity check, not a connection: it happens once at sign-in, and it grants no access to a calendar, a page, an advertising account, a message or a record.

What is received: the email address on the account, the name on it, and the address of the account's profile picture.

What is kept: the name and email address are stored on the workspace account they identify, and the profile picture may be stored as that account's picture. The time of the sign-in and a count of sign-ins are recorded on the account, and the fact that this provider was used is written to the workspace's own audit record. If the account is new, a workspace is created for it.

What is not kept: no access token and no refresh token from a sign-in is stored anywhere. Once the identity has been confirmed, the workspace issues its own session and the provider's token is discarded. No friend list, contact list, connection list, page, post or any other data is requested or received.

6. Other providers: what is accessed and why

Each connection below is described by what it reads, what it writes, and what is kept. Availability is stated on the service overview rather than repeated here, so that one page can never disagree with the other.

Microsoft Outlook calendar Available as Beta

The permissions it requests are Calendars.ReadWrite (to list the calendars on the account, read the busy periods on the chosen one, and create, change, cancel and remove the events that correspond to workspace appointments), User.Read (to confirm which account was connected) and offline_access (so the connection keeps working without asking again). What it would store is the same short record described for Google in section 3 — the event's identifier, title, start and end — in the same place, with its tokens encrypted the same way.

Facebook Pages, Instagram and Meta Ads Available as Beta

Reads: the list of Facebook Pages, Instagram business accounts, advertising accounts and businesses the authorising person controls, with each one's name, identifier, follower count and picture, so the user can choose which to connect; the posts on a connected page or Instagram account together with the comments on them; the messages sent to a connected page or Instagram account; and for an advertising account, its currency, its campaigns and their status, and spend and performance figures.

Writes: posts and images the workspace is asked to publish to a connected page or Instagram account; replies to comments; replies to messages; and a change of status when a campaign is paused or resumed from the workspace.

Keeps: the identifier of the authorising Meta account, the permissions that were actually granted, the list of pages, Instagram accounts and advertising accounts that the grant covers, and one access token for the connection plus one for each connected page. Meta does not issue a refresh token for this kind of connection, so none is stored. Every token is encrypted before it is written. For each connected channel AppConnect keeps its identifier, name, username, picture and follower count, and for each post it published, the identifier and link the network returned, so it is not published twice.

Meta can also tell us directly to disconnect or to delete: AppConnect answers Meta's deauthorisation and data deletion callbacks, and a deletion request removes the connection records for that Meta account and returns a confirmation code.

WhatsApp Business Available as Beta

WhatsApp is not connected through AppConnect. Where a workspace sends and receives WhatsApp messages today, an administrator set that up by entering credentials from their own WhatsApp Business account directly into the workspace — there is no AppConnect consent screen involved, and this policy is not what governs it. The handling of those messages is covered by the privacy policy of the platform running that workspace, and by the administrator's own agreement with Meta.

Discord Available as Beta

Reads: the identifier, name and icon of the Discord server the authorising person chooses; the text channels and the roles on that server, so a channel and a role can be selected; and, when somebody uses one of the workspace's commands on that server, the command they used and their Discord user identifier and username.

Writes: messages to the chosen channel; direct messages to a server member; the addition or removal of a role on a member; and the list of commands the workspace offers on that server.

Keeps: the server's identifier, name and icon reference, the chosen channel and the address needed to post to it, the permissions that were granted, and the access and refresh tokens for the connection — all encrypted before they are written. Where a Discord user is matched to a contact in the workspace, AppConnect keeps the link between the two and when that person was first and last seen. A Discord user is matched to a contact only on an exact email address match, never on a username.

7. Importing records from another business system

A business moving to a new workspace can authorise AppConnect to read its records out of the system it is leaving, so its history arrives with it. This connection is read-only in the strictest sense: AppConnect never creates, changes or deletes anything in the system being imported from. It is a one-directional copy, run when the business asks for it.

Every one of these is a read permission, with one exception worth naming plainly: Salesforce does not publish a read-only equivalent, so its api scope is broader than what AppConnect uses. AppConnect issues only read requests against it.

Reads: contacts and leads; companies or accounts; deals or opportunities, and the pipeline stages they sit in; tasks; notes; the tags on records; and the definitions of the custom fields the business added, so those fields survive the move. Also read, deliberately, is each contact's marketing opt-out state — whether they had asked not to be emailed or called.

Keeps: the records themselves become the workspace's own contacts, companies, deals, tasks and notes, held under the workspace's privacy terms from then on. Alongside them AppConnect keeps a map from each record's identifier in the old system to the one in the workspace, so that running the import again updates rather than duplicates, and a log of any record that could not be imported and why. The authorisation itself — access token and refresh token, or the access token a business pasted in — is encrypted before it is written.

Opt-outs travel with the record. Somebody who had refused marketing in the old system arrives still refused. That refusal belongs to them, and an import is not an opportunity to reset it.

8. Storage, protection and retention

Where it is stored. Connection records — the authorisation tokens, the selected account and the data imported for that connection as described above — are stored in the database of the platform that runs the user's workspace, operated by Velocity Automation Corp.

Tokens are encrypted at rest. Every access token and refresh token AppConnect holds, for every provider described in this policy, is encrypted with AES-256-GCM before it is written to the database, and is decrypted only at the moment a request to that provider is made. This applies to calendar, messaging, advertising and record-import connections alike.

In transit. All communication with providers' APIs, and all traffic to this website and to the workspaces that use AppConnect, takes place over encrypted HTTPS/TLS connections.

Access. The production database is managed by Supabase and cannot be reached from the public internet without credentials. Those credentials are held by Velocity Automation Corp and are not issued to customers, nor to the organisations that administer workspaces. Supabase encrypts stored data at rest at the platform level. That is separate from, and additional to, the token encryption described above, which we apply ourselves before a token is written — so an authorisation token is not readable from the database contents alone.

Retention.

• Authorisation tokens are kept only while the connection exists. When a user disconnects an account, the connection record containing those tokens is deleted, or the tokens are erased from it.
• Busy times imported from a connected calendar are deleted at the same time as the connection, and an individual imported event is deleted when it disappears from the connected calendar.
• The identifiers of things AppConnect created at a provider — an event for an appointment, a published post — are kept for as long as the workspace keeps the record they belong to.
• Records imported from another business system are the workspace's own data once imported and are kept, or deleted, by the workspace under its own terms. Disconnecting the import does not delete them, because by then they are the business's records in its new home.
• Operational logs that may reference a connection or a sync attempt are retained only for as long as is reasonably necessary to operate and secure the service, investigate faults and meet legal obligations, and are then deleted. They are not used to build a profile of anyone, and are not shared for anyone else's purposes.

9. Who the data is shared with

Data obtained through AppConnect is not shared with third parties for their own purposes. It is handled by:

• the provider the account belongs to — Google, Microsoft, Meta, Discord, or the business system being imported from — as the source and, where the connection writes, the destination of the data, under that provider's own terms and privacy policy;
• the infrastructure providers that host the platform on which the user's workspace runs, which process the data only on our instructions in order to host it — Vercel (application hosting and this website), Supabase (the database in which connections and their authorisation tokens are stored) and Twilio SendGrid (delivery of email we send, including messages submitted through the support form);
• the organisation that administers the user's workspace, to the extent that the connection's results are visible to it — the appointments in the workspace, the messages in its shared inbox, the figures on its advertising reports, the records it imported. Connecting an account does not give that organisation access to the rest of that account.

We may also disclose data where we are legally required to, or where it is necessary to investigate abuse or protect the security of the service.

10. What we do not do with it

• We do not sell data obtained from a connected account, and we do not accept payment for access to it.
• We do not use it for advertising, ad targeting, retargeting, personalised advertising or interest-based advertising. Reading an advertising account's own results, for the business that owns it, is not advertising use.
• We do not use it to train, develop or improve artificial-intelligence or machine-learning models.
• We do not use it for credit assessment, lending or any decision about the user unrelated to the features described in this policy.
• We do not transfer it to data brokers or information resellers.
• We do not use one connection's access to reach anything another connection covers, and we do not read data a connection's stated purpose does not need.

11. How to revoke access

Access can be withdrawn at any time, from either side, without contacting us:

1. In the workspace. Open the settings where the account was connected and disconnect it. The stored authorisation is deleted, together with the data imported for that connection.
2. At the provider. Remove AppConnect's access in the provider's own account settings. For a Google account that is myaccount.google.com/permissions — select AppConnect and choose to remove its access, and Google immediately invalidates the authorisation so that AppConnect can no longer read or write to any calendar on that account. Every other provider named in this policy offers the same control in its own account or business settings.

Revoking access does not delete what the connection already did. Events placed on a calendar, posts that were published, messages that were sent and records that were imported are real things in the places they now exist. They can be removed there, in the ordinary way, by whoever controls that place.

12. How to have data deleted

Disconnecting, as described above, deletes the authorisation and the data AppConnect imported for that connection. If you want confirmation of deletion, or you want us to delete anything that may remain — for example a reference in a support record — email privacy@getappconnect.com from the address of the connected account and say what you want removed. We will confirm when it is done.

Where a provider offers its own data deletion request, we honour it through that route as well: a deletion request received from Meta, for example, deletes the connection records held for that Meta account and returns a confirmation code that can be used to check the outcome.

13. Other data this website handles

This website, getappconnect.com, is a set of static pages. It sets no cookies and runs no analytics or advertising scripts. Apart from the support form described below, it asks for no personal information. Our hosting provider records ordinary server request data such as IP address, timestamp and requested URL for the purpose of serving and protecting the site.

If you email the privacy address, we hold your message and your email address in order to answer it.

The support form

If you write to us through the support form, we collect what you type into it:

• Your name and email address — so we can answer you, and know who we are answering.
• Your company, if you choose to give it — it is optional, and the form says so.
• The topic you select and the message you write.
• The date and time of the submission, and the page it was sent from, recorded with the message so we can see the context of a request.

Why we may use it: your consent, given by ticking the box on the form. The box is not ticked for you, and the form does not send without it — a submission that arrives without consent is refused rather than delivered.

What we do with it: we read your message and reply to the address you gave. That is all. It is not added to a marketing list, not used to profile you, and not sold or shared for anyone else's purposes.

Who it passes through: the message is delivered to our own inbox by Twilio SendGrid, our email provider, acting on our instructions.

How long we keep it: for as long as is reasonably necessary to deal with what you wrote and to keep a record of the exchange, and then no longer. You can ask us to delete the correspondence at any time by writing to privacy@getappconnect.com.

We never ask for credentials. Nobody from AppConnect will ever ask you for a password, a one-time code or an API key — not by email, and not on that form. If you receive a message that does, it is not from us.

14. Your rights and how to reach us

Depending on where you live, you may have rights over personal data we hold about you — for example to ask for a copy of it, to have it corrected, or to have it deleted. You do not need to invoke a law to exercise the controls in sections 11 and 12; they are available to every user. For anything else, write to privacy@getappconnect.com and we will respond.

15. Children

AppConnect is a business tool. It is not directed to children, and we do not knowingly collect data from children.

16. Changes to this policy

If this policy changes, the updated version is published on this page with a new "last updated" date. If a change materially affects how data from a connected account is accessed, used, stored or shared, we will not apply it to data already collected without first giving notice to the affected users.

Velocity Automation Corp · privacy@getappconnect.com