Privacy policy

1. Operator and purpose

The integration is operated by the owner of the connected Google account for personal email assistance. It uses Hermes Agent and a local gogcli connector to search, read, summarize, and answer owner-requested questions about email. It is not a public, multi-user email service.

2. Google data accessed

The Gmail permission is https://www.googleapis.com/auth/gmail.readonly. Depending on the owner’s request, the connector may retrieve email bodies, snippets, subjects, senders, recipients, dates, labels, thread information, and other message metadata returned by Gmail. This read permission can include sensitive messages; it is not restricted to a particular label or sender by Google.

Basic Google identity permissions identify the account authorizing the connection. This Gmail connection does not request permission to send messages, create drafts, change labels or read status, archive, trash, or delete mail. These limits apply to this connector, not to unrelated browser sessions or other tools separately configured in Hermes.

3. How email data is used and shared

Email data is used to carry out the owner’s requested, visible email-reading and assistance tasks. Relevant content may be included in requests sent to configured AI providers. Depending on configuration, this can involve an API routing service and an underlying model provider.

That transfer is necessary for the requested AI-assisted feature and occurs under the owner’s configuration and authorization. The providers’ own privacy, security, and retention terms apply. A local connector does not mean that all email processing remains on the local device.

The integration does not sell Google user data or use it for advertising, profiling for advertising, lending, or credit decisions. It does not implement features for training or fine-tuning generalized AI models. Provider choices and data-use settings must remain consistent with the Limited Use commitments below; an unrelated provider’s data-use practices are not overridden by this policy.

4. Storage, security, and retention

The local connector uses macOS Keychain to store its OAuth client secret and refresh token. Any separately downloaded client file or backup remains the owner’s responsibility to protect. No Google credential is intentionally included in this public website or its deployment.

Retrieved mail and generated answers can be retained in Hermes conversation history, local logs, exports, or files the owner requests. There is no automatic zero-retention guarantee. The owner controls local history and file retention; external provider retention depends on the provider and account settings.

Read-only Gmail access prevents mailbox writes through this connection. It does not eliminate the risks of disclosing sensitive mail in AI requests, local history, exported files, or responses influenced by untrusted email content.

5. This website and its hosting

Vercel hosts the public documentation pages. The pages contain no analytics scripts, advertising, forms, embedded third-party content, or application-managed cookies. They do not receive Gmail API responses or store email data.

The hosting provider may process routine request information, such as IP address, browser information, request time, and URL, to deliver and secure the site under its own policies. This is separate from the local Gmail integration.

6. Google API Limited Use

Hermes Gmail Read Only’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.

Google user data is limited to the disclosed, owner-authorized features. It is not sold or transferred to advertising platforms, data brokers, or information resellers, and is not used to train or improve generalized AI models. Any provider used to process Google user data must support these restrictions. Any human access beyond the account owner must have a permitted basis under that policy.

7. Revoking access and deleting retained data

The owner can revoke the application in Google Account settings at any time. Revocation prevents future Gmail requests under that grant; deleting a local token alone does not necessarily revoke Google’s grant.

Revoking access does not automatically remove previously fetched information from Hermes history, owner-created files, backups, or AI-provider records. Local retained copies can be managed by the owner using the relevant application or storage controls. Provider-held records are subject to that provider’s deletion and retention controls.

8. Contact and changes

For privacy questions or requests, contact the operator using the support email displayed on this application’s Google OAuth consent screen. As this is a personal installation, the connected account owner is also its operator.

This policy will be updated if the integration’s data practices change. New data uses or broader permissions require disclosure and the owner’s consent before they are enabled. Publishing this page does not mean Google has verified or endorsed the app.