Data handling

Privacy policy

This policy describes Hermes Connector’s personal and household Google integrations and this informational website.

Who operates the connector

Hermes Connector is privately operated by Jacob Chapel for personal use and a small number of personally known household users. For questions, access or deletion requests, contact jacob.chapel@gmail.com.

Google data and permissions

Each integration uses the permissions authorized through Google. Depending on the enabled workflow, this may include:

• Drive: file content and metadata for app-created or explicitly app-opened files, used to publish selected local notes and attachments to the authorized user’s Drive.
• Gmail: messages, metadata and labels used to read and organize information for authorized personal or household tasks.
• Calendar: calendar-list information and event data used for authorized planning and event updates.
• Authorization: OAuth access and refresh tokens used to maintain the connection. Google account passwords are not requested or stored by the connector.

Permissions are granted per account and integration. Enabling one workflow does not imply that every listed service is used for that account.

How data is used and transferred

Google data is used to carry out the configured personal or household tasks, such as producing a requested summary, organizing information, updating events or publishing files. It is not sold, used for advertising, or made into a publicly available dataset.

Some authorized automations use configured AI or other service providers. Relevant task content may be sent to those providers to perform the requested work; their own privacy and retention policies also apply. The connector’s Google credentials are not part of the intended task content sent to an AI model. This informational website has no connection to those private workflows.

Hermes Connector’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 and retention

Authorization tokens are stored on the operator-controlled system with restricted file permissions. Workflow records and derived outputs may be kept in the operator’s local files, configured tools and the authorized Google account. Retention depends on the workflow and the user’s choices; there is no single automatic deletion period.

In the current one-way Drive publishing workflow, deleting a local file does not delete an existing Drive copy. To remove that copy, delete it in Drive and manage its trash or retained versions as needed.

Control and deletion

You can revoke the connector’s access in Google Account connections and ask the operator to stop the relevant workflow or remove locally retained copies. Revoking access prevents future authorized access but does not automatically erase files or outputs already created. Google-held copies can be managed in the relevant Google service.

This website

This site is hosted by Cloudflare and contains only public explanatory text. It has no sign-in, contact form, advertising, application database or application analytics. Cloudflare may process standard request metadata, such as IP addresses and browser information, to deliver and protect the site, under Cloudflare’s privacy policy.

Changes

This policy may be updated when the enabled integrations or data practices change. The current version is available at this address. Contact the operator with any questions before authorizing an integration.