Privacy policy

Who operates the integration

The integration is operated by the owner of this personal installation and this domain. It is independent of Google and Nous Research. For questions or requests concerning access, correction or deletion, use the user support email displayed on the integration's Google authorization screen.

Google information accessed

After the owner authorizes an account, the integration can access that Gmail account's email address, message identifiers, headers such as sender, recipient, subject and date, message snippets and message bodies. Google describes the requested gmail.readonly scope as viewing email messages and settings.

The installed reader uses mailbox identification, message search and message-reading endpoints. It does not implement attachment downloads, remote image loading, sending, Gmail draft creation, labeling, archiving, marking messages read or deletion. Read-only authorization does not limit access to a particular folder or label.

How information is used

Accessed email data is used to answer the owner's requests, including finding mail, summarizing messages, identifying deadlines and suggesting follow-ups. The integration does not sell email data or use it for advertising, credit assessment or data brokerage. It does not implement model training.

Email content is treated as external information to summarize, not as authorization to execute instructions contained in a message.

AI processing and service providers

Email text returned to Hermes becomes part of its working context and may be transmitted to the AI model provider configured by the owner to produce an answer. That provider processes the submitted content under its applicable terms, retention rules and account settings. Read-only Gmail permission restricts mailbox changes; it does not mean email content stays entirely on the owner's server.

Google provides Gmail and OAuth authorization. The owner's private server provider hosts the Hermes workspace and stored records. Cloudflare hosts these public information pages and provides their network delivery. The public pages do not read mail or receive OAuth tokens.

These pages contain no advertising or analytics scripts. Cloudflare may process ordinary website request information, such as IP addresses and request metadata, to deliver and protect the site.

Storage and retention

Google OAuth client credentials and refresh tokens are kept in restricted local files on the owner's setup computer and private Hermes server. They are not intentionally included in agent prompts or published on this site. The integration checks that the live Google grant contains exactly the read-only Gmail scope before using it.

The reader does not maintain a separate mailbox archive. However, email content returned during a request can be retained in Hermes sessions, Companion conversations, tasks or memory and in backups of those records. Visible Companion conversations and saved tasks generally remain until the owner removes them. Deleting a Companion conversation does not also delete its native Hermes session, memory entries or backup copies.

Removal from live records and expiry or deletion of backups are separate steps. AI provider retention is governed separately by that provider's policies and the owner's account configuration. No fixed automatic deletion period for all email-derived records is promised.

Control, revocation and deletion

The owner can revoke the app's access using Google Account connections. Revocation prevents continued use of that authorization but does not erase information already stored in conversations, memory, tasks, backups or provider records.

To remove stored access, delete the integration's account credentials from both the setup computer and the private server. To remove email-derived content, review and delete the relevant Companion records, native Hermes sessions, memory and backup copies separately. None of those actions deletes the original Gmail messages through this read-only integration.

Security and changes

The integration uses encrypted Google API and SSH connections, restricts access to credential files and validates account identity and scope. These measures reduce risk but do not guarantee that a computer, server or connected provider can never be compromised.

This policy will be updated when the integration's data practices change. The date above identifies the current version.