Share secrets once. Then they disappear.
One-time, end-to-end encrypted links for passwords, API keys, and files. Everything is encrypted in your browser — the server only ever stores ciphertext, and it's deleted after a single reveal.
- Zero-knowledge
- AES-GCM in browser
- One-time reveal
- Auto-expiry
- Open-source API
Create a one-time secret link
Paste the secret, choose when it expires, then send the link.
Share an encrypted file
Files are encrypted locally, then deleted after download or expiry.
Click to upload or drag and drop
Original and encrypted payload must each fit under 2 MB.
The encrypted file is deleted after this time or after the first download.
3. Create link
Advanced settings
Get an email when the file is accessed. Your address is stored until access or expiry and shared with the mail provider for delivery.
How SnapPwd protects your secrets
Security detailsEncrypted before upload
A random AES-GCM key is generated and the secret is encrypted in your browser. Only ciphertext is sent.
Server never receives plaintext
The decryption key lives in the URL fragment after #, which browsers never send to the server.
Deleted after first reveal or expiry
The payload is removed the moment it is read, or when the expiry you set elapses — whichever comes first.
Open-source API and CLI
The API, CLI and self-hosted web client are MIT-licensed on GitHub. Read the encryption code or self-host the whole stack. The hosted app's code is not public.
No account required
No sign-up or email required. Optionally request an email when your secret is accessed.
Human reveal confirmation
Links wait for an explicit click, so link scanners and chat previews can't silently burn a one-time secret.
How it works
- 01
Paste & encrypt
Enter a secret and set an expiry. It is encrypted locally before anything leaves the page.
- 02
Share the link
Send the generated URL. The key is in the fragment, so the server never sees it.
- 03
Reveal once
The recipient clicks to decrypt in their browser. The payload is then deleted for good.