Zero-knowledge: what it means and why it matters in a password manager

Almost every password manager advertises AES-256 encryption. What most of them don't make clear is where that encryption happens. And that's the difference between a provider that could read your passwords (or be forced to) and one that mathematically cannot. We call that zero-knowledge.

What does zero-knowledge actually mean?

A zero-knowledge architecture is one where the server never has access to your plaintext data or to the key that decrypts it. Your master password never travels, is never stored, is never processed on the server. All encryption and decryption happen on your device.

The server only stores encrypted blobs: random-looking noise that means nothing without your key.

How does it work technically?

1. You pick a master password that only you know.
2. Your device derives a cryptographic key with PBKDF2 (hundreds of thousands of iterations) or Argon2.
3. That key wraps a vault key (DEK) using AES-256-GCM.
4. Every vault entry is encrypted with that DEK before leaving the device.
5. What reaches the server is already ciphertext, unreadable.

Why does this matter if my provider won't get hacked?

Major password managers have suffered breaches. The difference is huge:

• In a non zero-knowledge provider, attackers can reach your data.
• In a zero-knowledge one, attackers walk away with encrypted blobs that would take centuries to crack, even with dedicated hardware.

It also protects you against rogue employees at the provider, court orders or any scenario where the server is compromised.

What do I lose if I forget my master password?

This is the trade-off: if no one else knows your key, no one can recover it for you. A good zero-knowledge manager gives you recovery keys or social recovery also encrypted on the client, never in plaintext.

How do I verify a manager is really zero-knowledge?

• Public documentation of the cryptographic model (AES-256-GCM, PBKDF2/Argon2).
• Auditable code or independent third-party audits.
• The provider explicitly states it cannot reset your master password.
• Team sharing uses end-to-end encryption (wrapped keys, no plaintext exchange).

Zero-knowledge at Lock Down Keys

At Lock Down Keys we apply zero-knowledge from day one: your master password never leaves your device, shared vaults use per-member wrapped keys and our servers only see AES-256-GCM blobs. To go deeper, read our companion piece on AES-256-GCM explained.