Privacy Policy

Hermes Consent — last updated 2026-09-26

Hermes Consent ("the application") is a private, single-user automation integration. It is operated by one individual, for that individual's own Google account, and has no other users. This policy describes what data the application accesses and how it is handled.

1. Whose data

Only the account owner's own Google data. The application has no other users and does not process data belonging to any third party.

2. What is accessed

• Gmail (read and send) — message metadata and content, to produce summaries and briefings, and to send messages to the owner.
• Google Calendar — event details across the owner's calendars, to produce schedule summaries.
• Google Drive, Docs and Sheets — to create and append the owner's own log and report files.
• Google Contacts — names and addresses, to resolve correspondents.

3. How it is used

Accessed data is used solely to provide the owner with summaries, briefings, reminders and logged records of their own information. No profiling, advertising, marketing, analytics, or automated decision-making about individuals is performed.

4. Where data is stored

The application runs on a single private server controlled by the owner. Data retrieved from Google is stored only on that server, in the owner's own storage, for the owner's own reference. Credentials are stored on that server in protected files and are not transmitted to any third party.

5. Sharing and disclosure

• No data is sold, rented, or shared with third parties.
• No data is used for advertising or to train machine-learning models by this application's operator.
• No humans other than the owner read the data.
• Data is not transferred to any party except the owner.

6. Retention and deletion

Data is retained only while it is useful to the owner and can be deleted at any time by the owner. Access can be revoked at any time through the Google Account permissions page (myaccount.google.com/permissions), after which the application can no longer access the account. Locally stored data can be deleted from the owner's server at any time.

7. Security

OAuth credentials are stored on the owner's private server in restricted files; access to that server is limited to the owner. The application requests the minimum scopes needed for the functions described above.

8. Google API Services User Data Policy

The application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

9. Changes

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

10. Contact

Questions about this policy: augi001@gmail.com