Two secrets, both required
A password and an Access Key. A guessed or stolen password alone cannot open a vault.
Security
Built so we can’t read your secrets.
Passwords, keys, card numbers and other secret fields are encrypted on your device before they reach us. This page shows how, and is just as clear about what we can still see.
- AES-256-GCM
- Authenticated encryption for every secret field, with ChaCha20-Poly1305 available where a vault uses it.
- Argon2id + PBKDF2
- Your password and Access Key are turned into keys on your device, never on our servers.
- Hash-chained audit log
- Security-relevant actions are recorded in a chain that shows if an entry was altered or removed.
What we can and can’t read
Secret fields are end-to-end encrypted. Names and non-secret fields are encrypted in transit and at rest, but our servers can read them — that is what makes search, tags and notifications work.
Encrypted on your device
We cannot read these, even with full access to our database.
- Passwords, tokens and API credentials
- Card numbers and security codes
- SSH and private keys, recovery passphrases, seed phrases
- Account numbers, PINs, national ID numbers
- Notes, including their titles and folders
- Attachments, and the earlier values of any secret field
Readable by our servers
Protected by TLS and by storage encryption, but not end-to-end.
- Item names and the type of item
- Tags and the website an item belongs to
- Non-secret fields, such as a username or a card’s expiry date
- Vault and folder names
Put anything sensitive in a secret field or a Note, not in a title or a tag.
How your keys work
Five steps, all of them on your device. The server only ever sees the result.
- 1
Your password becomes a secret on your device
It is stretched with PBKDF2-SHA256 (600,000 iterations) into a password-derived secret that stays in memory. It is not your vault key, and it is not stored.
- 2
Your Access Key is generated on your device
A random 30-character key, shown once in your Emergency Kit. We keep only a one-way check that it is the right key — never the key itself.
- 3
The two are combined into an unlock key
Argon2id of the password secret is mixed with an HKDF of the Access Key. The result is held in memory only. Neither factor alone is enough.
- 4
The unlock key opens your master key, then each vault’s key
A random 256-bit master key is wrapped by the unlock key; every vault has its own random 256-bit key, wrapped by the master key. Our servers store only wrapped keys.
- 5
Secret fields are encrypted before they are sent
Each field is encrypted with AES-256-GCM and a fresh random nonce. Changing your password re-wraps one key; it never re-encrypts your items.
What we built around it
Encryption is the foundation. These are the controls that keep it from being bypassed.
Passkeys and second factors
Authenticator app, passkeys and backup codes at sign-in, and a passkey option to unlock the vault.
Trusted-device unlock
Pair a phone once by QR code, then approve browser unlocks from it. Trust is only ever created by pairing.
Sharing without sharing your keys
Each recipient gets the vault key re-wrapped for them on your device. Ownership can never be shared, and secure links keep their key in the URL fragment, which is not sent to a server.
A tamper-evident audit trail
Hash-chained entries, checked before any purge, with retention that depends on your plan. Designed to support SOC 2 Type II, ISO 27001 and GDPR Article 30 reviews.
Machine access with a policy engine
Pipelines use scoped keys with path patterns, environment pinning and per-key narrowing, and are rate limited by plan.
Backups you control
A vault backup restores as a new vault, never over the live one. Enterprise organization archives are encrypted to keys you hold and delivered to your own storage.
Abuse protection on every sign-in path
Progressive delays, IP blocking, and identical responses for known and unknown addresses, so a form cannot be used to find out who has an account.
Limits we state plainly
A security page that lists only strengths is marketing. These are the trade-offs.
- We cannot reset your master password or recover your Access Key. Without your Emergency Kit, encrypted fields are unrecoverable by anyone, including us.
- Item names, tags and non-secret fields are readable by our servers. Keep anything sensitive in a secret field or a Note.
- While your vault is unlocked, anything on your screen can be read by software already running on that device.
Go deeper
Security model
The key hierarchy, device trust and the boundaries between them.
Read moreWhat zero-knowledge means here
Exactly which data we cannot read, and which we can.
Read moreAudit and compliance
How the audit log is chained, kept and verified.
Read moreFound a vulnerability?
We run a bug bounty program, and researchers acting in good faith are covered by our Safe Harbor policy.
Security FAQ
See it for yourself
Create a vault, and read exactly what is encrypted before you store anything.
Create Your Free Vault