Where your credentials live

On your computer

Server records — host, user, SSH key or password — are stored in a local file encrypted with your operating system secure storage: Keychain on macOS, DPAPI on Windows, the desktop secret service on Linux. If that facility is unavailable, MihraOps refuses to save rather than falling back to plain text.

Known host fingerprints are kept in a separate file. It holds public fingerprints only, so it is not encrypted.

On your server

Git and registry credentials you ask MihraOps to remember are stored on the server you control, under ~/.mihraops/secrets, encrypted with a key at ~/.config/mihraops/keys/master.key. They travel there over your SSH connection and are never routed through our backend.

What licensing receives

Only what licensing needs: the license key you entered, a one-way hash of the machine identifier, a one-way hash of the installation identifier, the device label you can edit, and your platform, operating system version and app version.

Raw machine identifiers never leave your device. The Free plan makes no license calls.

Usage measurement

The desktop app sends no separate usage or telemetry signal. To check for updates it fetches the release manifest from our server, and that request is the only thing usage measurement is based on.

Only a per-day tally is stored: how many installations checked for an update on a given day, per platform. There is no per-installation record, so the count is anonymous rather than pseudonymous. Repeat checks on the same day are folded together in memory only, using the IP address, which is never written to the database.

What it cannot see

SSH private keys and passphrases, server passwords, registry and Git tokens, your source code, container data, environment values, logs and terminal output. None of it passes through our infrastructure, because the connection is between your computer and your server.