Skip to main content

A password manager that cannot read your passwords

Not as a promise — as a consequence of how the key is built. One share of it is created inside your phone's secure hardware and can never leave, so the vault key cannot be assembled anywhere but on your device, at the moment you unlock it.

See exactly how

Who can see what

The interesting rows are the ones where the answer is “never” — and the one where it is not.

DataYour deviceOur servers
Your passwordsDecrypted only while you are looking at themNever — encrypted entries are not uploaded
Your passcodeHeld only long enough to derive a keyNever — it is not transmitted
Key share 1Created inside StrongBox/TEE, non-exportableNever — this is what makes the rest hold
Key share 2Stored encryptedHandled briefly during key derivation, and stored encrypted. Useless without share 1
Email, device model, security eventsYes — to run your account and refuse abuse

We list that fourth row rather than rounding it away. Our servers do handle one share of the key — and still cannot open your vault, because share 1 has never existed anywhere but your phone.

The proof is what we cannot do

There is no account recovery. If you forget your passcode or lose the device, the vault is gone.

No reset link, no recovery question, no support override — and no way for us to be compelled into one. A service able to restore your vault is a service able to read it; this is the same fact stated from the other side.

Backups and exports carry a layer tied to the device that wrote them, so they open only there. Please keep that in mind before the app becomes your only copy of something critical.

What you control

Erase everything, immediately

Settings → Reset Account wipes the vault and your account data from our servers. No queue, no retention window, no support ticket.

Backups go to your Drive

Not ours. Backup files are written to your own Google Drive account, encrypted. We never receive them.

You can see which device holds the account

On paid tiers an account runs on one device at a time, and the app names the device holding it. A second sign-in is refused, not quietly allowed.

Nothing is filled without you

Every autofill is gated behind a fingerprint or passcode check, every time.

Choose how much protection you want

TierEncryptionExtras
🥈 Silver
Free
AES-256-CTR with HMAC-SHA256, in softwareUnlimited devices
🥇 GoldAES-256-GCM in native code, StrongBox/TEE-backed keysCloud key share, one device per account
💎 PlatinumSame as GoldDevice attestation, certificate pinning, overlay and tamper detection
🛡️ TitaniumSame as GoldOPAQUE zero-knowledge protocol in Rust — the server never sees anything derived from your passcode

Silver runs in JavaScript and does not use hardware key storage. The paid tiers move encryption into native code with hardware-backed keys.

Availability

Android 7.0 and above. Hardware-backed tiers need a device with StrongBox or a TEE; screen-recording protection during passcode entry requires Android 15. There is no iOS version.