Hermes Workspace

Privacy policy

Last updated: 3 November 2026. Operator: Jack Salzke.

This policy covers my personal Hermes assistant’s Google Workspace connection and this information website. There is no public account-registration service.

Purpose and information accessed

With my Google consent, the integration can access Gmail messages and labels; calendar information; Drive files and metadata; Docs and Sheets content; and Contacts information. Permissions include the ability to modify data and send email. Access is used to fulfil my requests and personal organisation tasks, not to collect information about website visitors.

The integration is intended for my own Google account. I control which tasks it performs. Email sends and calendar actions affecting others require my explicit approval under the assistant’s operating instructions. These instructions do not restrict the underlying OAuth credentials to read-only access.

AI processing and other providers

Information relevant to a task may be included in prompts and tool results sent to the assistant’s configured AI provider. The current configuration uses OpenAI. Data handling by that provider is subject to its terms, privacy practices and the account’s data controls. Training/data sharing is disabled in the ChatGPT account used by this integration. Google user data must not be used for unrelated advertising, profiling or training general-purpose AI models.

Google provides the connected services. Storage and backup providers process information needed to operate and recover this private installation. Task content is not intended for sale or unrelated distribution. Sharing a file or sending information to another person requires the applicable approval.

Hermes Workspace’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Storage, access and location

Google account credentials are stored as private, unencrypted token files on my managed server, with account-level file permissions. Encrypted recovery backups include those credentials. Task information may also appear in conversation history, memory, tool results, local files and documents stored in Google services.

Access is limited by the installation’s operating-system controls and the accounts used for the connected services. This is a personal installation, not a multi-user service. An administrator or someone who compromises an authorised account or server could obtain access.

Processing can occur on my server and on Google, AI-provider, backup and hosting infrastructure. This policy does not promise that all data remains in one country.

Retention and deletion

Information is kept for the task, ongoing context or recovery needs. Conversation history, memory and backups may retain information longer than temporary working files. There is no verified guarantee that every copy is removed within a fixed period.

Deleting an item from Google does not necessarily remove excerpts already retained in assistant history or backups. Backups expire according to their existing retention schedule rather than being rewritten whenever a source item is removed. Stopping access and deleting retained copies are separate actions.

Consent and disconnection

The connection uses Google OAuth consent. I can review and remove the app’s access through Google Account connections. Revocation prevents further authorised Google API access but does not itself delete previously stored information.

For questions, requests to stop processing, or help removing retained information, contact jgsalzke@gmail.com.

This website

These static information pages do not request Google access, collect form submissions, or contain application analytics or advertising cookies. The hosting provider may process ordinary request metadata, such as an IP address and browser information, to deliver and protect the site. Any information you send by email is processed through the email services involved.