Exactly how Lockbox protects your data. No hand-waving. No "military-grade" nonsense. Just facts.
All data at rest. NIST-approved. Authenticated encryption prevents tampering.
Master password to key. 600,000 iterations via native C++ (OpenSSL). OWASP standard.
Derives separate keys for vault, sync, and sharing from one master key.
Every item is encrypted separately with AES-256-GCM under your vault key, each with its own random nonce and authentication tag.
Cloud sync deliberately sits outside this hierarchy. Your master key cannot derive it, because every install has its own random PBKDF2 salt, so the same master password produces a different master key on each device. The sync key is derived separately from a sync passphrase you choose, which is why you enter that passphrase once per device.
| Action | Data sent | Can we read it? |
|---|---|---|
| Normal use | Nothing | N/A |
| Whisper share | Encrypted ciphertext only | No. Key is in URL fragment. |
| Cloud sync (optional) | Encrypted blobs to Lockbox servers, plus routing metadata (anonymous account ID, device ID, item IDs, change times) | No. Encrypted on your device; we hold no keys. |
Even if compelled by a government, subpoena, or court order, we cannot:
This is not a policy decision. It is a mathematical impossibility. We do not have the keys.
Every feature is built with security first. Here is exactly what protects your data.
What it does: Every item in your vault is encrypted with AES-256-GCM, the same standard used by banks and governments. GCM mode provides authenticated encryption, meaning it both encrypts and verifies that data has not been tampered with.
Why it matters: Even if someone gains access to your device storage, they see only encrypted data. Without your master password, your vault is unreadable.
What it does: Your master password is transformed into an encryption key using 600,000 rounds of PBKDF2-SHA256. This runs via native C++ (OpenSSL/CommonCrypto) for consistent performance on both iOS and Android.
Why it matters: 600,000 iterations meets the OWASP 2023 standard. Each brute-force guess costs significant computation time, making password cracking impractical.
What it does: Each item in your vault is encrypted individually with AES-256-GCM, using a fresh random nonce per item. Your vault key is itself derived from your master password via PBKDF2-SHA256 (600,000 iterations) and HKDF-SHA512.
Why it matters: Items are stored and decrypted independently, so the app never needs to hold your whole vault in plaintext at once. Your keys never leave your device.
| Feature | Detail |
|---|---|
| Clipboard | Auto-cleared after 10 seconds |
| Auto-lock | Locks when app goes to background |
| Biometric unlock | Key stored in the OS keychain (iOS Keychain / Android Keystore) |
| Dead Man's Switch | Auto-wipe after 7/14/30 days of inactivity |
| Rate limiting | Progressive lockouts after 5/10/20 failed attempts |
We use only proven, well-tested libraries (@noble/ciphers and @noble/hashes). No hand-rolled cryptography. These are widely audited, open-source libraries trusted by thousands of projects.
We have not yet completed a formal third-party security audit. We are transparent about this. We use only well-audited, open-source crypto libraries (@noble/ciphers and @noble/hashes). A formal audit will be funded from revenue and the results published here.
Found a vulnerability? Email security@lockboxnow.app