Your information

Privacy policy

Effective date: October 12, 2026

1. Information accessed

With the owner’s Google authorization, Personal AI Assistant can access Gmail account information, message and thread identifiers, sender and recipient addresses, subjects, dates, labels, unread status, message bodies, and attachment metadata or selected attachment contents. OAuth access and refresh tokens enable the connection.

2. Purposes and actions

Information is used to find and explain email, summarize relevant details, retrieve supported attachments, and carry out the owner’s requests or authorized automations. Examples include order tracking, receipt processing for personal budgeting, and personal reports.

The Gmail API connection requests gmail.modify so it can read email and remove the unread label from selected messages. Although Google grants broader capabilities with this scope, this integration does not expose sending, deleting messages, or arbitrary label changes. Simply reading a message does not change its read status.

3. AI processing and other services

Relevant message content and derived information may enter the locally run assistant’s conversation context and be processed by the AI model configured by the owner. Local models process that context on the owner’s computer. If a hosted model is configured, relevant context is transmitted to that provider to generate the requested response; that provider’s applicable data-handling and retention terms also apply. Local operation of the application does not mean that all processing is offline.

Owner-authorized workflows may transmit selected information to configured services, such as a personal budgeting service, an approved messaging destination, or the owner-only email report destination. Those services process the information under their own terms. The owner should review the active model and integrations before using sensitive email content.

Google account credentials and OAuth tokens are handled by the isolated Gmail service, not included in model-facing tool results, and are not published to this website.

4. Storage, retention, and deletion

OAuth tokens are kept in private local storage with restricted filesystem permissions. Email bodies are decoded in memory by the Gmail reader, but returned content can persist in the assistant’s conversation history, task results, or workflow records. Explicitly downloaded attachments are saved to private local attachment storage. Derived order and budgeting records may be retained for ongoing tracking and duplicate prevention.

There is no single automatic deletion period for all local records. Retention follows the owner’s configured cleanup settings and workflow needs; records without an applicable cleanup rule remain until deleted. The owner controls local deletion and backups. Data already sent to another service follows that service’s retention and deletion procedures.

5. Limits on use and disclosure

Google user data is used for the personal features described above, not sold, used for advertising, or supplied to data brokers. This integration does not use that data to train generalized AI models. Any configured hosted processing must be consistent with these limits.

Access by anyone other than the owner is not part of ordinary operation. Any additional disclosure must be limited to an owner-consented feature, a necessary security purpose, or a legal obligation.

Personal AI Assistant’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

6. Your controls

The owner can disable Gmail tools or automations, stop the local assistant, and revoke the connection through Google Account connections. Revocation stops future authorized access but does not erase information already saved locally or sent to another configured service. Delete those records separately if needed.

7. This website

This static website contains no account registration, Gmail authorization, contact form, analytics script, or advertising tracker. It does not receive email contents or OAuth tokens. Cloudflare, the intended hosting provider, may process ordinary request information such as IP addresses and browser details to deliver and secure the site, under its privacy policy.

8. Changes and contact

This policy will be updated when the integration’s data practices change. A materially new use of Google data requires the owner’s consent before that use begins.

This integration is operated solely for its owner. The support contact is supplied in the Google OAuth consent configuration; it is not published on this informational website.