Vault and security
Encryption
The master password goes through Argon2id on the device. Out come an authentication key (the server receives a hash of it) and a vault key that never leaves the device. Every item of the vault (host, key, identity, snippet, database connection) is sealed with XChaCha20-Poly1305 before it leaves for sync.
The server can neither read your hosts nor reset your password.
Recovery key
Shown once at account creation. It alone recovers the vault if the password is lost. It can be regenerated under Settings › Account. Without the password and the recovery key the data is lost: by design.
Two-factor authentication
Settings › Account › Two-factor authentication: TOTP with backup codes. It is required to add a second device, for the remote terminal and for the Claude connector. Sign-in to app.konsolity.com and admin.konsolity.com asks for it too.
When is the code asked? With Continue with Apple, Continue with Google or a passkey, never: Apple, Google and the passkey already protect the sign-in. With e-mail and password, the code is asked only the first time you sign in on a device or browser; it then becomes trusted. To remove that trust: app.konsolity.com › Security › Trusted devices and browsers, or revoke the device in the device list.
App lock
Settings › Security: Face ID, Touch ID or master password when the app comes back to the front, with the content masked. On desktop, quick unlock through the system keychain is offered.
SSH keys
Private keys stay encrypted in the vault; an internal agent signs for sessions without ever handing the key over. Connection logs are redacted: never a password, a key or the text of a command.
Devices
Settings › Account › Devices, or app.konsolity.com: every device, its platform, last activity, country. Revoking a device signs it out and removes its keys everywhere.
Activity and notifications
Settings › Security › Activity (app) and app.konsolity.com › Security › Activity (console) list the security events of the account: sign-ins, new devices, passkeys, CLI machine commands, Claude. Filters by type, period, device and state. Each event opens in a modal: who, what, when, where (device, IP address, approximate city, browser).
A notification opens that modal directly. A destructive command asked by a CLI machine waits for Allow or Refuse. A sign-in, a new device or a passkey added asks It was me or It wasn't me: in the latter case the access is revoked, a new master password is required and an alert is sent by e-mail and to your other devices. While an event is pending, the answer stays possible from the history.
The system notifications carry the same buttons: Allow / Refuse for a command, It was me / It wasn't me for a sign-in or a device, View for an information. You answer without opening the app; Allow asks for Face ID, Touch ID or the device code first. After the sign-in, the app explains these notifications and asks for the system's permission; Settings › Notifications turns them on or off and sends a test notification. On a computer they also appear when the window does not have the focus.