Reason Gmail

Data handling

Privacy policy

Updated 18 November 2026

This policy describes the personal local Gmail connector named Reason Gmail and these documentation pages.

Information accessed

With the owner's Google authorization, the connector can access requested Gmail messages and threads, including their contents and headers, labels, and drafts. It can create drafts, send messages or drafts, and add or remove labels through the available tools.

Purpose and permissions

Google user data is used to perform the requested Gmail operations and return their results to Reason. The Google permission is gmail.modify. The connector does not expose every action allowed by that permission, and has no permanent email deletion tool.

Data use follows the Google API Services User Data Policy and its Limited Use requirements. The connector does not sell Google user data, use it for advertising, or independently train AI models with it.

Where data goes

The connector sends authenticated requests directly to Google's Gmail API. Requested results are returned to the local Reason application. Reason may include these results in conversations and send relevant content to the AI providers configured in Reason. Those providers' handling and retention depend on the owner's Reason configuration and the applicable service terms.

This documentation website does not receive OAuth credentials, mailbox data or connector tool results. Hosting infrastructure may record ordinary website access logs, such as request times and network addresses. The pages do not run application analytics or set application cookies.

Local storage and retention

The Google OAuth client credentials and refresh tokens are stored in private local application files accessible to the operating-system account running the connector. Tokens are retained to keep the owner's authorized connection working.

The connector does not maintain a separate email archive. Reason may retain tool results or email content in its conversations. Removing the connector's credential files does not remove copies already retained by Reason or its configured providers.

Revoking access and deletion

The owner can revoke access through Google Account connections, remove the Gmail connection from Reason, and delete the local connector's credential files. Conversation records must be managed separately through Reason's controls.

Scope and contact

This is a personal integration for its owner, with no public signup. For questions about this connector, use the operator's support email shown on Google's authorization screen. This policy should be updated if the connector's features or data handling change.