Privacy Policy
This policy describes the owner-operated Gmail integration used by Fan Kai. It also explains this static documentation website. The application is for its owner’s personal use and is not open for public registration.
Google data accessed and purpose
With the account owner’s OAuth authorization, the integration can read Gmail messages, senders, recipients, subjects, message identifiers, timestamps, labels and message bodies. It uses this data to identify important correspondence and deadlines, summarize messages, maintain review progress and prepare replies. The send permission is used only after the owner gives explicit confirmation for a message to be sent.
The current grant contains gmail.readonly and gmail.send. It does not grant Calendar, Drive, Contacts or mailbox-modification permissions. Routine checks do not mark messages as read, archive or delete messages. Attachments are not automatically downloaded as part of scheduled checks.
AI processing and Telegram delivery
Relevant message contents and metadata may be transmitted from the owner’s local Hermes runtime to its configured AI inference provider to produce summaries and draft replies. The runtime currently uses OpenAI for inference; this configuration may change at the owner’s direction. This is therefore not an entirely offline service.
Selected summaries, necessary message context and draft replies are delivered through Telegram to the owner’s designated private conversation. The AI provider and Telegram process that data under their own applicable terms and privacy policies. This application does not represent that their retention policies are identical to local storage policies.
Cloudflare Pages hosts only these public documentation pages. Email messages, OAuth tokens and private briefings are not intentionally published to this website or sent to Pages for storage.
Local storage, retention and security
OAuth client credentials and refresh tokens are stored on the owner’s computer in files restricted to the local OS user. These credential files are not encrypted by the application itself; device-level protection depends on the owner’s system configuration. The integration uses HTTPS for calls to Google, the AI service and Telegram.
Message excerpts, message identifiers, review checkpoints, reports and operational logs may be stored locally to support reliable checks and follow-up. Reports can also remain in the owner’s Telegram history and in the inference provider’s systems under their respective retention policies. Local records remain until the owner removes them or configures a retention policy; no fixed automatic deletion period is currently promised.
Limited Use and no advertising
Hermes Workspace’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
The operator does not sell Gmail data, use it for advertising or credit decisions, or intentionally use it to train or improve a generalized AI model. Google data is used only for the owner-requested email assistance described here. Necessary transfers to the configured inference service and Telegram support that user-facing function.
Your control and deletion
The owner can stop scheduled checks and revoke authorization in Google Account third-party connections. Revocation stops future authorized access but does not automatically delete previously created local files, Telegram messages or provider-held records. The owner can delete local credentials, review files and reports, delete Telegram messages, and use the relevant provider’s available data controls.
Website visitors
This static site has no forms, application tracking scripts or mailbox login flow. The site operator does not add analytics or advertising cookies. Cloudflare may process routine request information such as IP addresses and browser details to serve and protect the site under Cloudflare’s Privacy Policy.
Contact and changes
Contact Fan Kai at [email protected] for access, deletion or policy questions. This page will be updated when the application’s data practices change.