Hermes Google Workspace Connector

Overview

This policy applies to a private, single-user Google OAuth integration operated by Shayne Cooper. The connector links the operator's Google account with a locally managed Hermes Agent installation. It is not offered to the public.

Google data the connector may access

Depending on the permissions granted by the operator, the connector may access:

• Gmail messages, metadata, labels, drafts, and sending functions;
• Google Calendar calendars and events;
• Google Drive files, folders, metadata, and file-management functions;
• Google Docs and Google Sheets content;
• Google Contacts information.

How Google data is used

Google data is used only to authenticate the operator and perform tasks the operator explicitly requests, such as finding a file, reading requested content, creating or updating an item, or sending an operator-approved message.

The connector does not use Google data for advertising, profiling, or sale.

Storage and retention

OAuth credentials are stored on the operator's computer. Task outputs may be stored locally or in the operator's Google account, according to the operator's instructions. The connector does not operate a separate public user database.

Credentials remain until they expire, are replaced, or are revoked by the operator. Local outputs and operational logs remain until the operator deletes them or the configured local retention process removes them.

AI processing and service providers

When the operator asks Hermes Agent to analyze or act on Google content, the relevant content may be transmitted to the AI model provider configured by the operator and to infrastructure required to fulfill that request. Data is shared only as needed to perform the operator-requested task and is subject to the applicable provider terms and configuration.

Disclosure

Google user data is not sold. It is not shared with advertisers or data brokers. It may be disclosed only to service providers required to fulfill an operator-requested task, at the operator's direction, or when legally required.

Security

The connector uses Google's OAuth authorization process and Google APIs over encrypted connections. Access to locally stored credentials depends on the security of the operator's computer and account.

Google API Services User Data Policy

The connector's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Revoking access and deletion

The operator can revoke the connector's Google access at any time from Google Account Permissions. Local tokens and outputs can then be deleted from the operator's computer. Files or events created in Google Workspace remain under the operator's control and can be deleted through the relevant Google service.

Changes

This policy may be updated if the connector's permissions or data-handling behavior changes. The effective date above will be revised when material changes are made.

Contact

Contact the operator through the Gallandis GitHub profile or the support email displayed on the Google OAuth consent screen.