I Built BurnLink Because My Paranoia Was Justified

Confession: I got hacked. many times. This is what came after.

First breach: 2019. Got the notification email like everyone else. Password was there. Changed it everywhere (or thought I did). Still have no idea if it's floating around somewhere.

After the first breach, I got angry. Not at the hackers. At the system.

Why are we still emailing passwords? Why do we trust Google to delete things? Why is our only option "hope nobody gets hacked"?

So, I Built BurnLink. Not As a Feature. As Rage.

We didn't design it in a conference room. We designed it in a panic room, 3am, after firing someone who shouldn't have had access to credentials that shouldn't have existed in the first place.

The rule was simple: If I can't verify it's deleted, I won't use it. That's it. That's the entire philosophy.

What That Actually Looks Like:

Client-side encryption — I needed to know the server couldn't read it
Single-use links — I needed to know the damage was contained
60-second auto-delete — I needed to know nobody had time to copy it
Open source — I needed proof from strangers on the internet that I wasn't lying

Not because it's trendy. Because I've been breached way too many times and I'm not doing it again.

Here's The Weird Part

Building this made me realize: I was the problem.

Not the tools. Me. I was trusting the wrong people with the wrong data in the wrong ways.

BurnLink doesn't fix trust issues. It just makes them visible. And if you can see the problem, maybe you stop pretending it doesn't exist.

So What Is This?

It's not a startup. It's not a lifestyle business. It's not trying to raise funding or exit.

It's a tool I built because I had to. Open source. MIT licensed. You can deploy it on your own server if you don't trust me (you shouldn't).

Use it for:

  • Passwords that shouldn't exist

  • Credentials that should burn

  • Secrets that need to disappear

  • Things you're too paranoid about

Don't use it for:

  • Things you need to keep

  • Things you need to prove you sent

  • Replacing actual security practices

What I Actually Want

I don't want your money. I don't want you to be my customer.

I want you to look at how you're sharing sensitive data and ask: "Am I insane for trusting this?"

If the answer is yes, try BurnLink. Audit the code. Break it. Tell me what's wrong.

Build your own version. But please please stop emailing passwords. Stop trusting companies that say they'll delete your data in 30 days. They keep backups. They have logs. You can't verify any of it.

Visit :
Github :
MIT License (actually yours, not mine)

P.S. — If BurnLink gets hacked, you'll know immediately. Because we'll tell you. Because we're not hiding from it. That's the difference.

founder of

179 views

Add a comment

Replies

Best

this hit hard because i went through something similar recently 😭 watching accounts get accessed in real time permanently changes how you think about “temporary” security compromises and trust

 Man, I feel that. There's nothing like watching it happen in real-time to make you realize how fragile everything is. Once you've seen the access logs, once you've realized someone else was in your account doing stuff, the concept of "temporary" anything becomes a joke. You can't unsee it.

That's exactly why I built this. Not as a feature. As a way to stop trusting temporary measures.

Glad you're thinking about this stuff now. Most people don't until it's too late.

 yeah that experience permanently changes how you think about security honestly

 Absolutely. Once you’ve watched it happen in real time, “temporary” security stops feeling temporary. It changes how you trust people and tools after that.

 yep, 100% agreed on this