Backup the server cannot read

Your hosts, keys and settings are encrypted on the phone with a key derived from a passphrase only you hold, then uploaded. What reaches the server is a blob nobody but you can open.

Zero-knowledge, meant literally

The passphrase never leaves your device and is not recoverable. If you forget it, the backup is lost — that is what makes the guarantee real rather than a policy promise.

What is included

• Hosts, including passwords and imported private keys.
• Jump hosts, snippets and your port-forward library.
• Security key entries — useful, because the private half lives on the token and travels with it.

What is deliberately excluded

Hardware-backed keys are not backed up. Their private half is inside this device's secure element and cannot be copied anywhere, so including the metadata would restore an entry that appears in your key list, can be selected for a host, and then fails at connect time naming a Keystore alias that does not exist on that device. A missing key you are told about beats a present one that silently does not work, so the app excludes them and says how many it skipped.

AWS, Google Cloud and Cloudflare credentials are not included either. An AWS secret key reaches a whole account, which is a different order of exposure from one server's password. After restoring, enter them again; hosts that use them will not connect until you do.

You can delete your encrypted cloud backup from Settings > Cloud backup.

Restoring onto a new phone

Secrets are re-sealed with the new device's own Keystore on restore. Earlier backup formats stored device-bound ciphertext that only restored onto the phone that made it — a backup that looked complete and was not. The current format is portable, and older ones are detected rather than silently producing broken credentials.

Making a new cloud backup is a Pro feature. Viewing, restoring and deleting a backup you already have is free, including after a subscription lapses. Local export of session history is free.