Privacy Policy

Hermes Personal Assistant is a self-hosted assistant operated by Marc Antoni Mas for my personal use. It runs inside an Ubuntu virtual machine on my Windows computer and connects to my own Gmail account using Google OAuth. I control it through a private Telegram bot.

This policy covers the current Hermes Gmail integration and a planned separate email service. This website only publishes the policy; it is not an email-processing backend and does not store OAuth credentials. Publishing this policy does not grant Google permissions or activate the planned service.

The assistant can read email content and relevant metadata, including sender, recipients, subject, and timestamps, to find emails, summarize them, and prepare suggested reply text at my request.

Hermes’s existing Google OAuth token is restricted to gmail.readonly. This current read-only connection cannot send or schedule email, create Gmail drafts, modify messages, or delete messages. Suggested replies are currently text that I manually copy and send.

A separately operated email service is planned but has not been implemented or verified. Hermes would submit proposed emails to it. The service would hold its own Google OAuth credentials with permissions supporting Gmail draft creation and sending; its exact permissions will be documented when implemented. This would be separate from Hermes’s current read-only token.

The planned service would create a Gmail draft and present a preview of To, CC, BCC, subject, body, and attachments for my explicit approval. The design requires approval of that exact version before sending: changes would invalidate approval, and rejected or expired requests would not be sent.

The service’s Google permissions would permit sending. Requiring my approval would be enforced by the service, not by a draft-only Google permission. The design calls for isolating its credentials and approval mechanism from Hermes, but neither approval enforcement nor credential isolation has been implemented or verified. Prevention of unauthorized sending is not guaranteed.

If implemented, the service would process proposed email content, recipients, relevant metadata, attachments when provided, and approval records to manage drafts, previews, approval decisions, and sending.

Google handles OAuth authorization and provides the authorized Gmail data through its API.

Selected email content may be sent to OpenAI through my configured ChatGPT/Codex subscription connection to process requests and prepare summaries or suggested reply text. Processing is therefore not limited to the local virtual machine.

Telegram carries my requests to the assistant through the private bot. Requested summaries and suggested replies may appear in Telegram and may contain email-derived content. Read-only Gmail access does not prevent this content from being processed by OpenAI or appearing in Telegram.

If implemented, the separate email service would receive proposals from Hermes and exchange draft and sending data with Google. OpenAI and Telegram would remain involved where selected content is processed or displayed through the configured workflow; the planned service’s preview and approval channel is not yet specified here.

These providers handle the data they receive under their applicable terms and privacy policies. This policy makes no guarantees about their retention or other data-handling practices.

OAuth credentials are stored locally in the Ubuntu virtual machine, separately from this website. Local conversation history, logs, or backups may retain email-derived content, including summaries and suggested replies.

If implemented, the email service could also retain credentials, proposed messages, recipient details, metadata, attachments when provided, and approval records in its storage, service records, logs, or backups. Its storage locations and removal procedures have not yet been established here.

There is no fixed retention period stated here. Content is not necessarily deleted immediately after a request, and removing one local copy does not automatically remove other copies in histories, logs, or backups, or data already received by providers.

I can revoke the assistant’s access from my Google Account connections page by selecting Hermes Personal Assistant and removing its access. If the separate service is implemented and authorized, I would also need to revoke any separate Google authorization it uses; revoking Hermes’s current token would not necessarily revoke the service’s access.

Revocation stops future authorized access under the revoked authorization, including draft creation and sending where applicable. It does not automatically delete existing copies, Gmail drafts or sent messages, local or service records, or content already sent to OpenAI or Telegram.

Manage connections in your Google Account

As the owner, I can stop the assistant in the Ubuntu virtual machine, remove its locally stored OAuth credentials and tokens, and delete email-derived conversation history and logs from the assistant’s configured storage locations. I can also review and remove backups containing those credentials or email-derived content, including copies stored outside the virtual machine.

If the separate service is implemented, I would also need to stop it and remove its credentials and retained data, including proposals, attachments, approval records, logs, and backups, from its actual storage locations. Concrete removal instructions must be documented with that implementation; no deletion commands are specified for the unbuilt service.

Revoking Google access and removing local data are separate steps. Deleting local files does not delete messages in Gmail or copies held by OpenAI or Telegram; any available provider-side deletion controls must be used separately.

For questions about Hermes Personal Assistant or this policy, contact Marc Antoni Mas at the public address below.

[email protected]