Scope
Hermes Gmail for Atlas is Ryan’s personal-use desktop integration. This notice applies to the Gmail access and local processing provided by this integration, not to every Hermes tool or service.
Access
Atlas uses Google OAuth Gmail read-only permission. That permission permits the integration to read Gmail message metadata and message content for organization. It does not grant permission to send, edit, or delete Gmail messages.
Use and processing
Gmail data is used to organize Ryan’s mail and prepare information for his review. Routine processing is designed to run in the local Hermes environment. No Gmail data is published on this website.
Local storage and retention
OAuth credentials are stored in protected local files. Local operational metadata may include the connected account identifier, authorization state, provider cursors, check timestamps, fingerprints, and deduplication or review state.
The approved collector is under development and does not currently maintain an active Gmail message-body cache. Local credential files, operational records, and local backups are retained until the operator removes them; this notice does not promise an automatic deletion period.
Sharing and the public website
The static website contains no Gmail data. The hosting provider may create ordinary server logs needed to deliver and secure the site. These pages add no analytics, advertising trackers, forms, or sign-in flow.
Gmail data is used only to provide the Gmail organization features described here. It is not used for advertising, sold, or used to train a general-purpose AI model. This statement is not a claim of external certification.
The integration uses Google’s APIs to access Gmail. Any future non-local processing or third-party sharing would be reviewed and disclosed in an updated notice before activation.
Control and revocation
Ryan can revoke Atlas’s Google access through his Google Account permissions and can remove local credentials and operational records from the Hermes environment. Revocation stops future Gmail API access; it does not automatically erase local files, records, or backups that already exist.
Changes and contact
This notice will be updated if the integration’s Gmail access, use, storage, or sharing practices materially change. Contact: ryan.houston@gmail.com.