Privacy Policy

This policy is issued by aSalesPartner LLC, a Wyoming limited liability company ("aSalesPartner", "we" or "us"). We supply, train, monitor and coach sales representatives who sell as part of our clients' teams, and we run a workspace application for that work.

This policy covers two groups of people: visitors to this public website, and users of the workspace, including anyone whose organization connects a Google account to it.

When a client organization uses the workspace, it decides which records to enter and which outside services to connect, and we process those records on its behalf to provide the service. As our Terms of Service describe, we may also keep and use information entered into the workspace to operate and improve the service, including after an engagement ends. For information about visitors to this website, and about our own dealings with clients and prospective clients, aSalesPartner decides how the information is used.

Google access is never automatic. It begins only when an authorized user in a workspace explicitly connects a mailbox or a calendar, and each capability is a separate authorization with its own consent screen.

Connecting a company sending mailbox requests these scopes:

openid, email, profile

Confirms which Google Account is being connected, and proves its verified primary address, so the mailbox cannot be bound to the wrong account.

https://www.googleapis.com/auth/gmail.send

Sends approved messages from the connected mailbox. This scope grants no read access at all — it cannot open a message, list a mailbox, or read a profile.

Receiving replies is a second, separate authorization. It is requested only if the workspace additionally turns on inbound retrieval for that mailbox, and it goes through its own consent screen:

https://www.googleapis.com/auth/gmail.readonly

Reads received messages so replies to the workspace's own outbound email can be matched to the right conversation. Access is read-only: no message is modified, no label is changed, and nothing is marked as read.

Connecting a Google Calendar is a third, entirely separate authorization, using a different OAuth client. It requests openid, email and profile, plus:

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

Creates and updates only the meeting events the app itself owns.

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

Reads busy/free times to offer meeting slots that do not conflict.

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

Reads the calendar's own settings — its identifier, its time zone, and whether it can create Google Meet links.

The application refuses broader alternatives by design. A calendar grant containing https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/calendar.events, any Gmail scope, or https://mail.google.com/ is rejected rather than accepted, and Gmail and Calendar authorizations are never combined into one grant.

Separately, this website offers a "Sign in with Google" option for workspace accounts. That sign-in is handled by the Lovable Cloud authentication service and is used only to establish who you are; it grants no access to Gmail or Calendar.

Connecting a mailbox or calendar stores the connection itself. Retrieving messages stores message content. The two are listed separately below because they have very different sensitivity.

The mailbox connection record

The mailbox address, the address Google's own profile endpoint reported for it, the stable Google account identifier (the OIDC subject), the verified hosted domain, the exact scopes granted, the connection's state and health, and the connection, verification, last-used and revocation timestamps.

OAuth tokens

The refresh and access tokens are stored encrypted in a private database schema that the application's public API cannot reach. They are never returned to a browser, never written to a log, and never recorded in an audit entry.

The Gmail sync position

A cursor recording how far inbound retrieval has read, so the same messages are not fetched twice. It holds no message content.

Retrieved messages matched to a known contact

The subject, the message body text, the Message-ID and In-Reply-To headers, the Gmail thread identifier, the Gmail message identifier, a content fingerprint, and timestamps.

Retrieved messages that match nothing

Held as an unmatched record with the sender's address and display name, the subject, the body, and the message's headers, each header value truncated to 4,096 characters.

Attachments

Attachment content is never downloaded or stored. Only the file name, the declared media type, the size in bytes, and — where the file is an executable, an archive, or over 25 MB — the reason it was set aside for manual review.

Calendar connections and events

The calendar account's email address and account identifier, the calendar identifier, its time zone and granted capabilities; and for each meeting the app manages, a snapshot of the event: title, description, location, start and end times, status, conferencing details, and each attendee's email address, display name and response status.

Inbound retrieval reads only the mailbox's inbox, and excludes Chat, sent mail, drafts, trash and spam, along with the mailbox's own outgoing copies. It also reads only recent mail: each pass is limited to a window of between one and thirty days.

Within those limits, every message returned is retrieved and stored, including messages unrelated to the workspace's own sales conversations. A message that cannot be matched to a known contact is not discarded — it is kept as an unmatched record, with its body and headers, for a person to resolve.

