Security & privacy
End-to-end encryption
The secret is encrypted in the sender's browser with AES-256-GCM (Web Crypto API), using a random key generated locally. The key is placed in the link fragment (after #). Browsers never send the fragment to the server, so the server cannot decrypt what it stores.
What the server stores
- The encrypted blob (opaque; its length is rounded up to hide the exact size), its type (text/file/image), expiry time and view count.
- A salted hash of the IP address, used only for abuse rate limiting; it is deleted together with the secret.
- No cookies, no trackers, no analytics and no accounts. Nothing is stored in your browser either (no local storage).
Extra password
If you set a password, the content is also encrypted with a key derived from it (PBKDF2-SHA256, 600,000 iterations). Both the link and the password are required. For password-protected secrets, deletion after reading happens only after a successful decryption, so a wrong password does not destroy the secret.
Offline private note
In "Offline private note" mode nothing you type is sent to the server. The only request made asks the server for the current time, so that expiry cannot be bypassed by changing the computer clock. The string is protected only by its password and can be attacked offline, so the password must be strong (12+ characters; the generator makes 80-bit passwords). The expiry is a courtesy check, not a guarantee.
Limits
- The recipient can copy or screenshot the secret while it is displayed.
- Anyone with the full link can read the secret; send it through the most direct channel you can.
- A read or expired secret cannot be recovered.
- If an attacker controls the sender's or recipient's device, no encryption helps.
Link previews
Links can be previewed in chat apps without consuming the secret: the receiving page requires an explicit click before any data is downloaded.