How Hermes Calendar handles data.

Access and purpose

With the owner's Google consent, Hermes requests Calendar event access and read-only calendar-list access. It can retrieve calendar names, identifiers, timezones and permissions, and event titles, descriptions, locations, dates, recurrence information, organizer and attendee information. Google permissions determine what is visible. Data is used to answer the owner's private calendar questions and prepare explicitly approved event creation or updates.

Google's event permission also authorizes deletion at the OAuth level. Hermes provides no event deletion tool. It provides no sharing, calendar-creation or guest-management tool. Changes can be visible to existing guests or people sharing the calendar; Google may send service notifications.

Processing and disclosure

Selected calendar results and the owner's requests are processed by the privately operated Hermes service and its configured self-hosted AI model service. Replies and exact change proposals are delivered through the owner's encrypted Matrix conversation. The assistant decrypts messages for processing; chat encryption does not prevent private server history from retaining content.

Google receives API and authorization requests. The integration does not publish calendar data on this website or send it to GitHub Pages. The Calendar adapter has no advertising, data-sale or model-training function.

Storage and retention

OAuth credentials and refresh tokens are stored in access-controlled private storage. Automatic refresh continues only while Google authorization remains valid. Credentials are excluded from model tool results and adapter error messages.

Private conversation history, tool results, operational records and change-proposal records may retain requests, calendar content and identifiers. The proposal ledger keeps exact proposed changes and relevant previous values. Its ten-minute approval window does not delete stored records. The integration currently has no automatic time-based deletion policy for durable records. Storage and backup retention on the private servers are controlled by the operator.

Owner control

Only a fresh verified owner message can approve a stored change proposal. Calendar descriptions or other retrieved content cannot authorize changes. The owner can revoke future access through Google Account connections. Revocation does not erase records already stored. The owner can request removal of private records through the existing private Hermes conversation; server copies and backups require operator handling.

This informational website

The site's files contain no scripts, forms, analytics, tracking pixels or embedded third-party resources. GitHub Pages hosts these public pages and logs visitors' IP addresses for security. GitHub's processing is described in its Privacy Statement.

Contact and changes

Operator: JohnL404. The authorized owner can raise privacy questions through the existing private Hermes conversation. This policy will be updated before materially different data handling is enabled.