Privacy notice

1. Data accessed and why

The integration uses Google OAuth, not a Gmail password supplied to this website. It can access account identity, message identifiers, senders and recipients, subjects, dates, labels and selected message bodies. Its granted Gmail permissions support reading, sending and modifying mail, as well as Gmail settings. These capabilities serve the owner’s requested mail tasks; they are not all exercised by scheduled reviews.

Scheduled monitoring reads selected messages to summarize important changes and identify actions. It does not send mail, delete messages, change settings or mark messages read. Sending and other mailbox changes require a specific owner instruction. Credential and security-code messages are excluded from routine body review. Attachments are not downloaded by routine monitoring; handling them requires a relevant owner request.

2. AI processing and message delivery

Selected mail text and related prompts are provided to the configured AI provider to produce the requested summaries, classifications or drafts. The current mail-review model uses OpenAI. Processing is therefore not wholly on-device. Provider-side handling and retention depend on that service’s terms and the owner’s account settings; this notice does not promise zero provider retention.

Notices containing relevant mail facts or excerpts may be delivered to the owner through Telegram and retained in private assistant conversation history. When the owner authorizes sending an email, Google processes that message and delivers it to the specified recipients.

The integration does not sell mailbox data or use it for advertising. Its purpose is the owner’s requested mail assistance. Any use of Google data must follow the Google API Services User Data Policy, including Limited Use. This description is not a claim of Google certification or of independently audited provider settings.

3. Storage and access

OAuth secrets are stored in the operating system’s protected credential service on the owner’s host. Mail identifiers, subjects, relevant facts, deduplication records and prepared drafts may be stored in the private workspace and mail-monitor database. Selected tool results and excerpts can also remain in private execution or conversation logs. Routine monitoring is not intended to create a full-mailbox archive.

Access is limited by the owner’s host, assistant and connected-account controls. A separate agent name is not an operating-system security boundary. The public website has no access to the credential store, private workspace or mailbox.

4. Retention, revocation and removal

Operational records and conversation history remain until removed under the owner’s local or service retention controls; this integration does not enforce a fixed automatic deletion deadline. The owner can stop the mail monitors and revoke the connection in Google Account connections.

Revoking access prevents future API access but does not erase previously saved summaries, drafts, local records, backups or messages already delivered. Those copies must be removed from their respective stores. The operator can be contacted at the address below for questions or removal requests concerning data in this integration.

5. This informational website

The site contains static pages. It has no signup form, application cookies, analytics scripts or embedded mailbox content. Hosting is intended to use Cloudflare Pages. Cloudflare may process ordinary connection information, such as IP addresses and request logs, to deliver and protect the site under its privacy policy. Visiting a link to Google or another provider is subject to that provider’s terms.

6. Changes and contact

This notice will be updated when the integration’s data practices change. Questions: [email protected].