Privacy Policy

Last updated: 25 September 2026

This policy describes how Hermes Backups ("the application") handles data obtained through Google APIs. The application is a private, single-user tool that runs on the owner's own computer and connects only to the owner's own Google account.

Google user data the application accesses

Google service (scope)	Why it is used
Drive	Uploads compressed backups of a local software project to a folder in the owner's own Drive, and deletes the oldest archives so at most twenty are kept.
Gmail (read, modify, send)	Reads the owner's own messages to prepare a daily summary for the owner, and sends mail from the owner's account only when the owner requests it.
Calendar	Reads and writes the owner's own calendar entries when the owner requests it.
Sheets and Docs	Reads and writes the owner's own spreadsheets and documents when the owner requests it.
Contacts (read-only)	Looks up the owner's own contacts when the owner requests it.

How Google user data is used

Solely to perform the actions listed above, at the owner's request. The application does not use Google user data for advertising, profiling, or any purpose unrelated to those actions.

How Google user data is stored

Credentials: the OAuth access and refresh tokens are stored in a single file on the owner's own computer, readable only by the owner's operating-system account.
Backups: project archives are stored in the owner's own Google Drive folder. At most twenty are retained; older ones are removed (and remain recoverable from Drive's trash for approximately thirty days).
Derived content: summaries and other outputs are written to the owner's own computer or the owner's own Google account. Nothing is copied to any other location.

How Google user data is shared

It is not shared with anyone. The application has no other users, no server of its own, no third-party analytics, and no advertising. There is no transmission of Google user data to any third party. The application's use of Google user data complies with the Google API Services User Data Policy, including the Limited Use requirements.

Retention, deletion and revoking access

Revoke access: visit myaccount.google.com/permissions, select the application and remove its access. Access stops immediately.
Delete stored credentials: delete the token file on the owner's computer after revoking access. No credential is retained anywhere else.
Delete stored backups or documents: delete them from the owner's own Google Drive, Sheets, Docs or Gmail in the normal way.

Security

Credentials are stored with restrictive file permissions on a single computer. The application does not transmit Google user data over any channel other than Google's own authenticated APIs.

Children

The application is not directed to children and has no users other than its owner.

Changes

Any change to this policy will be published on this page with a new "last updated" date.

Contact

[email protected]