Privacy policy

The short version

• You don't need an account to use sshwiz. We don't know who you are.
• Your SSH credentials never reach us. They're stored encrypted on your machine and sent only to the servers you connect to.
• No analytics, no telemetry, no tracking cookies in the app or on this site.
• We don't sell or share personal data, because we don't collect it.

What sshwiz stores on your computer

Everything the app knows lives in your own operating-system user profile, and none of it is transmitted to us:

• Connection profiles — hostnames, usernames, ports, passwords and passphrases you choose to save. They're written to a local file encrypted with AES-256-GCM; the encryption key is held in your operating system's keychain, not in the file.
• Private keys stay where they already are. A key-file profile stores the path to the key, not the key itself.
• Your Shelf — the packages and scripts you added, including copies taken from the marketplace, plus any recipes you wrote yourself.
• App settings and session history, including the terminal output of commands you ran.

Deleting the app's data directory removes all of it. Nothing is left on the servers you connected to either — sshwiz installs no agent and no daemon; it runs the same commands you would have typed.

Sudo and credential handling

When a command needs privileges, your sudo password is piped to sudo -S over stdin. It is never interpolated into a command line, so it never lands in shell history and is never visible to ps on the server.

What happens when the app fetches the marketplace

The Market tab reads the published catalog anonymously over HTTPS from Google Firestore. There's no login and no identifier attached to the request. As with any HTTPS request, the receiving infrastructure — Google Cloud, and this site's host when the JSON API is used — sees your IP address, timestamp and user agent, and records them in standard server logs under Google's own retention. We don't combine those logs with anything else, and they contain nothing about your servers: the request only asks “what is published?”

Marketplace items you add are copied into your local Shelf. After that they work offline, and we have no way to tell what you added or ran.

The AI assist panel

AI features are opt-in and run on your provider account:

• Your API key is stored locally — in the app's own storage, or in your browser'slocalStorage in the admin portal. It is never written to the catalog or to any database of ours.
• Your prompt (the request you type, plus the item being drafted) is sent to the provider you configured — Anthropic, OpenAI, or any OpenAI-compatible endpoint, including a local Ollama instance, in which case nothing leaves your machine at all.
• Because browsers can't call those providers directly, the portal's requests pass through this site's /api/ai route. The key and the prompt are forwarded for that single request and are not stored or logged server-side.
• Whatever you send is then handled under your provider's privacy terms. Read theirs too.

This website

The public pages — the product page, this policy, the support page and the authoring guide — are static HTML. They set no cookies, run no analytics and embed no third-party trackers. The site is served by Firebase App Hosting, whose infrastructure keeps standard request logs (IP address, timestamp, requested path).

The admin portal at /admin is for the marketplace's own maintainers. It uses Firebase Authentication, which stores the email address and password hash of admin accounts and sets a session cookie so you stay signed in. If you don't maintain the catalog, none of this applies to you.

The public JSON API is rate limited per API key (identified by a hash of the key, kept in memory only) so one client can't exhaust it for everyone.

Who else sees your data

We use two processors, and only for the functions above: Google Firebase (Firestore for the catalog, Authentication for admin sign-in, App Hosting for this site) and, if you turn on AI assist, the AI provider you choose. We don't sell personal data, we don't share it for advertising, and we don't run profiling. We would disclose data if legally compelled — but for app users, there is essentially nothing to disclose.

Your rights

If you're in the EU/EEA, the UK, or a US state with a privacy statute, you have rights to access, correct, export or delete personal data an organisation holds about you. For sshwiz app users, we hold none — the data described above sits on your own machine and you can delete it yourself at any time. If you've emailed support, or you hold an admin account, write to contact@higglerslab.com and we'll action the request; admin accounts and their mail threads are deleted on request.

Children

sshwiz is a system-administration tool for professional use and isn't directed at children under 13 (or under 16 in the EEA). We don't knowingly collect their data.

Changes to this policy

If the policy changes we update the date at the top of this page, and material changes are called out in the release notes for the version that introduces them.

Contact

Questions about this policy, or about anything the app does with data: contact@higglerslab.com. Other ways to reach us are on the support page.