Personal Gmail Reader

Privacy policy

Last updated: October 27, 2026

Operator and purpose

Personal Gmail Reader is a personal productivity application operated by the owner of app92.net for the owner and explicitly invited account holders. Its purpose is to search and summarize email for user-requested tasks, including locating booking confirmations and receipts. It is not a public email service.

Google data accessed

Each account holder authorizes their own account through Google OAuth. The intended Gmail permission is https://www.googleapis.com/auth/gmail.readonly. When authorized, this allows access to mailbox information, message headers, senders and recipients, subjects, message bodies, and attachments. The permission is mailbox-wide; it does not technically restrict access to booking emails or a specific folder.

The application uses searches and selected messages relevant to the requested task rather than continuously copying the entire mailbox. Gmail read-only access does not permit sending messages or changing mailbox contents, labels, or read status.

How data is used and shared

Relevant email content is used to answer the account holder's requests and produce requested outputs, such as a travel plan. For AI-assisted tasks, selected message content may be transmitted to GitHub Copilot and its configured model providers. Those services process that content under the terms and data controls applicable to the user's account. Do not assume that using a local Gmail client keeps all message content local.

The application does not sell Google user data, use it for advertising, or build general-purpose AI training datasets. Access and transfers of Google user data are limited to providing the requested user-facing functionality, with any other disclosure limited to the account holder's authorization, security needs, or legal requirements as permitted by Google's policies.

The operator, authorized account holders, and AI services involved in a requested task may have access to the selected content. Only information needed for that task should be included in generated documents. Publishing or sharing a generated document requires separate care because recipients may then receive its contents.

Storage and security

The Gmail client runs on the owner's Windows computer. In the intended OAuth configuration, each account has separate encrypted credentials, with the encryption key protected by the operating-system keyring. Passwords are not required by the Gmail API, and credentials must not be stored in this public site or source control. Local encryption does not protect against a compromised process running as the same Windows user.

This public information site has no mailbox connection, sign-in form, advertising, or application analytics. Its hosting provider, Cloudflare, may process ordinary request metadata such as IP addresses and browser information to deliver and secure the site. See Cloudflare's privacy policy.

Retention and deletion

OAuth credentials are retained locally until access is disconnected or the credentials are removed. Selected email excerpts, downloads, conversation history, and requested outputs may persist in local files or the AI service's conversation history. There is no automatic deletion deadline for those outputs; they must be managed separately under the applicable service controls.

Account holders may request removal of local credentials and locally retained email-derived material by contacting the operator. Deleting local files does not automatically delete AI conversation history, already shared documents, or backups. Those copies require separate deletion through the relevant service or recipient.

Your control and revoking access

You may revoke the application's Google access at any time using Google Account connections. Revocation prevents further authorized API access but does not erase previously created outputs. Each account's consent and revocation are independent.

Contact and changes

For support, access removal, deletion requests, or questions about this policy, email jindaniaarif@gmail.com. Do not include passwords, verification codes, or tokens. Changes to this policy will be published here with an updated date.