Privacy
Your email data travels between your browser and Google. This tool has no email-processing backend.
What the tool accesses
With your permission, the tool reads Gmail conversations and attachments, changes labels, moves conversations to Trash, and sends replies you explicitly submit. Optional read-only Contacts access is used to match a sender’s address with an available photo.
Where the data lives
Email content, reply drafts, sender photos, queue state and Google access tokens are held in this tab’s memory. This application does not write them to cookies, local storage, a server database or application analytics. Reloading or closing the tab clears the application’s session; you must reconnect to use Gmail again. Your browser may retain network cache or history outside the application’s control.
Who receives data
Google receives authenticated Gmail and Contacts API requests. Google also receives sign-in requests through its Identity Services library. Sender photos load from Google’s photo servers. The hosting provider processes ordinary website requests and may maintain technical logs, account information and access controls under its own policies. This application does not send your emails or access tokens to the hosting provider or the site operator.
Email images and links
Embedded attachments are retrieved from Gmail. Remote images are blocked by default. If you choose Load images, the sender or image host may receive your IP address and a tracking signal. Opening links in an email can reveal information to the destination website. Referrer information is suppressed.
Your choices
Use Disconnect to clear this tab’s session. Use Revoke access to request revocation from Google, or remove the application in Google Account connections. Google’s existing mailbox records, sent mail and consent history remain subject to Google’s policies.
Risks and permissions
The Gmail permission is broad: Google authorizes reading, modifying and sending email, even though this interface limits actions to its visible controls. Site code and dependencies must be trusted to handle that access correctly. Browser processing reduces server exposure; it does not eliminate security or privacy risk. The tool has no advertising or third-party analytics code.
Launch status and contact
This is a preview. The operator’s identity, support contact, final domain and Google verification must be finalized before public Gmail access launches. These disclosures must be updated if the application’s data handling changes.