Last updated October 21, 2026

Privacy Policy

This policy describes how the privately operated Hermes Personal AI integration accesses, uses, stores, and shares data obtained through Google APIs.

1. Scope and purpose

Hermes Personal AI is used by its account owner for personal productivity. The application is not offered as a public service. These pages are informational only; visiting them does not connect to any Google account or collect Google user data.

2. Google data accessed

With explicit OAuth authorization, the application may access Gmail messages and metadata; Google Calendar events and calendars; Google Drive file information and contents; Google Docs and Sheets content; and Google Contacts information. Depending on the owner's request, authorized actions can include creating, updating, or deleting supported content. Contacts access is currently read-only.

3. How data is used

Google user data is used only to respond to requests from the authorized account owner, such as searching email, organizing messages, managing events, and reading or editing files. Information may be included in prompts sent to the AI model endpoint configured by the owner when needed to complete those requests. The owner controls which model endpoint is configured and is responsible for any separate privacy terms governing that endpoint.

4. Storage and retention

Google OAuth credentials and tokens are stored within the owner's self-managed environment rather than on this website. Google data may be temporarily processed or retained in local assistant conversations, logs, or files according to the owner's configuration. Retention and deletion are controlled by the owner; there is no public user database associated with this website.

5. Disclosure and sharing

This integration does not sell Google user data, use it for advertising, or share it with data brokers. Data is exchanged with Google's APIs to perform the requested actions and may be processed by the configured AI model endpoint. The static website is hosted by Cloudflare, but it is not an intermediary for Google account API requests or OAuth token storage.

6. Security and access controls

Access is granted through Google's OAuth authorization process. The application runs in an operator-controlled environment and restricts access to its local credential files. The operator is responsible for security of the environment and for reviewing permissions before approving actions.

7. Revocation and deletion

The owner can revoke Google access at Google Account third-party connections, and can delete locally stored tokens, assistant history, or other retained data within the self-managed environment. Revocation stops further authorized Google API access, although it does not automatically erase previously retained local information.

8. Google API Limited Use

Use of information received from Google APIs is intended to adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not used to train generalized AI models by this integration's operator.

9. Contact

This is a personal-use application. For questions about access and data handling, contact the application owner using the support email provided on the Google OAuth consent screen.

Important: This policy describes the intended configuration of this personal integration. The owner should review and update it if the integration's data storage, model provider, sharing, or retention settings change.