Privacy policy
Applies to Hermes, a personal automation tool operated by one person for his own Google account. Effective 17 November 2026.
1. Who is responsible
This application is written and operated by an individual, Jay, who is also its only user. For anything in this policy, the contact address is vshagan@gmail.com. There is no company, no team and no other user behind it.
2. What Google user data is accessed
The operator signs in to this application with his own Google account and grants it access through Google's OAuth consent screen. Depending on the scopes he has approved, the application can read:
- Google Drive — the file list and file metadata of his own Drive, and the content of files it opens (including Google Docs and Sheets documents);
- Gmail — messages in his own mailbox, read only;
- Google Calendar — events and calendars in his own account;
- basic account information — the email address that identifies the account, used only to know which account it is signed in to.
The application has no access to anyone else's Google account. It never asks for, and is never given, another person's data.
3. How that data is used, and why
The data is used for one purpose only: to provide the application's function to the account owner — searching, reading and indexing his own documents, mail and calendar so that he can find and organise his own material. Every use is a feature he asked the application to perform on his own data. Nothing else is done with it.
4. Storage, and how long it is kept
The application runs on the operator's own computer. Google user data is not stored on any server belonging to the application, because there is no such server. Locally the application keeps:
- an OAuth token (access and refresh token) issued by Google, so it does not have to ask him to sign in each time. It is kept in a local file readable only by his own user account on that computer;
- a local index of the items it has read — titles, identifiers, dates and short excerpts — so that searching is fast.
Both live on that one computer and are removed when he removes them as described in section 7. Data held by Google remains in his Google account, under his control, until he deletes it there.
5. Sharing, selling, advertising and training
- Google user data is not sold or rented to anyone.
- It is not transferred to third parties. No other company, service or person receives it.
- It is not used for advertising, profiling or marketing of any kind, and it is not used to determine creditworthiness or for lending purposes.
- It is not used to develop, improve or train machine-learning or artificial-intelligence models, whether the application's own or anyone else's.
- No human other than the account owner reads it. The application sends nothing to any external service, and this website contains no analytics, no cookies and no third-party assets.
6. Google API Services User Data Policy — Limited Use
Hermes's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In plain terms: the application limits its use of Google user data to providing the user-facing features described in section 3, which are the features the operator actually sees and uses. It does not transfer that data to anyone except as needed to provide those features, to comply with applicable law, or as part of a merger or acquisition with the operator's consent — and in practice no transfer happens at all, because the data never leaves the operator's computer. All other uses, transfers and sales are prohibited.
7. How to revoke access and delete the data
At any time, and without asking anyone:
- Revoke the application's access in the Google Account permissions page: myaccount.google.com/permissions. Once revoked, the stored token stops working immediately and the application can no longer read anything.
- Delete the local token file on the computer where the application runs, which removes the stored credential from the machine.
- Delete the local index the application built, by removing the folder that holds it.
- Delete the underlying data itself in Google Drive, Gmail and Calendar if that is what he wants — the application has no copy that would survive it.
Because the operator is the only user, revocation and deletion are entirely in his hands; there is no third party to notify and no data to retrieve from anyone else.
8. Security
The token is held in a local file restricted to the operator's own user account on his own computer. It is never shared, published, emailed or committed to any public repository. The application connects to Google only over HTTPS. If a token ever leaked, the fix is the same as section 7: revoke it in the Google Account permissions page and delete the file.
9. Children
The application is not directed at children and has no users other than its operator, who is an adult.
10. Changes to this policy
If the application's data practices change, this page is updated and the effective date below changes with it. Because there is one user, he will know about any change as it happens.
11. Contact
Questions about this policy: vshagan@gmail.com.