Privacy Policy

Overview

Hermes is a self-hosted personal AI agent, built on the open-source Hermes agent by Nous Research. It is run by a single owner on their own server, for their own personal use. Hermes integrates with Google Workspace so that it can act on the owner's own Google data at the owner's request. This policy explains how Google user data is handled by the application.

What Google data Hermes accesses

Hermes connects only to the Google account of the person who runs it (the owner). With the owner's permission, the application may request access to the following Google scopes:

• Gmail — read, send, and modify.
• Google Drive — full access.
• Google Calendar.
• Google Contacts — read-only.
• Google Sheets.
• Google Docs.

Access is requested only so that Hermes can perform tasks the owner has asked for.

How Google data is used

Google data is used to carry out the tasks the owner requests. Examples include:

• Reading a Google Sheet to produce a daily task reminder.
• Reading and sending email.
• Listing, creating, and managing Drive files.
• Reading calendars, contacts, and documents.

The application acts on Google data only in response to the owner's own requests. It does not act on Google data for any other party.

Storage and handling

Google-related credentials and tokens are stored locally on the owner's own server:

• OAuth access and refresh tokens are stored in a file named google_token.json, with owner-only permissions.
• OAuth client credentials are stored in a file named google_client_secret.json.

These files remain under the owner's control on their own infrastructure.

Sharing of Google data

Hermes does not sell or share Google user data with third parties. It is a single-user application and no data is provided to advertisers, data brokers, or other services for their own purposes.

To generate responses to the owner's requests, Google-derived content may be transmitted to the AI model provider or providers configured within the agent. This transmission is limited to what is needed to answer the owner's request. Because the owner runs their own instance, the owner is responsible for the model providers they configure.

Owner control and revocation

The owner can revoke Hermes's access to their Google account at any time through Google's account security settings. The owner can also delete the stored token file (google_token.json) from their server at any time. The setup script for Hermes supports revocation of access.

After access is revoked or tokens are deleted, the application can no longer act on the owner's Google data until the owner reauthorizes it.

Compliance

Hermes's use of Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. Hermes's use of Google user data is limited to the purposes described in this policy and to what the owner requests.

Contact

Hermes is a personal, self-hosted application. If you need to contact the operator of this instance, use the support email shown on the Google consent screen.