We don't ask you to trust us. We give you the tools to verify our security claims yourself โ documented cryptography, a self-hostable deployment, and a responsible disclosure process.
Data flow: your device โ local encryption โ server (ciphertext only) โ attacker sees nothing useful
Every algorithmic choice has a reason. Here's the full stack.
AES-256-GCM
Item encryption
Authenticated encryption with a 256-bit key and per-item random 96-bit IVs. The auth tag detects tampering before decryption.
PBKDF2-SHA256
Key derivation ยท 600k iterations
Industry standard password hashing. 600,000 iterations matches NIST SP 800-132 recommendations for 2025. Salt is stored per-user.
HKDF
Key expansion
After deriving the master key from your password, we use HKDF to produce separate encryption and MAC keys, preventing key reuse.
RSA-OAEP-4096
Key wrapping
Your vault key is wrapped with your RSA-4096 public key for sharing and emergency access. The private key never leaves your device unencrypted.
TLS 1.3
Transport security
All API traffic uses TLS 1.3 with forward secrecy. Even encrypted vault data is protected in transit.
CSPRNG
Random number generation
All IVs, salts, and keys are generated using the platform's cryptographically secure RNG โ window.crypto in browsers, crypto module in Node.
Zero-knowledge
Encrypted on your device; we store only ciphertext
AES-256-GCM
Authenticated encryption for every item
PBKDF2-SHA256
Key derivation from your master password
Self-hostable
Run it on your own infrastructure
VaultKeep has not completed an independent security audit or a compliance certification such as SOC 2 or ISO 27001. We would rather say so plainly than imply otherwise.
We're not here to trash a competitor โ but the 2022 LastPass breach revealed real architectural differences worth understanding.
| Area | VaultKeep | LastPass (2022 breach) |
|---|---|---|
| URL storage | Encrypted client-side | Stored in plaintext โ attackers obtained all URLs |
| KDF iterations | PBKDF2-SHA256, 600,000 | As few as 1 iteration for legacy accounts |
| Transparency | Documented cryptography, self-hostable | Proprietary, vendor-hosted only |
| Data separation | Only encrypted blobs on servers | Mix of plaintext metadata + ciphertext |
| Breach response | Nothing useful for an attacker to steal | Customer vault backups exfiltrated |
We take security reports seriously. If you find a vulnerability, please report it with a description and steps to reproduce.
We commit to:
Responsible disclosure is welcome from everyone. We don't currently run a paid bug bounty programme.
Start with a free account. No credit card, no vendor lock-in, no excuses.
Create your vault