Joy G. Majumdar

BurnLink — The Ashtray For Your Secrets

We built something weird: an ashtray for digital secrets. Throw the password in, light it once, and watch it go. No smoke. No evidence. Just a little click and it’s gone.

Why this exists

  • People still email passwords, paste keys in Slack, and trust “we’ll delete it later.” That trust is why things get leaked.

  • BurnLink flips the script: make sharing fast, then make the trace disappear.

What it does (in plain terms)

  • Encrypts in your browser — the server never sees plaintext.

  • Produces a single-use link — download once, it’s deleted atomically.

  • Detects unfurlers and serves a neutral preview so bots don’t accidentally burn links.

  • Optional password + rate limits + Turnstile for extra safety.

  • Open source & self-hostable — run it where you actually trust it.

A tiny story (so it lands):
At 2AM my pager screamed. A contractor who should’ve been gone still had prod API keys. I rotated keys, cursed, and by 3AM I’d hacked together something that let me share a secret without leaving a copy. That angry little script became BurnLink.

If you care about minimizing blast radius

  • Use BurnLink for one-time credential handoffs, emergency shares, and any file that shouldn’t live in backups.

  • Don’t treat it as storage. Treat it as a fuse.

Try it: https://burnlink.page
Fork it: https://github.com/Joy-Majumder/BurnLink

“Share it once. Let it disappear.”

34 views

Add a comment

Replies

Best
Thomas G

I love that you made it open source and that the server can't see the content of the secret! It makes BurnLink trustable.
But I'm thinking: you're saying that you got the idea of BurnLink because a former contractor still had API keys. However I don't see how BurnLink could have prevented that from happenning: if you sent the API keys to the contractor using BurnLink, he could still save the API key locally on his machine when opening the link (and probably will save it if the API key is needed for daily work). The original link being unavailable doesn't prevent that. Am I correct, or did I misunderstand something?

Naim Azoutar

This is good, sharing secrets that disappear removes a lot of risk from leaks and mistakes. Simple flow, but very useful for teams handling sensitive data.