SSH ConnectIn short: SSH Connect has no server — there's no account, no analytics, and no cloud sync. Your servers, identities, private keys, passwords and session logs are encrypted and stored only on your device. The only network traffic the app generates is the SSH connection a client makes to the server you configured it to reach.
1. What we collect
We — the developer of SSH Connect — collect nothing. The app does not include analytics, crash-reporting, advertising, or telemetry SDKs of any kind, and it does not communicate with any server operated by us. There is no account system, so we never see your name, email, device identifier, or usage activity. Nothing about how you use the app is transmitted anywhere for us to receive.
2. What's stored on your device
To function, SSH Connect stores the following information locally, on your device only:
-
Clients (servers) — the host, port, username and
linked identity for each server you save, whether added manually or
imported from an
~/.ssh/configfile. - Identities — reusable login credentials: a password, a private key you paste or import, and an optional passphrase — kept independent of any single server.
- Command history & pinned commands — recent commands run per client, and any commands you pin for one-tap re-run.
- Session logs — a transcript (commands and output, timestamped) of every terminal session, kept for your own reference (see §5).
- App preferences — settings like app lock method, theme, and appearance.
All of the above lives in encrypted local storage, keyed by your device's secure hardware (the iOS Keychain / Android Keystore). None of it is synced to a cloud service, backed up to a server we operate, or accessible to us. Uninstalling the app removes it.
3. Network & server traffic
The only network connections SSH Connect initiates are the ones you configure: each client connects to the host and port you set up, using the identity you attach to it. Any commands you run and any output returned travel directly between your device and that server — they do not pass through us or any server we control. The security and logging practices of the server you connect to are governed by whoever operates it, not by this policy.
4. Private keys & identities
When you paste a private key, import a key file, or enter a password for an identity, it's encrypted and written directly into the device's secure storage. The original key file is never copied elsewhere by the app, never leaves your device, and is included in an exported vault only when you explicitly choose to export it (see §6).
5. Session transcripts
Every terminal session's commands and output are saved locally as a transcript so you can review what happened later. Transcripts stay on-device unless you use the in-app share sheet to export one yourself — at which point the destination (e.g. Files, email, AirDrop) is your choice, governed by that destination's own privacy practices.
6. Vault export & deletion
Settings includes an Export encrypted vault option, which bundles your servers, identities and pinned commands into a single file encrypted with AES-256, locked by a password you choose at export time. That password never leaves your device and is not recoverable by us — losing it means losing access to that specific backup file.
Uninstalling the app permanently deletes every server, identity, credential, and session log stored by the app on that device. This is irreversible and, because we hold no copy of your data, cannot be undone by us either.
7. Biometrics & app lock
You may require Face ID / fingerprint or a PIN to open the app. Biometric data itself is processed entirely by your device's operating system — the app never receives or stores your biometric data; it only receives a yes/no authentication result from the OS.
8. Third parties & data sharing
We do not sell, rent, or share any data, because we do not collect or have access to any. The app does not integrate any third-party analytics, advertising, or data-broker SDKs. The server(s) you configure are third-party systems you choose to connect to, and are outside our control — review their own logging and security practices separately.
9. Children's privacy
SSH Connect is a technical tool intended for developers and sysadmins managing server infrastructure, and is not directed at children. Since we collect no data from any user, we do not knowingly collect data from children either.
10. Changes to this policy
If this policy changes, we'll update the "Last updated" date at the top of this page and, for material changes, note it in the app's release notes. Continued use of the app after a change constitutes acceptance of the revised policy.
11. Contact
Questions about this policy or the app's data handling can be sent to shreyansh@shrynshjn.com.