LinkVault

The problem wasn’t file security. It was payment timing. I rebuilt the flow.

Hey everyone,

A few days ago I posted here about building a secure “view-only” layer to prevent clients from downloading deliverables before paying.

That was the original idea.

But after more feedback (and thinking deeper about the actual problem), I realized something:

The issue isn’t file security.
It’s payment timing.

The real problem

Most freelance workflows look like this:

• You finish the work

• You send the final file

• You send the invoice

• Then you wait

And in that moment… you lose all leverage.

If the client delays, ghosts, or “forgets”, you're stuck chasing.

What I changed

Instead of trying to protect the file after sending it, I changed the flow entirely:

The client doesn’t get the file until they pay.

Not as a rule.
As a system.

How it works now

• I upload the deliverable

• The client gets a secure preview link

• They can review the work

• When they’re ready, they pay (Stripe)

• The file unlocks automatically

No manual checks. No follow-ups.

No payment → no access.

What surprised me

The biggest shift wasn’t technical. It was psychological.

Before:

“I hope they pay after seeing the file.”

Now:

“Access and payment are the same action.”

It removes that awkward gap where everything depends on trust.

This is not escrow (and not a marketplace)

I’m not trying to build another Upwork or Fiverr.

There’s:

• no onboarding for clients

• no disputes system

• no platform lock-in

It’s just a simple layer that ties file access directly to payment.

Why I’m posting again

This feels like a completely different product now.

Before:

• secure viewer

• anti-download

• DRM-style thinking

Now:

• payment-gated delivery

• Stripe-triggered access

• removing payment risk structurally

Curious how you handle this

How are you dealing with delivery right now?

• Do you send files before payment?

• Do you split milestones?

• Do you rely on trust?

And more importantly:

👉 Would you use something where the file only unlocks after payment?

If anyone’s interested in the technical side (Stripe webhooks, access control, etc.), happy to share more.

Link (if you want to check it out):
https://linkvault.biz

Hey everyone,

I’m a serial founder and mobile dev, and I’ve been burned too many times by the "trust model."

We’ve all been there: you send a "preview" of a video or a design, and the client suddenly goes quiet. Later, you find out they used a screen recorder or a downloader to grab your work without ever settling the deal.

I got tired of it, so I built LinkVault.biz.

The concept is simple: It’s a secure vault for your files. Instead of sending an attachment or a standard cloud link, you send a LinkVault link.

What it does:

• Zero-Download Previews: They can watch/view, but they can't save it.

• Anti-Screen Recording: Technical layers to make it harder to rip the content.

• Total Access Control: You can kill the link or lock the file the second a client starts acting "ghosty."

I’m currently opening the API for Professional and Enterprise users who want to integrate this protection into their own agency workflows or custom platforms.

I’d love the community’s "roast" on two things:

1. Is the landing page clear enough about the "Security" aspect vs. just being another cloud storage?

2. For those using an API for file management, what’s the #1 feature you’d look for in a security-first layer?

Happy to talk about the tech stack or the challenges of building a secure viewer if anyone is curious!