How Assisto Uses Google Data

Assisto offers six separate, optional, read-only Google Workspace connections:

• Gmail: find and read messages, threads, and attachments you ask Assisto to check.
• Google Drive: find and read business files and folders you ask Assisto to check.
• Google Calendar: find and read calendars and events for scheduling context.
• Google Docs: find and read document text relevant to your request.
• Google Sheets: find and read spreadsheet values relevant to your request.
• Google Contacts: find and read contact details relevant to your request.

The raw Google data accessed can include message bodies, headers and attachments; Drive file names, metadata and content; event details; document text; spreadsheet cell values; and contact details, but only for the service and request you choose. The Google email permission identifies the connected account; Assisto does not request unrelated profile fields. Assisto does not request permission to send email or create, edit, move, share, or delete Google content.

You choose a Google service and authorize Assisto's Google OAuth client through a connection flow operated by Composio as Assisto's connector processor. When you explicitly ask Assisto to check that service, Assisto performs a scoped read and uses the returned content to answer that request or prepare an internal draft for you.

Returned Google content is transient request context and is not added to Assisto's durable business memory. Assisto's generic connector-memory tool also rejects Google Workspace content. Structural audit records can retain the connector name, read-only tool name, status, and provider log identifier without the returned Google content. Answers or drafts created for you can remain in a provenance-tagged Assisto chat. During this read-only release, Assisto blocks Google-derived chat content from being converted into a durable customer, supplier, quote, invoice, task, note, document, or other business record.

Assisto does not build an aggregated or anonymized dataset from Google content. Content-free operational measures may count connector attempts, success or failure, service name, and read-only tool name to operate and secure the feature; they do not contain the returned message, file, event, document, sheet, or contact content.

Composio processes connection credentials and Google API calls as Assisto's connector provider. Where AI interpretation is required, the minimum relevant Google content is sent to Google Cloud Vertex AI for the current request. Assisto forces live Google connector results and provenance-tagged Google chat history to that Vertex AI route and fails closed if it is unavailable; changing the default model route cannot send that content directly to a non-Google AI provider.

Assisto does not sell Google user data, use it for advertising, or use it to train or improve general-purpose AI models. Human access is limited to what is necessary for security, legal obligations, or support that you explicitly request and consent to.

Raw or derived Google content is not transferred to advertisers, data brokers, lenders, or general-purpose AI training providers. Composio receives the minimum data needed to operate the authorized connection, and Google Cloud Vertex AI receives the minimum relevant content only when AI interpretation is needed for the user-facing request.

Google data is transmitted over HTTPS. OAuth access and refresh tokens are held by Composio and are not stored in Assisto's application database. Assisto applies tenant-scoped access controls, production security headers, content minimisation, and restricted operational access.

Connected-app content is separated from trusted application instructions, treated as untrusted evidence, checked for prompt-injection language, and cannot authorize an action. Live Google results and provenance-tagged Google chat history cannot fall back to a non-Google AI provider or create a durable business record.

• Google content returned for a live read is transient for the current request and is not retained as durable connector memory.
• Active connection state is retained while one or more app connections are in use. Assisto's current Disconnect all control is provider-wide. After you confirm it, Assisto revokes and removes every app connection owned by this Assisto account in Composio, including Google and non-Google apps, before removing local connector-account state, session state, and legacy Google connector-memory records. Assisto keeps only a content-free disconnected marker while the account exists.
• Answers or drafts produced from Google data remain in the provenance-tagged Assisto chat while your account is active, unless you delete that chat earlier. Deleting a tagged Google chat permanently removes its messages, conversation state, and correlated AI workflow records from Assisto's active database. The read-only release does not save them into separate business records.
• Content-free connector audit records may identify the service, read-only tool, request shape, outcome, and time, but do not contain returned Google content. They are retained while the account exists for security, abuse prevention, and reliability, and are removed in a verified Google-data erasure or full account-deletion process unless a specific legal obligation applies.
• Managed backup copies are isolated from normal product use and retained only for the configured production backup lifecycle. If a backup is restored, completed erasure requests are re-applied before the restored system returns to service.

To delete a Google-derived Assisto chat answer or request account deletion, email info@assistocrm.com from your account email and identify the connection or chat concerned. We verify identity and check for a narrow, documented legal or security hold before deletion. We respond without undue delay and within one calendar month. If the law permits an extension for a complex request, we will explain it within that first month.

A legal or security hold is an exception only for the minimum data and period required, with a recorded reason and review date. Where legally permitted, we tell you what cannot yet be erased. The verified support process can permanently delete an exact legacy chat even if it predates the current Google provenance marker.

• In Assisto, open Settings, find Connected apps, and select Disconnect all. Before sending the request, Assisto shows the app names currently known to be connected and warns that the action applies to the whole Composio gateway. If you confirm, Assisto asks Composio to revoke and remove every app connection owned by this Assisto account, including Google and non-Google apps, verifies that none remain, and then removes local connection state and any legacy Google connector-memory records. This control cannot disconnect only one app. Select Cancel to keep every connection.
• In your Google Account, open Security, then Third-party apps and services, select Assisto or the displayed connection provider, and remove access.
• You can also ask support to disconnect a connection and delete related Assisto chat answers.

Revoking Google access stops future API reads. It does not automatically delete an answer or draft already saved in an Assisto chat; use the deletion process above for that chat content.

Assisto's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

This page supplements the full Assisto Privacy Policy.