Privacy Policy
Hermes29062026 · personal Google Workspace assistant · last updated 21 October 2026
1. Summary
Hermes29062026 is a personal tool used by one person: Matthew Choi, the owner of the Google account it is connected to. It is self-hosted software running on the owner's own computer. It is not a commercial service, has no customers, and is not operated on behalf of anyone else.
Google data is accessed only to carry out instructions the owner gives. It is never sold, shared with third parties, used for advertising, or used to train any model.
2. Who the app accesses
The app authorises against the Google account of the person who runs it. The OAuth consent is granted by that account. There is no account registration flow and no other person can grant consent to this app.
3. What data is accessed, and why
The app requests the following Google API scopes. Each is used only for the purpose stated.
| Scope | Data accessed | Purpose |
|---|---|---|
gmail.readonly | Mailbox contents: messages, threads, labels | Answering the owner's questions about their mail, such as "what came in today" or "find the message about X" |
gmail.send | Ability to send mail as the owner | Sending a document or summary the owner explicitly asked to be emailed |
gmail.modify | Ability to label, move, and mark mail as read | Marking processed mail as read and applying labels so the owner's inbox stays tidy |
calendar | Calendar events, including event creation and deletion | Listing the owner's schedule, and creating or removing events on the owner's instruction |
drive | Files in the owner's Drive, including their contents | Finding, reading, uploading, and sharing files the owner asks about |
documents | Google Docs documents | Reading a document the owner asks about, and creating or appending to one |
spreadsheets | Google Sheets spreadsheets | Reading a sheet the owner asks about, and writing values the owner supplies |
contacts.readonly | The owner's contact list | Resolving names to email addresses when the owner asks to mail or share with someone |
4. Where the data goes
- Google account data → the owner's own machine, and nowhere else. The assistant runs on hardware the owner controls, on his own network. There is no cloud service operated by a third party in the data path.
- No third-party processors. No analytics SDK, no crash reporter, no telemetry service, no advertising network, and no third-party AI API receives the owner's mail or documents for the purpose of this app's core functions.
- No sale, no sharing, no advertising use, no model training. The data is not sold, licensed, or shared with any third party, and it is not used to train any machine-learning model.
- Credentials are stored locally. The OAuth refresh token is written to a local file on the owner's host, readable only by the owner's own user account, and is transmitted only to Google's token endpoint.
5. Retention
The app does not maintain its own copy of the owner's mailbox. Mail and documents are fetched from Google when an instruction requires them, used for that instruction, and then discarded. Google remains the system of record for the account, and Google's own retention and deletion policies continue to apply to everything stored in the account.
Data the owner explicitly asks to be saved — for example, a receipt logged into a local CSV, or a diary entry written to disk — is kept locally on the owner's machine and is deleted when the owner deletes it.
6. Sharing and disclosure
The app does not share the owner's Google data with anyone. Because the app sends mail and shares Drive files on the owner's instruction, data the owner explicitly asks to be sent is delivered to the recipient the owner names — that is the owner's own decision, made per request.
The owner can revoke the app's access at any time from Google account permissions. Revoking access invalidates the stored refresh token immediately, and the app stops being able to read or send anything.
7. Compliance
This app operates in accordance with the Google API Services User Data Policy and the Google APIs Terms of Service. It does not generate, distribute, or amplify non-consensual intimate imagery (AI-generated NCII) or any other sexual content, and contains no such functionality.
8. Data deletion
Deleting the local OAuth token file and revoking the grant in Google account settings removes all app-held access immediately. Because the app keeps no independent copy of account data, there is no separate deletion request to make and no backup to purge.
Contact
Questions about this policy can be raised with the developer of the app, who is also the owner of the connected account.