Hermes Personal
Data practices

Privacy Policy

Effective November 15, 2026

This policy covers the Google Docs and Google Calendar integration in Hermes Personal, operated privately for personal use. The account owner administers this deployment and manages access to its data.

Google information accessed

With the owner’s consent, the integration may access Google Docs content and document identifiers, Drive file metadata used to find documents, the list of subscribed Google calendars, and event information such as titles, times, descriptions, locations, and attendees. The granted permissions also allow creating or editing Docs and managing calendar events. Access remains subject to the Google account’s own permissions.

The exact OAuth scope set is Google Docs documents, read-only Drive metadata, Calendar events, and read-only Calendar calendar list. Gmail, Contacts, Sheets, general Drive file writes or sharing, and calendar sharing or whole-calendar deletion are not requested by this connection.

Purpose and use

Google information is used to provide the owner-facing assistant features: locating and summarizing documents, answering questions about documents or schedules, and performing document or event changes requested by the owner. Retrieved content is treated as source material, not authorization to take unrelated actions.

Processing and transfers

Relevant retrieved information may be sent in model requests through the configured Nous inference service and its underlying model provider to generate responses and perform the requested assistant task. This processing is necessary for the assistant’s conversational features. Provider handling and retention are also governed by the applicable provider and account terms. The operator is responsible for maintaining provider settings and use consistent with Google’s Limited Use requirements.

Google user data is not sold, used for advertising, or published on this information website. This integration does not use Google user data to train or improve general-purpose AI or machine-learning models. Transfers are limited to delivering the owner’s requested features, security purposes, or legal requirements.

Storage and retention

OAuth credentials are stored in the operator’s private service profile with owner-only file permissions. Retrieved content, responses, summaries, or remembered information may remain in local conversation history, memory, exported files requested by the owner, and private backups. There is no automatic fixed deletion period for these local records; they remain until the operator removes them or a configured retention rule applies. Copies held by inference providers may have a separate retention period under those providers’ terms.

Controls, revocation, and deletion

The owner can revoke Hermes Personal at any time in Google Account connections. Revocation stops future authorized Google access but does not automatically erase previously retained local conversations, summaries, exports, or backups. The operator can remove the integration’s token files and delete retained local data, and should account for backup copies. The account owner handles access, revocation, and deletion directly through the private deployment.

Security and the public website

The assistant is privately hosted with authenticated access. Google API requests use HTTPS; local authorization uses a temporary loopback callback with PKCE and state checks. These safeguards do not remove all risk. This public website serves static app information and does not host Google data, OAuth credentials, assistant conversations, or an account login. No analytics, advertising, or tracking scripts are added to these pages; the hosting provider may process ordinary request and security logs.

Google API Limited Use

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

Changes

This policy will be updated when the integration’s data practices change. The effective date appears above. Any additional Google permissions require separate owner consent.