Last updated October 11, 2026

Privacy policy

This policy describes a personal-use assistant. These public pages are separate from the private assistant.

How Google data is used

With authorization, Hermes reads Gmail messages to find and summarize information; its Gmail permission is read-only. It reads and manages Calendar events, Drive files (including sharing or deletion), Sheets spreadsheets, and Tasks lists and items to carry out requested or scheduled personal-assistant tasks. These services may allow records to be created, changed, or removed at the owner's direction. Google data is not sold, used for advertising, or published on this website.

Oura health data and fitness coaching

The optional Oura integration requests only the read-only daily scope for daily sleep, activity, and readiness summaries. These summaries and trends are combined with the owner’s existing fitness workout log for owner-authorized coaching. Oura workout access is not requested; missing workout information is not invented. Oura data is not sold, used for advertising, or published on this website.

Fitness storage and delivery

Oura client credentials and access and refresh tokens are stored in the owner’s private fitness-profile environment with access restrictions, separate from this public site. Health records and coaching outputs may be retained in that private environment, fitness conversation history, and operational records. Relevant health summaries and workout context may be sent to the fitness assistant’s configured AI provider to generate coaching; this is not exclusively on-device processing. Coaching messages are delivered through Telegram to the owner-selected group topic, where group members with access may read them. Raw health data and secrets are not intended for engineering conversations or public repositories.

Oura retention and control

The owner may disconnect the integration through Oura’s application-access controls and remove locally stored credentials. Disconnecting stops future access but does not erase previously retained fitness records, AI-provider records, or delivered Telegram messages. These may remain until removed under the relevant service’s controls and retention policies. The owner may ask the assistant to stop scheduled coaching and remove local integration records; consequential deletion requires confirmation. No automatic deletion interval is promised.

Storage and processing

Google authorization credentials and operational records are stored in the owner's private assistant environment. Retrieved content and summaries may appear in conversation histories, logs, or task outputs. Relevant data may be processed by an AI provider to fulfill a request, and requested results may be delivered through the owner's connected messaging services. This public website does not host Google account data or credentials.

Retention and control

Operational records may remain until the owner removes them or changes retention settings. The owner can revoke Google access in Google Account settings and remove locally stored credentials. Revocation stops new Google API access but does not automatically remove previously created records or delivered messages.

Public website

This informational website has no account registration, contact form, advertising, or owner-installed analytics. Its hosting provider may process ordinary web request data such as IP address and browser information to deliver and protect the pages. No Google account data is published here.

Changes

If how Google or Oura data is used changes, this policy must be updated before the new use. The Google authorization screen provides the app's support contact.