HERMES WORKSPACE OAUTH / PRIVACY

Privacy policy

Last updated: 2 September 2026

1. Operator and purpose

Hermes Workspace OAuth is operated for the account owner’s personal use with their self-hosted Hermes agent and gog command-line tool. It is not a public registration service. Contact: passcom.net@gmail.com.

2. Google data and permissions

Depending on the permissions granted through Google and the requested task, the integration may access email content, attachments and metadata; Drive files; calendars and events; documents, spreadsheets and presentations; contacts; tasks; forms and responses; Apps Script projects; and Classroom resources.

Permissions can include reading, creating, editing, sending, sharing or deleting supported resources. The Google consent screen identifies the requested permissions. Enabling an API alone does not grant access. Only permissions necessary for the enabled personal workflow should be granted.

3. Use of data

Google user data is used for the account owner’s requested assistant tasks, such as searching, summarizing, drafting communications and organizing or updating Workspace resources. Data is not sold or used for advertising, credit decisions or unrelated profiling.

4. AI providers and transfers

The currently configured AI provider is OpenAI. Content needed for a task may be sent to OpenAI, subject to the operator’s selected product, settings and applicable terms. OpenAI products do not necessarily have identical retention or data-use settings.

Before sending Google user data, the operator must confirm that the chosen provider configuration complies with Google’s Limited Use requirements, including restrictions on training generalized AI or machine-learning models. If those conditions cannot be met, Google user data must not be sent to that configuration.

Other AI providers may be added only after reviewing their data handling and updating this policy to identify them before they receive Google user data. Only task-relevant information should be sent. This app does not authorize providers to use Google user data for generalized model training.

5. Storage, retention and security

OAuth credentials and tokens belong in the operator-controlled agent environment, not in this public website. The operator is responsible for restricting access to credentials, retrieved content, task histories, caches, logs and backups.

Local retention depends on the agent’s history, logging and backup settings; this policy does not promise an automatic deletion interval. The operator can remove retained copies when no longer needed. Provider retention depends on the selected product and settings. Revoking Google access does not automatically delete copies already retained locally or by a provider.

6. Revocation and deletion

The owner can stop the integration and revoke authorization at Google Account connections. This stops future access under that authorization. Retained local histories, caches and backups must also be removed where applicable; provider-side data requests follow the provider’s controls. Contact the operator for assistance.

7. This informational website

This site provides app information and this policy. It does not request Google credentials, run Google sign-in, accept uploads or include application-level analytics or advertising. Cloudflare, its hosting provider, may process connection and security metadata such as IP addresses and request logs under its privacy policy. Visiting this site does not require Google account content or OAuth tokens.

8. Limited Use and policy changes

Hermes Workspace OAuth’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data must not be used to train or improve generalized AI or machine-learning models.

Material changes to data use, providers or sharing will be reflected here before changed processing begins. New Google permissions require authorization through Google.

← Back to app information