Recovery key: what to do if you forget your master password
With zero-knowledge encryption, nobody but you has the key to your vault - not even us. That's why you get a recovery key when you sign up. Here's how it works and where to keep it.
Blog · Security
"Zero-knowledge" is an easy promise to make. Here's exactly what happens to your data - from typing your password to syncing with a second device.
In a zero-knowledge model, the service provider doesn’t know your data or the keys to it. Encryption and decryption happen only on your devices, and the server stores and syncs nothing but encrypted content. In practice, that comes down to three layers.
When you type your master password, the Argon2id algorithm derives a key from it. Argon2id deliberately uses a lot of memory and computing power - a single sign-in takes a fraction of a second, but guessing passwords at scale becomes very expensive. Your master password itself is never sent to the server.
Your data is encrypted with a random vault key using AES-256-GCM. The vault key is protected separately, with the key derived from your master password - so changing your password doesn’t require re-encrypting your whole vault. GCM also detects whether anyone has tampered with the encrypted data, and a fresh random nonce for every encryption means the same item looks different every time.
How do you share an encrypted vault with your family or team without revealing the key to the server? Every member has a key pair. The shared vault key reaches each member encrypted with their public key (RSA-OAEP) - only they can decrypt it. The data itself is still encrypted with AES.
| Data | What the server sees |
|---|---|
| Master password | Nothing |
| Passwords, notes, and cards | Encrypted content only |
| Vault key | Encrypted only |
| Email address, plan, device list | Yes - needed to run your account |
The connection to the server is also protected by TLS, and we store data in the European Union.
Get the details in our Security Whitepaper. Architecture, key management, authentication, and sharing - documented in our technical documentation.