Privacy Policy

To Your Servers

SSH, Mosh, and SFTP connections go straight from your phone to the server you configured, or through the jump hosts you set up. Your login credentials, what you type, what the server returns, and the files you transfer travel on that connection. SSH and Mosh both encrypt it. Static Hum Studio is not part of that exchange and cannot see it.

To Tailscale (Optional)

If you add a Tailscale API key, SlipShell sends it to Tailscale’s API at api.tailscale.com to fetch the list of devices on your tailnet. That list stays on your phone. Tailscale handles the request under its own privacy policy. SlipShell sends your key nowhere else, and you can remove it in Settings at any time.

On Your Local Network (Optional)

When you scan for servers, SlipShell sends a standard mDNS query asking for SSH servers on the Wi-Fi network you are connected to, and collects their replies. Results stay on your device. Scanning needs no location or Nearby Wi-Fi Devices permission, and SlipShell asks for neither.

To Google Play (Operator Pro)

Operator Pro is a one-time purchase handled by Google Play. SlipShell never sees or stores your payment details. The app asks Google Play whether you own Operator Pro and keeps a record of the answer on your device. It uses the Google Play Billing Library to do that, and Google may collect information about the purchase and your device under Google’s privacy policy. As the seller, Static Hum Studio receives order details from Google, such as an order number, date, and amount, so we can handle refunds and support.

Links You Tap

A few screens link to outside pages, such as the Tailscale admin console, the source code for the bundled Mosh client, and this website. Those open in your browser only when you tap them, and from there the website you visit handles your request.

Local Diagnostic Log

SlipShell keeps a small log on your device to help with bug reports. Each entry records the time, the app build, the kind of event, a number standing in for the session, how long something took, and whether SSH or Mosh was in use.

It never records hostnames, usernames, commands, terminal output, file names, or credentials. Entries older than seven days are dropped. The log leaves your device only if you save a copy to a file or attach it to an email yourself.

Bug Reports (Optional)

From the Support screen, SlipShell drafts an email in your own email app, addressed to hello@statichum.studio. It includes the app version, your Android API level, and what you wrote. You can attach a snapshot of the diagnostic log and read exactly what it contains before you send. The app keeps that attachment in its private cache so your email app can read it, and removes it the next time it cleans up after the attachment is a day old. You can edit or delete anything in the email, and nothing is sent unless you send it.

We use report emails only to look into the problem you reported. If you want yours deleted, ask and we will delete it.

Android Backup

Android can back up app data to your Google account and copy it to a new phone during setup. SlipShell allows this so your setup can come with you, and it can include most of the storage list above, such as your server list, accepted host keys, snippets, themes, settings, and the SFTP transfer queue with its file paths. Passwords, private keys, key passphrases, your Tailscale API key, the diagnostic log, the list of open sessions, unsaved notes, and the folder access for notes and SSH config imports are excluded from both. Folder access cannot move to another phone anyway, so a new phone asks you to pick those folders again. Your notes themselves are files in your own storage, not app data, so they move to a new phone only if you copy them or the folder is synced. Unsaved note text stays on the old phone. Android backup is controlled by your device and Google account settings, not by us.

Files You Export

You can export your servers to a file. A normal export contains server settings and no passwords or keys. If you choose a key backup instead, the file also contains the private keys those servers and their jump hosts use, and the app asks you to confirm before creating it and tells you about any key it could not include. SlipShell adds no encryption of its own to that file, so treat it like the keys themselves.

Either file goes wherever you save or share it. When you share one, the app first writes it to its private cache so the receiving app can read it. That copy is removed after an hour, or the next time SlipShell starts if it was closed before then.