Security, in plain language
Every file is encrypted in your browser before upload. Simple and Private access differ in who controls recovery.
ZeroLatch manages recovery so authorized owners and recipients do not need a separate code.
This is not zero-knowledge: after authorization, the application can technically recover the key for this delivery.
You hold a recovery code that ZeroLatch never stores.
If the code is lost, the files cannot be recovered by you, your recipient, or ZeroLatch.
Confirm the address now, or keep it private and verify access through the delivery link later.
ZeroLatch asks you to check in before any safety period can complete.
Release links are random, purpose-specific, stored as hashes, and expire.
Files use AES-256-GCM authenticated encryption in the browser. Stored file objects are ciphertext.
Simple deliveries store a wrapped content key protected by the server-side managed-key boundary. A valid release token and correct delivery mode are required before the key can be requested.
Private deliveries derive access from a browser-generated recovery code. The recovery code itself is not stored by ZeroLatch.
Encryption reduces risk; it does not make any online service invulnerable. Database, application, email, device, and storage compromise are different risks. Use Private access when preventing ZeroLatch from recovering the content matters more than easy recovery.