Privacy Policy

Hermes Assistant · last updated 4 November 2026

Hermes Assistant ("the application") is a private, self-hosted software agent operated by a single individual for their own personal use. This policy explains what Google user data the application accesses, why, how it is stored, and how it can be removed. It applies to the whole application, and there are no other users.

1. Who operates this application

The application is operated by its owner, an individual, on a private server they control. It is not a company service, has no sign-up, and cannot be authorized by anyone other than the owner. The operator contact address is darvonmedia@gmail.com.

2. What Google data is accessed

Only the owner's own Google Account, and only within the scopes the owner approved at consent:

ScopeWhy it is needed
Gmail (read, modify, send)Search and read the owner's mail; label it; send or reply to messages the owner explicitly approves.
CalendarList the owner's events and create or delete events on request.
DriveFind, read, upload, share and organize the owner's own files.
SheetsRead and update spreadsheets the owner points the assistant at.
DocsRead, create and append to documents.
Contacts (read-only)Look up names, email addresses and phone numbers on request.

3. How the data is used

Accessed data is used for one purpose: carrying out the owner's own instructions. Examples include summarizing unread mail, preparing a daily agenda from calendar events, or locating a document. The data is not used for advertising, not used to build behavioral profiles or train models, and not used for any secondary purpose.

4. AI processing

To interpret requests and compose replies, the content the assistant retrieves (for example the text of an email or the title of a calendar event) may be included in a prompt sent to the AI model provider that powers the assistant. This transfer happens solely to generate the response the owner asked for, and the model provider is bound by its own terms not to use submitted data to train its models. No Google user data is sent to any other third party.

5. Storage and security

Google OAuth credentials and refresh tokens are stored only on the owner's own server, in a file readable solely by the account that runs the application, with permissions restricted to that account (0600). Message, calendar and file content is not stored in a database by the application; retrieved content exists in the assistant's working session for as long as it takes to answer the request. Server access is restricted to the owner.

6. Sharing

No Google user data is sold, rented, traded or disclosed to any third party, and no human other than the owner reviews it. The only exception is the AI model provider described in section 4, which processes content to produce the owner's response.

7. Google API Services User Data Policy

Hermes Assistant's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Data obtained through Google APIs is used only to provide the features described on this site and in section 2 above.

8. Retention and deletion

Nothing is retained beyond what is needed to answer a request. Access can be revoked at any time, which takes effect immediately:

Because no Google content is persisted by the application, revoking access completes deletion.

9. Changes

If the application's data handling changes, this page will be updated before the change takes effect, and the "last updated" date above will change accordingly.