Security Transparency

Exactly how Lockbox protects your data. No hand-waving. No "military-grade" nonsense. Just facts.

Encryption algorithms

AES-256-GCM

All data at rest. NIST-approved. Authenticated encryption prevents tampering.

Argon2id

Master password to key. Memory-hard (32MB). Resists GPU and ASIC attacks.

HKDF-SHA512

Derives separate keys for vault, sync, and sharing from one master key.

Envelope Encryption

Each item has its own random key, wrapped by the vault key. Compromise of one item does not expose others.

Key hierarchy

Master Password
  ↓ Argon2id (32MB memory, 3 iterations)
Master Key
  ├─ HKDF → Vault Key → wraps per-item keys
  ├─ HKDF → Sync Key → encrypts cloud backups
  └─ HKDF → Whisper Key → derives sharing keys

What leaves your device

ActionData sentCan we read it?
Normal useNothingN/A
Whisper shareEncrypted ciphertext onlyNo. Key is in URL fragment.
Cloud sync (optional)Encrypted blobs to YOUR iCloud/Google DriveNo. Encrypted before upload.

What we cannot do

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.

Runtime protection

FeatureDetail
ClipboardAuto-cleared after 30 seconds
Auto-lockLocks when app goes to background
Biometric unlockKey stored in hardware secure enclave (not software)
Dead Man's SwitchAuto-wipe after 7/14/30 days of inactivity
Rate limitingProgressive lockouts after 5/10/20 failed attempts

Open source

Our encryption module is published on GitHub for anyone to audit. We use only proven, well-tested libraries (libsodium, SQLCipher). No hand-rolled cryptography.

github.com/lockboxnow

What about a security audit?

We have not yet completed a formal third-party security audit. We are transparent about this. Our crypto module is open source precisely so that the community can inspect it. A formal audit will be funded from revenue and the results published here.

Contact

Found a vulnerability? Email security@lockboxnow.app