Privacy policy

Last updated: 14 October 2026

1. Scope and current status

This policy describes the private, single-user Life OS / Hermes Google Workspace integration and this public information site. The operator uses the integration for their own personal productivity; it is not offered as a service for public registration.

The Google Workspace connection is being configured. No Google account has yet been authorized through this integration. The account-data practices below describe the intended behavior after authorization. The separate pre-existing backup connection is outside this integration's scope.

2. Google data accessed and purposes

After the operator authorizes access, the integration can use the Google APIs and permissions actually granted for:

• Gmail: reading message metadata and content; finding and summarizing mail; preparing and sending approved messages or replies; and approved label or read-status changes.
• Google Calendar: reading calendar and event details, which can include descriptions, locations, and attendees; planning; and approved event or calendar changes.
• Google Drive: searching and reading file metadata and content; approved downloads, uploads, file organization, editing, sharing, or deletion.
• Google Sheets: reading spreadsheet content and preparing or carrying out approved spreadsheet creation and edits.
• Google Docs: reading document content and preparing or carrying out approved document creation and edits.

The intended purposes are user-directed information retrieval, summarization, organization, planning, and document or message assistance. Broad Drive permission can cover existing files the account can access, not just files created by this integration. The planned integration does not include Google Contacts.

Writes and other account changes require explicit operator approval. This is an operating policy for the assistant, not a technical limitation imposed by the Google OAuth scopes. Reading and summarizing may still disclose selected data to an AI processor as described below.

3. Third-party processing and disclosure

Hermes sends conversation context and relevant tool results to a configured remote AI provider to generate responses and perform requested assistant tasks. Google-derived content, such as an email excerpt, event details, document text, or spreadsheet cells, may therefore leave the operator's server.

The currently configured primary model provider is OpenAI, using the OpenAI Codex authentication route. This information site does not establish that provider's retention, human-review, or training settings. Those settings and applicable service terms must be checked before Google account data is processed. This policy does not promise zero retention, local-only processing, or no possible provider access.

Google processes the account's data through its services. The VPS hosting provider supplies the infrastructure on which private credentials and local data are stored. Information can also be sent to recipients or collaborators when the operator explicitly approves an email, invitation, or sharing action. Any additional processing service must be disclosed before it is used with Google data.

4. Storage and retention

OAuth client credentials and access/refresh tokens are stored persistently in private server files so the connection can survive restarts and refresh access tokens. The skill's token-file format is not itself encrypted. At-rest encryption of the hosting storage has not been verified. Credentials and private storage must not be included in the public website's document root.

Google-derived information may persist in conversation history, tool-result records, downloaded files, requested working documents, or explicit saved notes and memories. Server logs may contain operational details and errors. There is no verified automatic deletion schedule for these records; data may remain until the operator deletes it. Deleting a conversation does not necessarily delete a separately downloaded file or saved memory.

No new automated backup arrangement is configured as part of this integration setup. If retained data is later backed up, copies may remain until the relevant backup retention period expires. Any future backup policy must be considered when deleting stored data. AI-provider retention is separate from local retention and depends on the applicable provider terms and settings.

5. Google policy restrictions

The intended use and transfer of information received from Google APIs is limited to the user-benefiting functionality described here and must adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data and developer policy.

Google Workspace data must not be sold, used for advertising, or used to develop, improve, or train generalized AI or machine-learning models. Before enabling AI processing of Google data, the operator must verify that the selected provider arrangement supports these restrictions. A general claim that a model provider is private or secure is not a substitute for that check.

6. Website and connection security

These static pages contain no analytics scripts, external fonts, tracking pixels, forms, account system, or application cookies. The hosting and reverse-proxy infrastructure may process ordinary connection metadata such as IP addresses, requested paths, timestamps, and user-agent strings; logging and retention depend on its configuration.

The site is intended to be served over HTTPS, and Google API calls use HTTPS. These measures do not establish end-to-end encryption for AI processing or guarantee that all stored data is encrypted. The site must not expose OAuth credentials, tokens, private account content, or server configuration.

7. Revocation, deletion, and operator contact

The operator can revoke Google authorization in Google Account connections. Revocation stops subsequent authorized API access but does not erase information already stored locally or retained by processors.

As the only intended user, the operator manages privacy and deletion through their existing private Hermes interface and server administration access. Requests should identify the relevant histories, downloaded files, saved notes, and any backup copies. This site publishes no personal contact information and provides no public registration or data-submission channel. Google account originals remain in Google unless an account modification was separately approved.

8. Changes

This policy must be updated when the connection is authorized or its data handling changes, including before using additional AI providers, external memory services, or other new data recipients. New permissions or uses outside prior consent require further operator approval.