Security
Client-side AES-256-GCM vault design, what we can and cannot see, and what Certified-style claims we do not make. Not an independent audit.
Encryption happens in your browser with Web Crypto before upload. Algorithm: AES-256-GCM after PBKDF2-HMAC-SHA-256 (250,000 iterations, SHA-256). 12-byte random IV and 16-byte random salt per item.
Titles and categories are encrypted the same way. The passphrase never leaves the browser — we only store a session hint that one was set, not the passphrase itself.
If you lose the passphrase, files cannot be recovered. We do not hold a key escrow.
Files and their titles/categories are encrypted in your browser with AES-256-GCM after deriving a key with PBKDF2-HMAC-SHA-256 (250,000 iterations). The passphrase never leaves the browser.
We cannot decrypt file bytes or labels. We still host ciphertext, file size, and per-item salt/IV. That is client-side encryption, not a claim that we know nothing about the blob.
There is not yet a published independent cryptographic audit. Do not make the vault the only copy of private keys, seed phrases, or recovery codes. See /security.
No. PrivyDeck is a personal privacy dashboard. Personal Shield is not a VPN. The vault is encrypted documents/files, not a password manager.