GhostCase

Hi Indie Hackers,

I’ve always been uncomfortable with cloud-based “secure file sharing.” Even when tools claim zero-knowledge, you still need to trust accounts, servers, and infrastructure you don’t control.

I wanted something much simpler: encrypt files locally, share a single file, and be done. No uploads, no accounts, no backend trust.

That idea became GhostCase. It turns files into password-protected HTML vaults that work entirely in the browser. Everything happens client-side — the file you share is the only thing that exists.

The hardest part wasn’t encryption itself, but keeping the UX simple while adding constraints like time-based access or one-time viewing.

I’m curious: how do you handle sending sensitive files today? And would you trust a purely client-side approach like this?

For anyone curious, here’s the link: https://ghostcase.app

Hi Indie Hackers!

I’ve always been skeptical of cloud-based encryption where you have to trust a provider with your keys or account security. That’s why I built GhostCase.

What makes it different? Unlike traditional tools, GhostCase turns your files into standalone, self-extracting HTML vaults. It uses Go (Golang) and Wasm to handle everything 100% client-side. This means your data never touches a server, and you don’t even need an account to use it.

Key Features:

• Burn-on-View: The file disappears after being read.

• Time-Lock: Set a specific date before the file can be decrypted.

• Zero Knowledge: Total privacy by design.

I just launched on Product Hunt and would love to get some feedback from this technical community on the encryption speed and the UX.

Check it out here: https://ghostcase.app

Looking forward to your thoughts!