Hermes Assistant

Data practices

Privacy Policy

This page explains how Hermes Assistant handles data from its dedicated Google account.

Account and information accessed

Google API access is authorized for Hermes Assistant’s dedicated Google account. Hermes does not directly access Edu’s personal Google account unless separate access is explicitly authorized in the future.

Depending on which permissions are granted and integrations are actually used, Hermes may access Gmail messages and metadata, Google Calendar events, Google Drive files, Docs, Sheets, and Contacts (currently read-only). Enabling an API or listing a service here does not mean its data is being accessed; access occurs as needed for authorized tasks.

Why and how data is used

The assistant uses information to carry out authorized assistance: handling correspondence, coordinating appointments and travel, organizing files, preparing drafts, tracking follow-ups, and responding to Edu’s requests. It may check the assistant inbox and calendar for relevant updates once connected.

Processing and sharing

Operational data and OAuth credentials are stored in an access-controlled VPS environment. Relevant information may be transmitted to and processed by the configured AI model provider (currently OpenAI) when necessary to perform an authorized task. Messages and task results may also be transmitted through the configured messaging interface (currently Telegram).

Google user data is not sold or used for advertising, credit decisions, or unrelated surveillance.

Google API Limited Use

Hermes Assistant’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.

Retention and control

Task-related data may remain in assistant session history and operational records; no automatic deletion schedule is currently promised. The account owner can revoke the app’s Google access in Google Account settings and can request a review or deletion of locally retained records by contacting the address below. Revocation stops future API access but does not by itself erase existing local records.

Changes and contact

Material changes in data use should be disclosed before new uses begin. Contact hermesagent08@gmail.com with privacy questions or deletion requests.