A direct connection.

There is no Hermie server in the middle, no separate Hermie account and no analytics SDK in the app. Your messages and attachments go to the gateway address you configure.

hermes serve

Your own gateway process — the one the desktop dashboard and the TUI talk to. Hermie speaks its session protocol directly, with nothing of ours in between.

If your gateway uses an identity provider, signing in can also open that provider’s page. Authentication belongs to your gateway; Hermie uses its native sign-in flow or the session token it provides.

This page explains the Hermie app’s data handling. The website you are reading it on is a separate thing, described further down. This page is not a privacy policy for your gateway or its providers.

Local storage, explained.

Hermie keeps enough information on your device to reconnect and make recent conversations available before the gateway answers.

Credentials
Access, refresh and session tokens, plus extra request headers, use platform secret storage.
Preferences
Your gateway address and display settings use ordinary app storage.
Recent conversations
Transcripts are cached locally for faster loading and offline reading.

The Mac runs the same iOS build and uses its keychain-backed secret storage. Cached transcripts have no additional encryption beyond the protection the operating system gives the app container.

Signing out clears credentials while keeping the gateway address. Reading a cached conversation offline does not run your agents on the device.

You choose what is on the other end.

Your gateway runs the agents and determines which models, tools and external services they use. Those services may process the content you send. Hermie’s direct connection does not mean every part of your agent’s work stays on your own machine.

The gateway operator is responsible for that setup and its data practices. Review those choices when deciding what to share, especially if someone else operates your gateway.

For private access, the project recommends a network such as Tailscale or Headscale. Use HTTPS for connections exposed to the public internet. Hermie supports HTTP for local and private-network setups and indicates when the connection is in cleartext.

Read the gateway requirements

And this website.

The app has no analytics. This website does: hermie.dev uses Google Analytics 4, measurement id G-KLLV2WBHEQ, to count visits and see which pages people read. It runs on the pages of this site and has nothing to do with the app or your gateway.

Page views
Which pages are opened, and the address you arrived from.
Approximate location
Derived by Google from your IP address, not from your device’s location.
Device and browser
Details such as browser, operating system and screen size.

There is nothing else here to collect. This site has no accounts, no sign-in and no forms: there is nowhere to type anything and nothing to submit. It never asks for your gateway address and never sees it.

The measurement id is a single constant in the website’s source. Emptying it removes both scripts from every page, and a browser setting or extension that blocks Google Analytics leaves the rest of the site working.

Open to inspection.

Hermie is open source. You can inspect how connections, credentials and transcript caching work in the repository. The security policy documents the app’s storage and transport behaviour in more detail.

To report a vulnerability in Hermie, contact [email protected] privately. Include the app version or commit, your platform and steps to reproduce the issue.

Issues in Hermes Agent itself, identity providers or gateway infrastructure should be reported to their respective maintainers.

Read the security policy