Disconnecting a Google account does less than the word suggests, so it is worth stating precisely. When a mailbox is disconnected, three things happen: the stored OAuth tokens are permanently deleted from the database; the connection is marked revoked and disconnected, which stops all further sending and retrieval; and the refresh token is then revoked at Google. The database change is recorded first, so a failed or unauthorized disconnect never reaches Google at all.

Disconnecting does not delete anything that was already retrieved. Message subjects and bodies, headers, unmatched records and calendar event snapshots all remain in the workspace. The connection record itself also remains, marked revoked, still holding the mailbox address, the Google account identifier and the scopes that had been granted.

There is no automatic expiry for Google-derived message or calendar data. The application runs no scheduled job that deletes it after any period. It is retained until it is deleted on request.

Two other categories do have automatic schedules, and they are the only ones that do:

• Website contact-form submissions: after 180 days the name, email, message, user-agent and request identifiers are erased from the record; after 365 days the record is deleted outright.
• Call recordings and transcripts: deleted on a retention period each customer organization configures for itself, subject to any legal hold it has applied.

The workspace has no self-service deletion. To have your account or retrieved Google data deleted, send a request through the contact form or to contact@asalespartner.com. Our team carries out deletion requests.

aSalesPartner's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

aSalesPartner does not sell Google user data, does not use it for advertising, and does not use it to build advertising profiles.

No aSalesPartner employee reads Google user data except with the user's explicit permission for support, for a security investigation, or where the law requires it, and Google user data is never used to train AI models.

Google user data is shared onward in exactly one case, and it is a case worth reading carefully. When a workspace's AI data provider is set to Anthropic, two features send email text to Anthropic's API:

• Reply classification sends the new, unquoted portion of a received reply, so the reply can be categorised. If that portion is empty, nothing is sent and the reply is flagged for manual review instead.
• Conversation summarisation sends the subject and full body of up to fifty messages from a single contact's thread — both received and sent — to produce a summary of that conversation.

The application ships with its AI data provider set to a local mock, which makes no external request. The Anthropic path is only active once a workspace's data provider setting is switched to Anthropic.

Anthropic processes that content only to return the classification or summary. It is not sent for advertising, and it is not sold.

Google user data is not sent to Resend, Apollo, LiveKit, Telnyx or Deepgram. Outbound email from a connected mailbox is sent through Google only; Resend is used on a separate receiving path for a different address and never receives Gmail content; Apollo receives prospect research criteria only; and the voice providers handle telephone call audio, which is a separate part of the service.

The full list of external services the application sends data to, and what each one receives:

Google

Gmail and Google Calendar, for the mailbox and calendar a workspace connects. Receives the messages the workspace sends — including the inquiry acknowledgements and inquiry notices described under "This website" — and the calendar events it creates, and returns the received messages and calendar data described above.

Supabase

Hosts the PostgreSQL database and the private file storage. Holds everything the application stores, including retrieved message content and the encrypted OAuth tokens.

Lovable Cloud

Provisions and manages that Supabase project, and provides the authentication service behind workspace sign-in, including "Sign in with Google".

Cloudflare

Serves the application. Cloudflare Turnstile also runs on the public contact form; when you submit that form your browser sends Turnstile a challenge token and the request metadata that accompanies it.

Anthropic

Receives the text sent to AI features. As described above, that can include received reply text and the subjects and bodies of email in a contact's thread, but only when a workspace has set its AI data provider to Anthropic.

Apollo

Used for prospect research. Receives the search criteria a workspace supplies and, when enriching a specific record, Apollo's own identifier for that person. The application explicitly disables Apollo's personal-email and phone-number reveal options. It receives no Google data.

Resend

Used on the inbound path for email delivered to a Resend receiving address, where it supplies the message body. The outbound configuration is currently in dry-run and sends nothing. It receives no Gmail data.

LiveKit

Hosts the real-time audio rooms used for calls. Receives call audio and participant identifiers, and writes call recordings into the private Supabase storage bucket.

Telnyx

Carries calls over the telephone network. Receives the calling and dialled phone numbers, call control events, and the call audio.

