The short answer
Zero-knowledge means the service provider has zero knowledge of your data. Your vault is encrypted and decrypted only on your own devices, with a key derived from a master password that never leaves them. The provider stores and syncs ciphertext — scrambled data that is useless without your key.
That is a very different promise from “we encrypt your data”. Many services encrypt data at rest but hold the keys themselves, so an employee, an attacker or a court order can unlock it. With zero-knowledge encryption, there is nothing on the server that can unlock it.
How zero-knowledge encryption works, step by step
- You choose a master password. It is the only secret you need to remember.
- Your device stretches it into keys. A deliberately slow, memory-hard function such as Argon2id turns the password into a strong key. Slowness is the point: it makes each guess expensive for an attacker.
- Keys are split by purpose. One derived key proves who you are to the server; a different, independent key encrypts your vault. The server only ever sees a hash of the first.
- Every item is encrypted locally. Titles, URLs, usernames, passwords, PINs and notes are sealed with authenticated encryption such as AES-256-GCM before upload.
- Only ciphertext is stored. When you sign in on another device, the ciphertext is downloaded and decrypted there.
What happens if the provider gets hacked?
This is the real test. If an attacker copies a zero-knowledge provider’s entire database, they get encrypted blobs and password hashes. To read anything, they must guess each user’s master password offline — and every guess costs them the full Argon2id computation. A long, unique master password puts that out of reach.
Rule of thumb: the security of a zero-knowledge vault rests on two things — sound cryptography from the provider, and a strong master password from you.
Zero-knowledge vs. “encrypted” services
| Zero-knowledge | Server-side encryption | |
|---|---|---|
| Where data is encrypted | On your device | On the provider’s servers |
| Who holds the keys | Only you | The provider |
| Database breach exposes | Ciphertext only | Potentially everything |
| Provider can reset your password and keep data | No (use a recovery key) | Yes |
The trade-off: you are responsible for your key
Because the provider cannot decrypt your vault, it also cannot recover it for you if you forget your master password. Good zero-knowledge managers solve this with a recovery key you generate at sign-up and store offline. Lockvero gives you one when you create your vault; keep it printed or in a safe place.
What to look for in a zero-knowledge password manager
- Modern key derivation: Argon2id (or at least a high-iteration PBKDF2) with published parameters.
- Everything encrypted: not just passwords, but site names, URLs and notes too. Metadata leaks reveal a lot.
- Separate authentication and encryption keys, so logging in never hands the server your vault key.
- Two-factor authentication and passkey support to protect the account itself.
- Safe sharing based on public-key cryptography, so sharing never requires the provider to see your data.
- Encrypted export, so you are never locked in.
How Lockvero applies zero-knowledge
Lockvero derives keys with Argon2id (64 MiB, 3 passes), separates them with HKDF, and encrypts every field with AES-256-GCM bound to its exact place in your vault. Our servers — and our database — hold only ciphertext. Read the full design on our security page.
Put it into practice
Lockvero keeps every password strong, unique and encrypted on your device. Free forever plan.
Create your free vault