1. Scope and operator
The integration is operated by Jason Tiller for his own personal productivity. It is a private, single-user installation and is not offered to the public as a commercial service.
2. Google data accessed
After the Google account owner grants permission, the integration may access data covered by the approved OAuth scopes, including:
- Gmail messages and message metadata, including permission to read, organize, modify, and send email;
- Google Calendar events and calendar metadata;
- files and content in Google Drive, Google Docs, and Google Sheets; and
- Google Contacts information on a read-only basis.
3. How data is used
Google user data is used only to carry out actions requested by the account owner, such as preparing personal summaries, reviewing schedules and messages, finding information, managing authorized Workspace content, and sending email when explicitly requested.
4. Storage and retention
OAuth credentials are stored locally in the account owner’s private Hermes environment. Google content may be processed locally to complete requested tasks. Generated summaries, task records, or logs may be retained according to the owner’s local Hermes settings. Data and credentials remain under the owner’s control and may be deleted from that environment at any time.
5. Sharing and disclosure
Google user data is not sold, rented, used for advertising, or shared with data brokers. Data is disclosed only when the account owner directs the integration to communicate with another service or recipient, when necessary to provide a requested function, or when required by law.
6. Security
Reasonable safeguards are used to protect locally stored credentials and data. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed.
7. Google API Services User Data Policy
The integration’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
8. User choices and revocation
The account owner may revoke access at any time from the Google Account permissions page and may delete locally stored OAuth credentials and retained data from the Hermes environment.
9. Changes to this policy
This policy may be updated if the integration’s functionality or data practices change. The effective date at the top of this page will identify the current version.
10. Contact
Questions about this policy may be sent to [email protected].