Privacy policy

Hermes Gmail VPS is a personal integration operated by its account owner for their own email account. It uses Google OAuth and the Gmail API to support owner-directed email assistance.

Data accessed and its purpose

The integration requests Gmail read and send permissions. It can access message content, headers, recipients, labels and attachment metadata returned by the Gmail API. It uses this information to show or summarize requested mail, check replies, and compose and send messages on the owner's instructions. The current connector does not provide an attachment-download tool.

Storage and protection

OAuth credentials are stored in private files on the owner's VPS with restricted filesystem permissions. A local sending ledger stores recipient addresses, companies, subjects, message identifiers, content hashes, send times and outcomes. Outreach records may also contain recipient and campaign details. This information supports duplicate prevention, sending limits and verification. Gmail remains the mailbox provider.

Processing and sharing

Requested email content may be supplied to the AI model provider configured by the owner in Hermes to carry out the requested task. That processing is subject to the provider's applicable terms and privacy settings. Messages, recipients and authorized attachments are transmitted to Google to send mail; recipients receive the resulting messages. Google user data is not sold, used for advertising or transferred for unrelated purposes. It is not used by this integration to train a generalized AI model.

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

Retention and deletion

Tokens and sending records are retained on the VPS until the owner removes them. The owner can delete the integration's local credentials, sending ledger and outreach records. Messages held in Gmail are managed separately in Gmail. Removing duplicate-prevention history can allow repeated contact, so the owner should retain only the records needed for ongoing correspondence.

Control and revocation

The owner can revoke access through Google Account connections. Revocation prevents further authorized API access but does not remove previously sent email or local records. The account owner administers access and local data directly. This personal integration does not offer public accounts.

This website

These static pages contain no sign-in forms, analytics scripts or advertising. The hosting provider may process standard request logs to operate the website.