Hermes Agent Personal OAuth Privacy Policy

Last updated:

This policy applies to the personal Google OAuth application maintained by rainbuilt for a self-hosted Hermes Agent instance. The application is used solely by its owner for personal tasks and is not a public service. It does not cover other Hermes Agent installations or the upstream project.

Information Accessed

Depending on enabled integrations and permissions granted through Google OAuth, the application may access Google account information and Google Workspace data, including Gmail messages and attachments, Calendar events, Drive files and metadata, and Docs and Sheets content. Access is limited to the Google permissions authorized by the owner; the application does not receive the owner's Google password.

How Information Is Used

Google data is used to perform tasks requested by the owner, such as finding and summarizing information, drafting or sending email, managing events, and reading or updating files. The application does not sell Google user data or use it for advertising, profiling for advertising, or training or improving generalized AI or machine learning models.

Storage and Processing

OAuth credentials and tokens are stored on the owner's device or self-hosted system running Hermes Agent. Retrieved content and generated results may also be stored there in conversation history, logs, or files, depending on the owner's configuration. This static website does not receive or store Google account content or OAuth credentials.

When a requested task uses an external AI model provider, relevant Google data may be sent to that provider as part of the task's context. Processing and retention by that provider depend on its terms and the owner's settings. Data is shared only as needed to carry out the owner's requested features, or where required by law.

Google API Limited Use

This application's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.

Retention, Deletion, and Revoking Access

Tokens are retained on the owner's system until removed. Conversation history, logs, cached content, and saved files are retained until the owner deletes them or the configured retention settings remove them. The owner can delete stored credentials and application data from the system running Hermes Agent, including any backups.

The owner can revoke access at any time through Google Account third-party connections. Revoking access stops future authorized access but does not automatically delete previously saved data. Any data retained by an external provider must be managed through that provider's settings or deletion process.

Contact

For questions about this application, contact rainbuilt on GitHub.

Application Homepage