This policy applies to Hermes Calendar, an owner-operated Google Calendar assistant. The service is not offered as a public multi-tenant application. Google Calendar access begins only when the owner explicitly grants consent through Google OAuth.

Publicly publishing the OAuth consent configuration does not make the owner's agents, calendar, credentials, or stored data available to other people.

Hermes Calendar may access the following data after consent:

• calendar names, identifiers, settings, and timezones;
• event titles, descriptions, dates, times, locations, attendees, and event identifiers;
• OAuth access and refresh credentials required to call the Google Calendar API.

The current integration requests the Google Calendar scope only. It does not use this OAuth grant to access Gmail, Drive, Contacts, Docs, Sheets, or unrelated Google services.

Google Calendar data is used only to:

• show and summarize the owner's upcoming schedule;
• create or update an event when the owner directly requests it;
• request fresh, event-specific approval before deleting an event;
• prepare categorized rolling seven-day reports for the owner.

Calendar data is not used for advertising, profiling, sale, or credit decisions, and is not used to train public or third-party AI models.

OAuth credentials are stored only in owner-controlled Hermes profile directories on a private server. Operating-system permissions limit credential files to the server account running Hermes. Raw OAuth credentials are not stored by the public Calculator Suite website and are not sent to Telegram or model endpoints.

Calendar content may be processed by the owner's self-hosted Hermes agents and self-hosted language models when needed to understand a request. Deterministic daily schedule reports read event data without using a language model.

Google Calendar data is not sold or shared with data brokers. Limited portions of schedule data may be sent to an owner-controlled private Telegram channel when the owner enables daily reporting or asks an agent to send a result. Telegram then processes that message under its own terms and privacy policy.

Google processes OAuth and Calendar API requests. Infrastructure and network providers may process encrypted traffic and routine technical logs needed to operate the private server.

OAuth credentials remain stored until the owner revokes access, removes the credentials, or replaces the integration. Calendar event data remains in Google Calendar according to the owner's Google settings. Agent history or private Telegram reports may contain the schedule details needed for the requested interaction and remain until the owner clears those systems.

The owner can request removal of local OAuth credentials and related Hermes history. Calendar deletion is never inferred from a general cleanup request; each event requires fresh approval before deletion.

The owner can revoke Google access at any time from Google Account third-party access settings. Revocation prevents future Calendar API calls after existing access expires.

The owner can also stop the private Hermes gateways, disable schedule jobs, remove the locally stored credentials, or withdraw Telegram bot access independently.

Hermes Calendar's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Privacy questions or requests concerning local Hermes data can be sent to privacy@calculatorsuite.com.

Material changes to this policy will be posted on this page with an updated effective date before they govern new uses of Google Calendar data.