1. Application and operator
Hermes Personal Workspace is a privately operated automation and information-management assistant. It is used by one individual to obtain Gmail summaries, Google Calendar summaries and planning assistance, Telegram notifications, and other personal automations. It is not a Google product, is not endorsed by Google, and is not open to public registration.
Privacy contact: vkonxie@gmail.com.
2. Google data and permissions
The active Google credential currently contains these OAuth scopes:
With these scopes, Hermes can read Gmail messages and metadata and read Calendar events. It cannot use this credential to send, modify, or delete Gmail messages or Calendar events. The Google APIs enforce the granted scopes.
Scope configuration note: the installed Google Workspace setup helper also lists optional scopes for Gmail sending and modification, full Calendar access, Drive, Contacts, Sheets, and Docs. Those scopes are not present in the current credential. A future authorization using that helper could request broader access unless its scope list is narrowed. This policy describes the currently granted Gmail and Calendar access, not any future authorization.
3. How Google data is used
- Gmail: search selected messages and read message metadata (such as sender, recipient, subject, date, labels, and snippets); when requested, retrieve message body text to prepare summaries, reminders, or answers for the operator.
- Google Calendar: read event titles, start/end times, descriptions, locations, status, and links when present, to summarize the operator's schedule and support planning.
- Automation: use relevant Google data only to provide the requested personal assistant features. Some scheduled jobs check mail or calendar information and may generate reminders or summaries.
Google API data is not sold, used for advertising, or used by this application to build a public profile or train an in-house general-purpose model.
4. AI processing and other recipients
Google data may be included in prompts sent to the AI model provider when Hermes is asked to summarize mail, plan around calendar events, or generate a related response. The active Google-related scheduled jobs use OpenAI Codex. This means message or event content needed for a result can be transmitted to OpenAI for processing. Provider-side retention, model-improvement, and other handling depend on the applicable OpenAI product terms and account settings; no specific retention period or blanket no-training setting has been verified for this deployment, so this policy makes no such promise. See the OpenAI Privacy Policy and the applicable Codex product terms.
When an alert or result is delivered through Telegram, Telegram receives that message and processes it under its own terms and privacy policy (Telegram Privacy Policy). A scheduled Gmail monitor also keeps a local deduplication record containing message IDs and check times (up to 2,000 IDs); it does not store message bodies in that deduplication record. The alert may include a message date, sender, and subject.
The public website is intended to be hosted on Cloudflare Pages. Cloudflare may process ordinary website request data, such as IP address, user agent, and request details, for delivery and security (Cloudflare Privacy Policy). The site itself is static and contains no analytics scripts, advertising pixels, or sign-up form. Cloudflare does not receive Gmail or Calendar data through the website.
Other than Google, the configured AI provider, Telegram for requested delivery, and the website host for ordinary web traffic, no additional recipient of Google data was identified in the reviewed integration path. Each provider has its own terms and privacy controls.
5. Storage and security
The Google API helper reads the stored OAuth credential locally and returns requested API results to the Hermes assistant. It does not maintain a dedicated cache of full Gmail message bodies or Calendar events. The OAuth token and Google OAuth client configuration are stored as local JSON files on the self-hosted machine, with owner-only file permissions. The integration does not apply separate application-level encryption to those files; any encryption at rest depends on the host's storage configuration.
Google-derived tool results and generated summaries may appear in Hermes conversation/session records and scheduled-job execution outputs on that machine. These records are separate from the Google API helper's token files. The current integration does not define a Google-data-specific retention period or automatic purge for those records.
Messages delivered to Telegram and content submitted to the AI provider may also be retained under those providers' independent systems and policies. Deleting a local token does not delete prior session records, Telegram messages, or provider-side records.
6. Retention and deletion
No fixed retention period for Google-derived conversation or scheduled-job output has been verified or configured by this integration. Local Hermes records may remain until removed through host-level session or job-history management. The Gmail monitor's local deduplication record is bounded to the latest 2,000 message IDs, but the integration does not set an expiry time for those IDs.
To stop future Google API access, revoke Hermes from your Google Account's third-party connections and remove the local OAuth token. The setup helper can request remote token revocation and delete the local token and pending authorization state; if remote revocation fails, use Google's account security page to revoke access directly. Revoking access does not remove previously generated summaries or copies held by Hermes, Telegram, or the AI provider. Those records require separate deletion through the relevant local or provider controls.
There is no self-service Google-data deletion control in this private assistant. A privacy request should be sent to the operator using the contact channel listed below once it has been confirmed.
7. Google API Services User Data Policy
Use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. Google data is used only to provide the user-facing personal assistant features described here. It is not sold or used for advertising. When data is sent to an AI provider to generate a requested response or sent through Telegram to deliver that response, the purpose is to provide that feature; provider-specific processing and retention remain governed by the providers' applicable terms and settings.
8. Your choices
- Do not request Gmail or Calendar summaries if you do not want that data processed for the feature.
- Revoke Google access at Google Account connections. Revocation prevents future access after it takes effect.
- Ask the operator to remove local Hermes records using the privacy contact once published. Telegram and AI-provider copies may need to be managed separately through those services.
9. Changes and effective date
This policy is effective October 17, 2026. If the application's Google scopes, data uses, AI provider, or delivery methods materially change, this page will be updated and any required user notice or consent will be provided before the changed use begins.