ANTON IVAAN / HERMES
Last updated: 24 October 2026

Privacy Policy

Hermes is a personal assistant operated by Anton Ivaan.

This policy covers this personal Hermes deployment and its public information pages at anton-ivaan.com/hermes/. It is not the privacy policy for every installation of the Hermes Agent framework. Privacy and support contact: from.siberi@gmail.com.

The assistant is used privately by its operator. This website has no public account registration or Google account connection form. Visiting it does not grant the assistant access to a visitor’s Google account.

1. Google data the assistant can access

Access depends on permissions expressly granted through Google OAuth. The current integration uses the following permissions:

Google Calendar

Calendar names and identifiers, event titles, descriptions, times, time zones, locations, attendees and meeting links. Used to find calendars, answer scheduling questions and manage requested events.

https://www.googleapis.com/auth/calendar.calendarlist.readonly
https://www.googleapis.com/auth/calendar.events

Gmail

Message and thread content, sender and recipient addresses, subjects, timestamps, message metadata and attachments when retrieved for a requested task. The send permission allows messages to be sent on the account owner’s behalf. The integration does not request permission to modify mailbox labels or delete email.

https://www.googleapis.com/auth/gmail.readonly
https://www.googleapis.com/auth/gmail.send

Google Drive

File and folder names, identifiers, metadata, sharing information and file contents retrieved for requested tasks. The current broad Drive scope can technically permit reading, creating, editing, organising, sharing and deleting accessible files, including existing files not created by Hermes. The assistant must act within the account owner’s instructions.

https://www.googleapis.com/auth/drive

OAuth access and refresh tokens are used to authenticate API requests. The assistant does not receive or store the Google account password through this integration.

2. How Google data is used

Google data is used to provide the assistant’s disclosed, user-facing functions: answering the owner’s questions, searching and summarising relevant information, managing requested calendar events, preparing and sending requested email, and working with requested documents and files. Outputs can include summaries, drafts, meeting invitations and documents.

Granting a permission is not authorisation for an unrelated action. The owner’s task instructions determine the work to perform. The integration is not used to sell data, deliver advertising, build advertising profiles, determine creditworthiness, or conduct surveillance.

3. AI processing and service providers

Hermes is an AI-powered assistant. Relevant Google content and tool results may be included in conversation context sent to the AI inference provider selected for the session. In the current environment this can include OpenAI. This is processing to produce the requested answer or action, not a claim that all processing remains on the operator’s device.

The assistant environment is hosted through Nous Research’s Hermes infrastructure. Hosting, storage and inference providers process data as needed to operate those services. Processing may take place in countries other than the account owner’s country. Their applicable terms and privacy notices also govern their service processing: OpenAI Privacy Policy and Nous Research Privacy Policy.

Data or generated content is sent to another recipient or connected service only as necessary for an owner-requested task—for example, sending an email or inviting an attendee—or for the limited security and legal purposes permitted by Google’s policy. Google data is not made public on this website. No data is sold to advertisers, data brokers or information resellers.

The operator does not use Google API data to train or improve general-purpose AI models. Inference services processing Google data must be used under settings and terms consistent with Google’s Limited Use requirements; the use of an AI model does not permit unrelated model-training use. This policy does not promise zero retention by an infrastructure or inference provider.

4. Google API Services User Data Policy — Limited Use

Hermes’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google data and data derived from it are used only for the disclosed user-facing features. Transfers are limited to providing those features with consent, security purposes, compliance with applicable law, or another transfer expressly permitted by Google’s policy. Human access is limited to the account owner and cases allowed by that policy, such as specific affirmative consent, security investigation or a legal obligation. This statement is not a claim that Google has verified or endorsed the application.

5. Storage, security and retention

OAuth credentials are stored in the private assistant environment, separately from the public website and public source assets. Google API requests use HTTPS. Access to the private environment must be limited to authorised accounts. No system can guarantee absolute security.

Conversation history, tool outputs, downloaded files, generated documents and deliberately saved notes may contain Google data and persist in the private environment. There is no automatic short retention period promised for all of these records; they can remain until the operator deletes them or the hosting service’s applicable retention rules remove them. OAuth tokens are retained while needed for the connection and must be removed when the connection is retired.

Infrastructure and inference providers may retain operational, security or backup records under their own applicable policies. A deletion request is not a promise of immediate erasure from every backup. Data intentionally saved in Google Drive, sent by email or delivered to meeting attendees also exists in those destination systems.

6. Revoking access and requesting deletion

  1. Stop future Google access: open Google Account → Third-party connections, select Hermes and revoke its access. New authorised API access stops; existing copied data is not automatically deleted.
  2. Delete retained assistant data: contact from.siberi@gmail.com and identify the data or connection to remove. Do not send passwords or OAuth tokens. The operator will verify the request and remove retained data under their control, subject to security and legal retention obligations.
  3. Remove destination copies: delete or manage files and events in the relevant Google service. Revocation or deletion of assistant history does not recall delivered email or erase copies held by recipients.

The operator can also be contacted about access, correction or other privacy requests. Where applicable, rights under local data protection law remain unaffected.

7. Public website visitors

The portfolio and Hermes information pages are static pages hosted on Vercel. They do not contain a Google login widget, advertising pixels, application analytics or contact forms. Fonts are served with the site rather than fetched from Google Fonts. The hosting provider can process technical request information such as IP address, requested URL, browser information and timestamps for delivery, security and operational logging under the Vercel Privacy Notice.

External links take you to services with their own policies. Contacting the operator by email shares the information you choose to send with the email services involved.

8. Changes and contact

This deployment is not directed to children and has no public sign-up. If its audience, Google permissions or data practices change, this policy and the relevant consent disclosures must be updated before new uses begin.

Questions: from.siberi@gmail.com. Application homepage: Hermes. Also read the Terms of Service.