A connection built around control.

Clear permissions, your choice of AI provider, and a straightforward way out.

Your password stays with Google

Authentication uses Google OAuth. The server verifies a single-use state value bound to your browser and uses PKCE for the authorization code exchange. Google credentials never appear in browser responses.

Tokens stay on the server

Google tokens, provider API keys and the latest brief are encrypted at rest with AES-256-GCM. Your browser receives an opaque, HttpOnly session cookie. Cookies use SameSite protections and Secure transport on HTTPS deployments. State-changing requests must come from this application's origin.

Email is treated as untrusted content

Messages are displayed as plain text. The app does not render email HTML, execute scripts, load tracking pixels, or fetch attachments. AI is instructed to treat message content as data and has no tools to send email or act on instructions in a message.

The smallest scope that supports these features

Gmail modify access supports message viewing, statistics, optional AI briefs and user-requested read-status changes, archiving and moving to Trash. Metadata-only access cannot provide message text; read-only access cannot support message changes. The server allows only these message-management operations and exposes no sending, permanent deletion, account delegation or Gmail settings operations.

Your provider, with separate consent

AI runs through the OpenAI, OpenRouter or custom endpoint you configure. Email excerpts leave this service only after you authorize AI processing. Saved provider keys are never returned to the browser. Custom endpoints must use public HTTPS addresses; internal addresses and redirects are blocked. You can disable AI, remove the saved key and delete the brief without disconnecting Gmail.

Revocation and incident reports

Disconnect in Settings to request token revocation and delete local account data. You can also revoke access in Google Account connections. To report a suspected vulnerability, contact [email protected] and avoid including actual email content or tokens in your report.

These are implementation safeguards, not a certification. We do not claim Google verification or a completed third-party security assessment.