Client-Side Encryption

Web Crypto API

We use the browser's built-in crypto.subtle API — implemented in C/C++ by browser vendors, hardware-accelerated, and independently audited by security researchers.

No External Libraries

Zero JavaScript crypto dependencies. No CryptoJS, no forge, no tweetnacl. Fewer dependencies means a smaller attack surface and no supply chain risk.

Encrypt Before Send

Data is encrypted in your browser, then sent as ciphertext via HTTPS. Double encryption in transit: AES-256-GCM (application layer) + TLS (transport layer).

Decrypt After Receive

Ciphertext is fetched from the server and decrypted in your browser. The plaintext exists only in browser memory — never written to disk, never sent back.

RSA-4096 for Sharing

Each user has an RSA-4096 key pair. When sharing a vault, the vault key is encrypted with the recipient's public key. Only their private key can decrypt it.

Vanilla JavaScript

No React, no Vue, no framework overhead. Pure vanilla JavaScript with the Web Crypto API. Works in every modern browser without polyfills or build tools.

Algorithms used

AES-256-GCM — symmetric encryption for all vault data
PBKDF2-SHA256 — key derivation from master password (600K iterations)
RSA-OAEP 4096 — asymmetric encryption for vault sharing
SHA-256 — auth key hashing for server verification
crypto.getRandomValues — CSPRNG for IVs, salts, and password generation