Encryption overview
Everything below is encrypted in your browser before it reaches the server. The server stores only ciphertext and never sees your master password. The values on this page are generated from the same code the web app runs, and the Encryption section of your user settings shows the same list.
| What | How it is protected | Technical names |
|---|---|---|
| Passwords and other secret values | Encrypted with your own 4096-bit key pair. | RSA-OAEP, SHA-256, 4096-bit keys |
| Your private key | Locked with a key made from your master password, stretched 600,000 times so guessing it is slow. | AES-256-GCM, PBKDF2-SHA256, 600,000 iterations |
| Attachments | Each file gets its own 256-bit key, locked with your key pair. | AES-256-GCM per file, key wrapped with RSA-OAEP 4096-bit |
| Encrypted backups, link shares and password-protected sends | Protected by their own password, stretched with a method that needs 64 MiB of memory per guess. | Argon2id (memory 64 MiB, 3 iterations, parallelism 1), AES-256-GCM |
What the numbers protect
- Key size (4096-bit RSA). Decides how hard it is to break the key pair directly. Your secrets are encrypted to the public half; only the private half, which never leaves your browser unencrypted, can read them.
- Iterations (600,000 for PBKDF2). Every guess at your master password has to repeat the derivation this many times. The count only slows guessing; a long, unique master password is what keeps your private key safe.
- Memory (64 MiB for Argon2id). Backups and links leave the vault, so their passwords are stretched with a method that also needs memory per guess, which makes guessing on special hardware expensive.
Comparing these numbers between products only makes sense together with what each number protects: an iteration count says nothing about a key size.
Your vault certificate
Your key pair comes with a certificate issued by the built-in certificate authority. Its key type, key size and signature algorithm are read from the certificate itself and shown on the Certificates page and in the Encryption section of your user settings, next to its fingerprint, issuer and validity. No private key material is shown anywhere.