Security

Zero-knowledge, not zero-effort

KeyAuthy is built so that losing the server would not lose your secrets. Encryption happens on your device, before sync, every time.

AES-256-GCM

Every secret, password, note and transcript is sealed with authenticated encryption before it touches the network.

PBKDF2 key derivation

Your master passcode is stretched on-device into the vault key. The passcode itself is never transmitted or stored.

Server sees ciphertext only

Sync stores opaque blobs. Nobody operating the backend — including us — can read a token, password or recording.

Passkey unlock

Platform passkeys wrap the vault key with hardware-backed biometrics, with the master passcode as fallback.

Auto-lock & clipboard wipe

The vault re-locks on idle and after restart, and copied codes are cleared from the clipboard automatically.

Re-keyable

Change your passcode and every stored row is re-encrypted with a fresh salt, row by row, with visible progress.

Access control

Only your people get in

Scoped team access

Sign-in is limited to the owner account and approved teammates on the clinic domain — everyone else is rejected at the door.

Row-level protection

Database policies scope every row to its owner, so an authenticated session still cannot reach another vault.

Recovery

You hold the only key — so keep a backup

Because the passcode never leaves your device, it cannot be reset for you. Export an encrypted backup file and store it somewhere safe; restoring needs only that file and your passcode.