Your terminal.
Your data.

The short version

This policy covers the Mobilissh iPhone and iPad app, developed by Dávid Róka, and this product website. It explains local storage and the data you choose to send to your own SSH servers, which are different from data collected by the developer.

What stays on your device

• Host profiles: names, addresses, ports, usernames, authentication preferences, port-forward rules and optional Wake-on-LAN MAC addresses are stored in the app’s local storage.
• Passwords and private keys: saved passwords and software private keys are stored in the iOS Keychain using device-only accessibility. Secure Enclave private keys are hardware-backed and cannot be exported or backed up. The app receives only the result of Face ID, Touch ID or passcode authentication, not your biometric data.
• Public keys and trusted servers: public key metadata and accepted SSH host keys are stored locally.
• Preferences: your settings, fonts, theme choices and terminal configuration are stored locally.
• Terminal content: open sessions retain terminal content and scrollback in memory. Closing a session releases its terminal state; navigating away or disconnecting is not the same as closing it.

Non-secret app files may be included in device backups according to your iOS backup settings. Do not treat a device backup as a backup of device-only SSH credentials or Secure Enclave keys.

Data sent to your servers

SSH connects directly from your device to the host you select. That server receives the connection information needed to provide the session, such as your network address, username, authentication exchange, terminal input and files you send. Password authentication sends the password through the encrypted SSH connection; public-key authentication proves possession of a private key without sending the private key.

Port forwarding carries traffic between the endpoints you configure through your SSH connection. DNS resolution and local-network service discovery may also create traffic to your network’s services. Your server and network operators have their own logging, retention and privacy practices; Mobilissh does not control them.

Clipboard, images and remote files

The app accesses the system clipboard for copy and paste and supported terminal clipboard protocols. Remote programs can request clipboard access; confirmation behavior depends on the request and terminal configuration. Only connect to servers and run programs you trust. Text or images pasted into a session are sent to that SSH server.

Compatible programs can receive pasted image data directly. Otherwise, the app uploads the image over SSH to $XDG_CACHE_HOME/mobilissh-paste, or ~/.cache/mobilissh-paste if that variable is unset, and pastes its path. Files older than seven days are cleaned up on a later image upload, not by a scheduled deletion. You can delete them on the server at any time.

Opening a remote file downloads it over the current SSH connection and saves a protected temporary copy on your device for Quick Look. These copies are not explicitly deleted when the preview closes; iOS manages temporary storage. Sharing a file creates a copy in the destination you choose. Links opened in a browser or another app are subject to that app’s privacy practices.

Permissions and background location

Local Network

Mobilissh can discover nearby SSH servers using Bonjour while the host list is open. Discovered service names and addresses remain in memory unless you save a host. Wake-on-LAN, where permitted by the device and build, broadcasts a packet containing the MAC address you enter on your local network. You can revoke Local Network access in iOS Settings.

Optional location access

Keep connections alive in background is off by default. Enabling it requests location permission and uses low-accuracy iOS location updates while at least one SSH session is connected, to help keep sessions and port forwards running in the background. Mobilissh does not use, store or transmit the location coordinates. iOS displays a location indicator, and this option can increase battery use.

Turn the option off in Mobilissh Settings or revoke Location permission in iOS Settings to stop this use. Ending all SSH connections also stops the updates. Background availability is controlled by iOS and is not guaranteed.

Authentication and files

Face ID, Touch ID or the device passcode can protect access to saved credentials. Key imports use files you select. Sharing and saving use the destinations you choose through iOS.

Retention, deletion and your controls

There is no developer-held app account or server-side profile to delete. You control local data in the app:

• Host and password: delete a saved host. To remove a saved password without deleting the host, edit the host, turn off Save in Keychain, and save.
• SSH private key: open SSH Keys and delete the key. This also removes its stored private key or Secure Enclave reference. Remove the corresponding public key from your servers’ authorized_keys separately if you want to revoke access there.
• Trusted host key: edit the host and choose Forget Host Key. Deleting a host profile does not itself remove its trusted host key.
• Terminal state: use Close Session in the session menu.
• Other local files: deleting the app removes its sandbox under normal iOS behavior. Delete saved keys and passwords with the in-app controls first; uninstalling is not a guaranteed Keychain wipe.
• Remote and shared files: delete uploaded images on the SSH server and shared files in their destination apps. Deleting Mobilissh does not remove those copies.

Device backups and operating-system diagnostics are managed separately by iOS. Mobilissh writes operational messages to iOS’s local logging system; these may include connection or file-operation metadata. It does not upload these logs to the developer. Avoid sharing logs that contain credentials or sensitive server information.

This website and support requests

This website does not set cookies, use browser storage, load third-party fonts, embed social widgets or run analytics. Its assets are served from the same website.

Serving a page necessarily exposes your IP address and request details to the hosting and network providers. Their access-log retention depends on the deployed hosting configuration; this is separate from the app’s no-collection behavior.

If you contact support, you choose what to share, including your email address, message and any attachments. Email providers process that correspondence to deliver it. Do not send private SSH keys, passwords, access tokens or unredacted terminal recordings. Support correspondence is separate from automatic app data collection.

Changes and privacy questions

This policy will be updated here if the app’s data practices change. The review date identifies the latest revision. For questions about privacy or a support message you have sent, use the contact details on the support page.