Privacy policy

Hermes Agent Mobile is a native iOS client for a user-configured, self-hosted Hermes WebUI server or Hermes agent host.

The app does not create an account with the developer. For normal public use, there is no hosted backend operated by the developer, except the optional push notification relay described below.

Hermes Agent Mobile does not send user data anywhere except the server the user configures, other than normal Apple/iOS system services used by permissions and, if the user turns on push notifications, the push relay described below.

Hermes Agent Mobile does not track you across apps or websites.

The app does not show ads, include third-party analytics SDKs, or collect in-app purchases or payments.

You provide the Hermes server URL and access details used to connect to your configured server.

The app stores the configured server URL in iOS Keychain.

If the Hermes WebUI server requires a password, the password is sent to that server only to sign in. Hermes Agent Mobile does not store the Hermes WebUI server password after login.

Bot Mode is optional and off by default. If the user sets up a Bot Mode connection to a Hermes agent host, the app stores that host's address, username, and password in iOS Keychain so it can sign in again, and sends the password only to that host. They are removed when the connection or its configured server is removed from the app.

Login/session cookies are handled by iOS networking cookie storage and are cleared when the user signs out or reconfigures the app.

As part of app functionality, Hermes Agent Mobile may send prompts/messages and assistant conversation data to the user-configured Hermes server.

The app may also send selected attachments, photos, files, shared content, URLs, workspace/file requests, and session actions or settings such as model, profile, reasoning, and workspace choices.

This data goes to the configured Hermes server, not to a developer-hosted backend in normal public use.

Hermes Agent Mobile stores the saved server URL (and any Bot Mode connection, as described above) in Keychain and app preferences in UserDefaults.

If push notifications are enabled for a server, the keys that pair the app with that server's notifications are stored in Keychain and removed when the server is removed from the app.

The app uses a local SwiftData offline cache so recent content can be viewed when the configured Hermes server is unavailable.

Cached sessions/messages can include session metadata, message text, reasoning text, tool-call metadata, and attachment metadata. The local message cache is capped at 5,000 messages.

Cached data expires after 7 days. Users can clear it from Settings → Offline Data → Clear Offline Cache.

Bot Mode keeps a separate on-device cache of recently loaded bot conversations, limited to 100 conversations and 8 MB, which expires after 30 days. Clear Offline Cache also clears it, and it is removed when its configured server is removed from the app.

Clearing the local cache removes local cached data from the device and does not delete anything from the configured Hermes server.

Shared text, URLs, files, and photos may be staged locally in the app group container when using the iOS share sheet.

Staged shared content is loaded by Hermes Agent Mobile when the app opens.

Staged content is sent to the configured Hermes server only when the user attaches or sends it through the app.

Photos and files are accessed only when the user selects them, shares them to the app, or exports/saves content.

Photos add-only permission is used to save exported workspace images to Photos.

The camera is used only when the user chooses to take a photo to attach in chat. Captured photos are sent to the configured Hermes server only if the user sends them.

Microphone and speech recognition are used only when you explicitly use composer dictation.

Hermes Agent Mobile does not persist audio recordings. Dictation produces editable draft text, and that text is sent only if the user sends the message.

Response-complete notifications are optional local notifications.

Notification title/body are generic and do not include transcript content. Notification payload is limited to routing info such as a session ID when needed.

Push notifications are optional and off until the user enables them for a server. When enabled, the user's Hermes host sends notifications through a relay operated by the developer, which forwards them to Apple's push notification service. The relay is open source (github.com/uzairansaruzi/hermex-push), and a server operator can run their own instead.

The relay receives the device's push token and notification metadata: the kind of notification, whether it came from a bot or a WebUI session, thread and session identifiers, and timestamps; for progress updates, also a status, the name of the running tool, and a call count. It stores the push token under a hash of the pairing key, not an account.

Notification text, such as the title, body, and profile name, is encrypted on the user's Hermes host and can be decrypted only on the user's device. The relay never receives message text, server URLs, or Hermes server credentials, and request logging is turned off.

The relay keeps a device's registration until push is turned off, the server is removed from the app, or Apple reports the token as no longer valid. Live Activity registrations expire after eight hours, and delivery receipts after ten minutes.

Live Activities may show session title, status, timer, or tool state on the Lock Screen or Dynamic Island. When push notifications are enabled, Live Activities can be updated through the same relay while the app is in the background.

Response excerpts in Live Activities are off by default and require explicit opt-in in Settings.

Local cache can be cleared in the app.

Configured-server data retention and deletion depends on the user's Hermes server setup.

Users should manage or delete server-side data on their configured Hermes server.

Questions about retention, deletion, or this policy can be sent to uzairansar@gmail.com.

Hermes Agent Mobile uses app libraries, not tracking or advertising SDKs.

Current third-party code includes LDSwiftEventSource, MarkdownUI, Splash, Highlightr / highlight.js assets, KeychainAccess, SwiftMath, NetworkImage, swift-cmark, and Lucide icons.

Questions about this policy can be sent to uzairansar@gmail.com.