Multi Gmail Privacy Policy

After a user grants permission through Google OAuth, Multi Gmail may access the user's Gmail address, message identifiers, sender and recipient fields, subject lines, dates, snippets, selected message bodies, thread information, and attachment metadata. It may also create Gmail drafts at the user's direction.

The current tool does not download attachment contents. It requests the Google OAuth scopes gmail.readonly and gmail.compose so these owner-requested features can work.

Google user data is used only to provide the action requested by the authorized user, such as finding recent messages, reading a chosen message, summarizing whether a message needs attention, or preparing a draft.

Gmail data is not used for advertising, sold, rented, or shared with data brokers. Access is not used for surveillance, credit decisions, employment decisions, or building advertising profiles.

OAuth client credentials and account tokens are encrypted with Windows Data Protection API (DPAPI) for the current Windows user and stored locally on that user's computer. Multi Gmail does not maintain a separate cloud database of Gmail messages or message bodies.

Users should protect their Windows account and device. No system can guarantee absolute security, but access is limited to the permissions granted through Google and can be revoked at any time.

Multi Gmail runs locally as a Codex integration. When the user asks Codex to search or read Gmail, the requested results are returned to Codex and may be processed by OpenAI to answer that request. Draft content supplied by the user is also processed when Codex prepares the requested draft.

OpenAI's handling of that information is governed by the terms, privacy policy, controls, and retention settings that apply to the user's OpenAI or ChatGPT account. Multi Gmail does not independently retain a second copy of message content after returning the requested result.

Google user data is shared only as needed with Google to operate Gmail API requests and with OpenAI/Codex to process actions explicitly requested by the user. Data may also be disclosed when required by applicable law or to protect the security and integrity of the service.

Multi Gmail stores encrypted OAuth credentials locally until the account is removed or access is revoked. Message contents are fetched on demand and are not stored in a separate Multi Gmail message database.

A user can revoke the app in their Google Account security settings and can delete the local Multi Gmail account configuration from the computer. Revocation prevents future Gmail API access through that token.

Multi Gmail's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Privacy questions can be sent to contact@earnio.pro. Material changes to this policy will be posted on this page with a revised date.

Return to the Multi Gmail homepage.