Deepgram

Produces live call transcripts. Receives the call audio streamed to it during a transcribed call.

Several of these are only reached when the relevant capability is configured and authorized. A feature appearing in the application is not the same as a provider being connected and active.

These companies may process information in the United States and in other countries. Each receives only what it needs to provide its service to us.

Beyond anything Google-derived, a workspace stores the records its authorized users enter or generate: company and lead details, contacts, tasks, meetings, messages, pipeline activity, approvals, and the audit evidence needed to show who did what.

Where the calling features are used, it also stores call records, recordings and transcripts, under the retention period the customer organization sets.

This information is used to operate and secure the service, to keep audit, reliability and abuse-prevention records, and to run the actions a workspace has explicitly set up. It is not sold.

We may also keep and use information entered into the workspace to operate and improve the service, including after an engagement ends, as our Terms of Service describe. This does not apply to information received from Google APIs, which is used only as described in the Google sections above.

A sales inquiry submitted here can include your name, work email, company, the inquiry type you chose, your current team size, your sales setup, your primary challenge, any optional context you add, your browser's user-agent string, and a hashed form of your request address used for abuse controls.

When you submit an inquiry, we send an automatic acknowledgement to the email address you gave, and we send a copy of your inquiry to our team by email. Both messages are sent through Google from our own company mailbox. We use your inquiry to reply to you, to follow up about the service you asked about, and to prevent abuse of the form.

Please do not submit passwords, provider credentials, personal customer data, or other sensitive information through the public form. An inquiry expresses interest in a conversation; it does not create an account, an engagement, or a provider connection.

Submissions are retained as described above: personal fields erased after 180 days, the record deleted after 365 days.

The records our workspace keeps of those two outgoing emails are erased once they are 180 days old. The emails themselves are ordinary email messages and remain in the mailboxes that sent and received them. If a receiving mailbox is connected to the workspace for retrieving replies, its copy is handled like other retrieved mail, as described under "Google data: retention, and what disconnecting does".

This website loads no analytics or advertising trackers. The only third-party code on it is Cloudflare Turnstile on the contact form, which is there to stop automated abuse. If that changes, we will update this policy before the change takes effect.

• OAuth tokens are encrypted with AES-256-GCM before they are stored, and each encrypted value is cryptographically bound to the specific connection and field it belongs to, so a stored value copied to another record fails to decrypt.
• Tokens live in a private database schema reachable only by the server, through restricted functions. They never appear in a browser response, a log line, or an audit record.
• The connect flow uses OAuth with PKCE and a nonce-bound identity token whose signature, issuer, audience, expiry, subject and verified-email claim are all checked, and the mailbox's own Gmail profile address must match what was authorized.
• Access inside a workspace is confined by company and role, enforced in the database itself with row-level security rather than in the interface alone.
• Disconnecting records the revocation in the database before contacting Google, so an unauthorized attempt cannot produce any effect on your Google account.

No system is perfectly secure, and this policy does not promise that one is.

You can disconnect a connected Google account from within the workspace at any time. Doing so deletes the stored tokens, stops all sending and retrieval, and revokes the app's access at Google.

You can also revoke aSalesPartner's access directly from your Google Account's security settings, under the third-party access section. Revoking there stops the app from reaching your Google data even if it still holds a token.

As explained above, neither action deletes data that was already retrieved. To have that deleted, you need to ask.

Depending on where you live, you may have the right to ask for access to the personal information we hold about you, to correct it, to delete it, to receive a copy of it, or to object to or restrict how we use it. We will not treat you differently for making a request. We may need to confirm your identity before we act on it.

If we hold your information on behalf of a client organization, we will pass your request to that organization and help it respond. You may also complain to the data protection authority where you live.

Send a deletion request, any other request about your information, or any question about how it is handled, through the contact form or to contact@asalespartner.com. Please do not include passwords or sensitive customer information in the message.

The service is for people aged 18 or older. It is not directed to children, and we do not knowingly collect information from anyone under 18.

If what the application does with Google data changes — a new scope, a new recipient, a new retention rule — this policy is updated before the change is enabled, and the date below changes with it. We update this policy in the same way for any other material change to how we handle personal information.