Privacy policy

Data accessed and why

With your Google OAuth consent, the connector accesses your Gmail account profile, message identifiers, labels and the messages requested by your assistant. It requests gmail.readonly to read messages and settings, and gmail.compose to manage drafts and send messages. It processes recipients, subjects and message bodies supplied for authorized email tasks.

Processing and sharing

The backend communicates with Google to exchange tokens and execute Gmail API operations. Data returned by Gmail tools can enter the assistant's conversation history and be sent to the AI providers configured by the workspace operator, including a configured fallback provider. Provider handling is subject to that provider's terms and the operator's configuration. Review those providers before connecting sensitive mail.

This connector does not contain an advertising integration, a sale-of-mailbox-data feature or a model-training pipeline. That does not describe or override third-party providers' independent data practices.

Storage and security

OAuth tokens and temporary authorization state are encrypted in private persistent backend storage. A separate encrypted per-account write ledger stores request hashes and delivery receipts to prevent duplicate writes. Tokens are exchanged server-side; they are not published in this website or its repository.

Conversation history, tool results and operational backups are managed by the workspace operator. Encryption of tokens does not imply that all conversation content or every backup is encrypted. The current connector has no automatic retention or deletion schedule for conversation history.

Retention, deletion and revocation

You can revoke access in Google Account connections. Revocation prevents future authorized API access but does not automatically delete earlier conversation history, backups or stored delivery receipts. Contact [email protected] for storage information or a deletion request for this deployment. Do not send passwords, OAuth tokens or private message contents in that request.

Workspace access

The backend supports a default Gmail account and separately authorized named accounts per authenticated workspace. Other authorized users or bots of that workspace may use the connected mailbox tools. Account reconnection preserves the write ledger. This is not an isolated public multi-user mailbox service.

Changes and questions

Changes will be published on this page with an updated date. Contact [email protected] for questions. Publication of this policy is not Google verification of the application.