A connection built around control.

Clear permissions, private processing, 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 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 allows both inbox reading and the read/unread/archive features. The app exposes no sending, permanent deletion, account delegation or Gmail settings operations. You choose each label change.

Private AI, with separate consent

AI runs on the operator's private self-hosted service. Email does not go to an external AI API. You can disable processing and delete the saved brief without disconnecting the inbox.

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.