Privacy Policy
Last updated: 2026-11-17
Credentials and your own host
Nomad connects to the host you configure. SSH private keys, passwords and VNC credentials are protected by the iOS Keychain and are not uploaded to Nomad's account or telemetry servers. They are used to establish the connection to your chosen host.
Agent conversations and third-party AI
Messages, attachments and task context are sent to your configured host. The agent running there may send this information, including project context it accesses, to its configured AI service provider, such as OpenAI, Anthropic or Google. Those services use the host user's accounts or API credentials and are subject to that provider's terms and privacy policy. Nomad does not include a free AI service or cloud development environment. Do not send personal information or other content you are not authorized to disclose.
Private sharing and browser access
Sharing grants access to a specific conversation, subject to the owner's permissions and history scope. An invitation requests access; a web link alone grants none. Owners or approved recipients can authorize browser access by scanning its QR code in Nomad. Messages and attachments you choose to share can be made available to authorized participants through the owner's Host Service. Host-managed device identities, public keys, permissions and access records are used for authorization. A browser may cache downloaded content on that device. Revoking a share stops future live access but does not remotely erase files, exports or history already downloaded or saved by recipients.
Remote access through the Nomad relay
So that you can reach a computer when your phone is on another network, Nomad can install its host service on a computer you add and register that computer with the Nomad relay. When the app can't connect to the computer directly, the connection passes through a Nomad relay server. It is an SSH connection encrypted end to end between your device and your computer, so the relay forwards it without being able to read it. To do this we store the computer's relay identifier, its name, your user name on it, its operating system and SSH host key fingerprints, and the name and public key of each device you allow; relay servers also process IP addresses, connection times and the amount of data forwarded. Passwords and private keys are never sent to us. Deleting the computer in the app stops its use of the relay and withdraws its registration; the host service stays installed on the computer until you remove it there.
Optional Nomad account and synchronization
Ordinary conversations and host-managed sharing do not require a Nomad account. If you choose to sign in with Apple, Google or GitHub, we store account identifiers, email address and display name, plus non-secret host/agent/team metadata and Saved Messages you choose to synchronize. SSH passwords and private keys are excluded. Authentication and legacy account-managed sharing may also use account/device identifiers, public keys and permission metadata; this is not a cloud copy of the live conversation.
Diagnostic log requests
To look into a connection problem, Nomad may ask your device for its diagnostic log for a few days. The app sends it the next time it is open, compressed, only while the switch "Allow Nomad to Request Diagnostic Logs" in Feedback is on (it is on unless you turn it off). The log records the app's connection steps and their timings, error details, the names and network addresses of your computers, the names of your chats, and the device model and app version. It contains no messages or files. We keep each log for 30 days, then delete it.
Feedback
If you submit feedback, we receive the description, optional attachments and included device/app information. Do not include secrets in feedback. The support email link uses the email application you choose.
Usage diagnostics
Nomad sends a random installation identifier, app-open/foreground events, device model, OS/app version and a country/region code to our telemetry service for usage counts and reliability. Country/region comes from the device's regional setting with an approximate request-country fallback. To measure reliability, Nomad also reports when you add a host, create a session or send a message: whether it succeeded, failed or was cancelled, a predefined failure reason with the error's type and numeric code, how long it took, the network type (such as Wi-Fi or cellular), a random identifier for that app launch, and settings such as the sign-in method or agent type. For a message only its approximate length range is reported, never its text. Crash, hang and CPU-exception diagnostics from MetricKit, and Nomad's own crash record of call-stack addresses, may also be sent. These diagnostics are not joined to your Nomad account and do not intentionally include SSH credentials, host names or addresses, usernames, terminal commands, file paths, chat messages or file contents. Normal network requests also expose connection information to the hosting/network providers handling them.
Notifications and Live Activities
When notification or Live Activity features are enabled, Nomad registers Apple push tokens with its notification relay using the installation identifier. To keep session status current while the app is suspended, the app and configured host can send session identifiers, session display names, host labels, agent labels, running/completed states and timing information to this relay. Turn-completion notifications can also include a short excerpt of the agent's reply (currently up to 140 characters) or an error summary. This excerpt is conversation content and is processed by the relay and Apple Push Notification service as notification text. This is app functionality, not advertising; it is separate from usage diagnostics and does not require forwarding a full conversation history. SSH credentials are not intentionally included. Session labels and notification excerpts can contain personal information. You can manage notifications and Live Activities in iOS settings.
No advertising tracking
Nomad has no in-app advertising or third-party advertising analytics. We do not sell personal data or use the installation identifier to track activity across other companies' apps and websites. Data flows to your selected host, authorized sharing participants and the host's configured AI providers are described above.
Deleting your data
In the app, Profile → Delete Account deletes your Nomad account, synchronized metadata and Saved Messages from our account service. Feedback may be retained with account-identifying fields removed. Account deletion does not delete logs or files on your own host, records held by an AI provider, or copies recipients already saved; manage those through the host, provider or recipient. You can revoke live sharing through the owner's sharing controls.
Contact
For privacy or support requests, contact jerryletsgobig@gmail.com.