Your calendar stays yours.

This policy explains how Hermes Calendar accesses and handles Google Calendar information.

Effective and last updated: September 2, 2026

1. Application and operator

Hermes Calendar is a private, single-user calendar assistant operated by Ryan Shao. It is used only by the operator for personal scheduling and daily planning.

2. Google data accessed

The application requests Google Calendar access. Depending on the owner's request, it may read event titles, dates, times, locations, descriptions, attendees, and calendar identifiers, and it may create, update, or delete calendar events.

3. How data is used

Calendar information is used only to provide calendar functions requested by the owner, including preparing private daily schedule summaries and carrying out explicit event-management instructions. It is not used for advertising, profiling, or training public machine-learning models.

4. Storage and retention

OAuth credentials are stored on a private server controlled by the owner and protected with restricted file permissions. Calendar data is processed as needed for the requested function. Short schedule summaries and operational records may appear in private Hermes session, scheduler, or system logs. They are not made public and are retained according to the owner's local system-retention practices.

5. Sharing and sale

Google user data is not sold, rented, or shared with advertisers or data brokers. Data is transmitted only to Google APIs and the private systems required to operate the owner's Hermes assistant.

6. Security

Reasonable technical safeguards are used, including least-privilege OAuth scopes, restricted credential-file permissions, encrypted HTTPS connections, and access controls on the private server. No system can guarantee absolute security.

7. Revocation and deletion

The owner can revoke Google access at any time through the Google Account permissions page. The owner may also request deletion of locally stored OAuth credentials and calendar-related operational records by contacting the operator.

8. Changes to this policy

This policy may be updated when the application's functionality or data practices change. The effective date at the top of this page will be revised when material changes are made.

9. Contact

Questions about this policy may be sent to xiang.shao@outlook.com.