Driverr — Privacy Policy

Driverr does not collect any data. It is an SSH client that connects from your device directly to machines you name and have credentials for. There is no Driverr server, no account and no analytics. I (the developer) never see your data, because none of it is ever sent to me. This app-specific policy supplements my general privacy policy and takes precedence for Driverr where they differ.

What the App Stores, and Where

• ›Hosts — the name, hostname, port and username you enter, and a herdr socket path if you set one. Stored on the device. They go only to that host, when you connect: the username is sent to sign in.
• ›Known host keys — stored on the device. They do not leave it.
• ›SSH private keys — kept in the iOS Keychain. A private key never leaves the device.
• ›Passwords, if you ask Driverr to remember one — kept in the iOS Keychain, and sent only to the saved host entry’s address, over SSH.
• ›Your settings — theme, font, font size, whether a pane’s screen wraps, and whether Driverr shows Live Activities. Stored on the device.
• ›Where you left off — the last pane you opened, and which blocked panes Driverr has already told you about. Stored on the device.
• ›Other app state — which host is selected, your Start or Stop choice for a host’s Live Activity, and your answer when Driverr offered to install its hook. Stored on the device.

Private keys and passwords are never written to a file or a log. A saved password belongs to the host entry, so it is sent only to that entry’s address. If you edit the address, the password is sent to the new address the next time you connect.

Host Key Checking

The first time Driverr connects to a host, it shows you the key’s fingerprint and stores the key on the device only if you accept it. After that it checks the host’s key on every connection. If the key has changed, Driverr stops the connection, tells you, and does not offer to accept the new key.

What the App Sends, and to Whom

Your terminal input, a command you type in the Run a command field, herdr commands, and the commands described in the next section, over an encrypted SSH connection, to the host you chose. A command you type in that field runs on that host. To sign in, Driverr also sends that host your username, and your password or a signature made with your key, as any SSH client does. If you attach a photo to a message for an agent, Driverr sends that photo to the same host, over the same connection. Nothing goes anywhere else.

While Driverr is in the background, iOS may wake it, no more than about every 15 minutes. If Driverr can sign in without asking you, it opens its own SSH connection to the last host you selected, checks whether an agent is waiting for you, and closes the connection. That check sends nothing anywhere else.

If you tap Continue in Background while connected, Driverr asks iOS to let it keep running after you leave the app. While that task runs, the SSH connection stays open and Driverr keeps checking herdr on that host, so the Live Activity stays current.

What the App Reads and Changes on Your Host

To show an agent’s conversation, Driverr runs commands on your host that read the session files Claude Code and Codex keep there, and the list of skills and commands installed for them. The conversation is shown from memory and is not saved on the device.

Each time you connect to a host yourself, Driverr also reads Claude Code’s settings file to see if its hook is installed, unless you answered Not Now for that host. Driverr holds the file in memory and does not save it.

Driverr changes files on your host only in these cases:

• ›When you attach a photo — Driverr writes it under ~/.driverr/inbox and deletes files there that are more than a day old.
• ›When you choose to install Driverr’s hook — Driverr reads Claude Code’s settings file (normally ~/.claude/settings.json), adds its entry, and writes the file back. If the file already existed, Driverr first copies it to settings.json.driverr-backup beside it, and replaces any older backup.
• ›When you choose to install a key — Driverr appends your public key to ~/.ssh/authorized_keys, and creates the file or the folder if it is missing.

A program running on your host can put text on your device’s clipboard, as in other terminal apps.

Notifications and Live Activities

When an agent on your host is waiting for you, Driverr can show a notification. While Driverr is connected to a host, it can also show a Live Activity on your Lock Screen and in the Dynamic Island. The card names the connected hosts, counts their panes by state, such as working, finished or idle, and says how many need you. When an agent is waiting, it also shows that agent, the title of its pane and the host. iOS may show a Live Activity on a paired Apple Watch too, without any watch app from Driverr.

Driverr makes the notification and the card on the device from what your host sent it. They do not go through a push server. You can turn Live Activities off in Driverr’s settings, and notifications off in iOS Settings.

Where Your Data Lives

On your device and on your own machines, and nowhere else. Driverr has no cloud component: no iCloud sync, no remote database, no crash reporting, no telemetry.

Third-Party Services

None. Driverr integrates no analytics, advertising, attribution or data-collection service. Its third-party code is open source and runs on your device. The list, with licences, is in THIRD-PARTY-NOTICES.md.

Deleting Your Data

You can delete individual hosts and SSH keys inside Driverr at any time. Deleting a host also removes its saved password and remembered host key, unless another saved host uses the same hostname. Deleting an SSH key removes its private key from the Keychain.

Deleting a host, or the app, does not undo changes Driverr made on that host: the hook entry in Claude Code’s settings file and its backup file, photos in ~/.driverr/inbox (Driverr clears old ones only when you attach another photo), and a public key you installed in ~/.ssh/authorized_keys.

Deleting the app removes data in its app container, such as hosts and settings, but iOS may retain Keychain items after an app is uninstalled. To remove saved credentials before uninstalling Driverr, delete every host and SSH key inside the app first.

Children’s Privacy

Driverr does not knowingly collect any information from anyone, including children under the age of 13.

Changes to This Policy

If this policy changes in the future, the updated version will be posted at this URL with a revised “last updated” date.

Contact

If you have any questions about this privacy policy, you can reach me at cunderw.dev/contact, or open an issue at github.com/cunderw/driverr.