Multi Gmail

DATA & PERMISSIONS

Privacy policy

How Multi Gmail handles your Google account and Gmail information.

Last updated: 2 November 2026

Who operates the app

Multi Gmail is a personal Gmail connector operated by Up. For privacy questions or a request to delete the connector’s stored information, contact sevenuphome@gmail.com.

Information the app accesses

With your permission, Multi Gmail accesses your Gmail account address, message headers and bodies, conversations, drafts, and attachments to fulfill requests you make in ChatGPT or Codex. The requested Google permissions are gmail.readonly and gmail.compose, with offline access so the connection can renew without repeated sign-in.

Google’s compose permission includes sending. Multi Gmail’s tools are limited to reading email and creating or updating drafts; they do not send, delete, archive, or label messages.

How information is used and shared

Google account and Gmail information is used to connect the account, retrieve the messages or attachments you request, and save drafts in Gmail. Requested content is returned to the ChatGPT or Codex conversation that calls the connector. Downloading an attachment returns that file to the signed-in user.

Google provides the Gmail and authorization services. The connector runs on OpenAI Sites using Cloudflare infrastructure. These providers process information needed to deliver their services. Content returned to ChatGPT or Codex is also subject to your account settings and those services’ policies.

Multi Gmail does not sell Google user data or use it for advertising. Multi Gmail’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Information stored by the connector

The connector stores your Site user identifier, your configured Google OAuth client ID and encrypted client secret, each connected Gmail address, an encrypted refresh token, and the connection date. Temporary sign-in records contain a hashed authorization state and an encrypted proof-key verifier and expire after ten minutes.

Email bodies and attachment contents are fetched when requested rather than saved in the connector’s database. The app does not intentionally log email bodies or authorization tokens. Hosting providers may retain operational logs or backups under their own service policies.

Security and cookies

Stored OAuth secrets and refresh tokens are encrypted with AES-256-GCM. Data access is scoped to the signed-in Site user. Google authorization uses a short-lived secure, HTTP-only cookie, a single-use state, and a proof key. OpenAI Sites also manages the sign-in session. No security measure eliminates every risk.

Retention, disconnection, and deletion

Mailbox connection records remain until you disconnect that mailbox or request deletion. Disconnecting removes its stored account record and refresh token from the connector’s active database. It does not revoke Google’s authorization, delete saved drafts or email in Gmail, or erase content already returned to a ChatGPT or Codex conversation.

To revoke Google access, visit Google Account connections. To request removal of your stored OAuth app configuration or other connector records, contact the developer. Manage Gmail drafts in Gmail and conversation retention using the controls in ChatGPT or Codex. Provider logs and backups may follow separate retention schedules.

Changes to this policy

This page will be updated if the connector’s data practices change. The date above identifies the latest revision.