TamingShare
Share passwords and secrets with self-destructing links
Share securely. Share once. Share gone.
A password sent by email stays in both mailboxes until someone deletes it.
Why a link
Two ways to send the same password
Two example emails: one with the password typed into the message, readable in both mailboxes until deleted, and one with a TamingShare link that is deleted once the reader clicks through its warning page.
Anyone who gets into either mailbox can read it for as long as the email is kept.
Opening it shows a warning page first. The secret is deleted once the reader clicks through, and the link stops working when it expires.
What you get back
A link to send, and a receipt to keep
Creating a secret gives you two links: one for the reader, and a receipt you keep for yourself.
Two illustrations: the link, shown with its expiry and its burn-after-reading setting, and the receipt, marked Active while the secret is still on the server and Burned once it has been destroyed.
Send this one. Everything after the # is the key, and browsers never send that part to us.
Keep this one. It says whether the secret is still on the server, and it has the button that burns it early.
How it works
Built to be forgotten.
Every secret is encrypted in your browser before it ever leaves your device. We never see your data, and neither does anyone else.
End-to-end encryption
Your text is encrypted with AES-256 in your browser. The key lives in the link, never on our server, so the data is unreadable to us.
Burn after reading
Flip one switch and the secret self-destructs the moment it is opened. No second view, no recovery.
It expires on its own
Set a lifespan from 5 minutes to a year. When the clock runs out the ciphertext is deleted, opened or not.
Zero-knowledge by design
For each secret we store the encrypted text, when it was created, when it expires and whether it burns. The key never reaches us, so nothing we hold can be read. Our database does not store your IP address. The rate limiter keeps a salted hash of it and clears that about a day after your last request.
A receipt for every link
When you create a link you also get a private receipt. It shows whether the secret is still on the server and when it expires. You can burn it early from there. Once the secret is gone, the receipt cannot tell you whether it was read, burned or expired.
The flow
Paste. Share. Gone.
Share sensitive information without leaving a trail in your email, chat logs, or ticketing systems.
Paste your secret
Drop in a password, API key, or private note. Pick an expiry and, optionally, burn-after-reading.
- Passwords & login credentials
- API keys & access secrets
- Private notes & sensitive messages
- Recovery codes, 2FA backups & PINs
Share the link
You get one encrypted link. Send it over email, Slack, or text. The link itself carries the key, so nothing readable reaches our server.
Gone after viewing
Once it is read or expires, the secret is permanently deleted. No one, including us, can bring it back.