Vault is built so that trusting us is optional. The cryptography means your secrets are unreadable to our servers, our staff, and anyone who steals the database. Here's exactly how.
Chosen by you, known only to you. It is never transmitted to a server and never written to disk. Lose it and no one — including us — can recover your vault. That's the point.
Your password is run through Argon2id — the memory-hard winner of the Password Hashing Competition — to produce a key-encryption key (KEK). Memory-hardness makes brute force expensive even with GPUs and ASICs.
A random 256-bit data-encryption key (DEK) actually encrypts your vault. The KEK only wraps the DEK — so changing your master password re-wraps one key instead of re-encrypting everything.
Each field is sealed individually with AES-256-GCM, an authenticated cipher. Decryption fails if a single byte was altered, so tampering is detected, not silently served.
When your vault syncs, it travels and rests as a single encrypted blob, partitioned per account. The key never goes with it.
Honesty beats marketing. Here's how Vault holds up — and where the limits genuinely are.
The attacker gets encrypted blobs and nothing to open them with. Without your master password there is no path to plaintext.
Traffic is TLS, and the payload is already ciphertext. Capturing it yields the same useless blob.
Your vault cannot be recovered. Zero-knowledge cuts both ways — write your backup codes down and keep them somewhere real.
Auto-lock and Face ID limit exposure, but an unlocked vault is an open vault. Set a short auto-lock and lock when you step away.
The strongest claim a password manager can make is “you don't have to take our word.” Vault is built to earn that.