This policy describes the personal-use Hermes PA setup operated by Richard Li. It covers Google access through PA, the Dan Telegram interface, and this informational website.
Google access requested
The setup requests the following permissions through Google's OAuth screen:
| Permission | Purpose and practical scope |
|---|---|
https://mail.google.com/ | Full Gmail mail access: read, compose, send, modify and permanently delete email, including deletion that bypasses the trash. The scope can expose complete message content. Actual sends, changes and deletions still require the owner's specific instruction. |
https://www.googleapis.com/auth/calendar | View, edit, share and permanently delete calendars accessible through Google Calendar, and manage their events, subject to the account's actual access rights. Actual calendar writes or sharing changes still require a specific owner instruction. |
The owner requested these full Gmail mail and Calendar scopes. The setup does not request Drive, Contacts or unrelated services. The initial connection and agenda acceptance tests remain read-only. Google's official consent screen governs the actual grant; authorizing the scopes does not itself request any send, deletion or sharing change.
What data is used, and why
For a requested task, PA may access account identifiers, selected message content and metadata, calendar names, and event titles, times, participants or descriptions. Initial connection checks are intended to use account and calendar metadata; the initial agenda test reads event summaries and times.
Google information is used to perform the owner's requested email and calendar tasks. The application is not offered as an advertising, data brokerage, credit decision or eligibility service.
Where information goes
- Google: supplies the authorized Gmail and Calendar data and performs specifically requested writes.
- The owner's Mac: runs Hermes and stores PA credentials and local assistant records. OAuth credentials remain with PA and are not copied into Dan or the other specialist profiles.
- OpenAI: relevant task context and Google-derived content may be sent to the configured OpenAI model for language processing. Processing and retention depend on the connected product and the owner's account settings; this page does not promise zero provider retention or claim unverified training controls.
- Telegram: the owner's requests and Dan's responses pass through Telegram. A returned email or agenda summary may therefore be present in the owner's Telegram chat.
- AWS: hosts only these public information pages. Website delivery involves network metadata, such as IP addresses and request information. Google tokens, mailbox data and private assistant records are not part of the website deployment.
Only the task context needed by Dan and PA should be exchanged in their private collaboration room. These local profiles provide logical separation; they are not separate operating-system security boundaries.
Storage and retention
OAuth client credentials and refresh tokens are stored in PA's local profile with restrictive file permissions. Relevant prompts, tool outputs and results may also remain in local session or room history and in Telegram. Local backups may retain records until the owner removes them. No automatic deletion period has been established for those records.
Revoking Google access stops future authorized API use after revocation takes effect; it does not erase messages or results already stored locally, by Telegram, or by a model provider.
Revocation and deletion
The owner can revoke access at Google Account connections. The owner can then remove PA's local Google credentials and the relevant session/room records and backups, and manage Telegram and OpenAI records using those services' controls. Deleting a local credential file alone does not necessarily revoke the token at Google.
For help with access or deletion, contact richardrq98@gmail.com. Do not send passwords, tokens, verification codes or private medical records to request help.
This website
These pages contain no account forms, Google sign-in widget, advertising, analytics script or tracking cookie code. Service providers may still process request metadata under their own policies.
Policy changes
Changes to permissions, providers or data handling must be reflected here before those changes are used. This policy does not claim Google verification or legal certification.