Zero-knowledge AES-256-GCM locking
Encryption and decryption run 100% client-side using Web Crypto subtle APIs with a random 16-byte salt and 12-byte IV on every lock.
Lock your disposable inbox with your own password right in the browser (PBKDF2 + AES-256-GCM) and unlock it later on any device — your password never leaves your device.
Tempboxy encrypts your private signed inbox token (tbx_v1_...) locally in your browser using Web Crypto PBKDF2-SHA256 (120,000 iterations) and AES-256-GCM with your chosen password, outputting a portable tbx_pw_... key. Nobody — not even Tempboxy servers — sees your password or can unlock the key without it.
Prefer keyless instant restore? Use Reusable Temp Mail or No Expiry Tempmail →
Encryption and decryption run 100% client-side using Web Crypto subtle APIs with a random 16-byte salt and 12-byte IV on every lock.
Copy your compact tbx_pw_... string or save a JSON vault file, then unlock and reopen your private .com or .edu.pl inbox from any device.
Your live address loads automatically. Type any password (4+ characters) in the Lock active inbox box and click Lock Inbox to generate an encrypted tbx_pw_... key.
No. Password derivation (PBKDF2-SHA256, 120,000 iterations) and AES-256-GCM encryption execute exclusively inside your browser.
Visit /temp-mail-with-password from any browser, paste your saved tbx_pw_... key, enter your password, and click Unlock & Open.
AES-256-GCM authentication fails immediately and refuses to decrypt the underlying inbox token, keeping your messages private.
Yes. /temp-mail-with-password defaults to No Expiry (ttl: never) so your password-locked vault stays reopenable whenever you need it.
No — because encryption is strictly client-side and zero-knowledge, we cannot recover forgotten passwords. Keep your password in a password manager.
Need more answers? Browse all 29 topics in the Complete Tempboxy FAQ.