About ZapFile
Why We Built This
Honestly? We got tired of the same old story with file sharing services.
You know the drill - upload your file to some company's server, wait for it to finish, send a link, then the other person has to download it from that same server. Meanwhile your file is sitting on someone else's computer, maybe getting scanned, maybe being used to train some AI model, who knows.
File size limits. Download limits. "Upgrade to premium to share files larger than 2GB!" Pay walls everywhere. And for what? Your file is just sitting on a hard drive somewhere waiting to be downloaded.
We thought there had to be a better way. Turns out there is - WebRTC has been built into browsers for years now, but hardly anyone uses it for file transfers. So we built ZapFile.
What We Believe
Your files are yours. Not ours, not anyone else's. We have no business seeing them, storing them, or doing anything with them. That's why we don't.
Privacy should be the default, not something you pay extra for or opt into. End-to-end encryption isn't a premium feature - it's just how it works.
File sharing shouldn't be complicated. Pick a file, share a code, done. No accounts, no subscriptions, no BS.
If we can't see it, we can't lose it. The best security is not collecting data in the first place. No data breaches if there's no data to breach.
How We Make Money
Right now? We don't. This is a side project that costs us about $20/month to run (mostly server costs for the signaling service).
We might add some non-intrusive ads later, or maybe a "buy us a coffee" button. We've talked about offering premium features like custom room codes or transfer analytics, but only if we can do it without compromising the core privacy promise.
One thing we'll never do: sell your data or force you to create an account to use the basic service.
Who We Are
Small team of developers who care way too much about privacy and user experience. We've all worked at tech companies and seen firsthand how user data gets treated. Spoiler: not great.
ZapFile started as a weekend project to scratch our own itch. Turns out other people wanted the same thing.
Open Source?
We're thinking about it. The client-side code is pretty straightforward, and we'd love to get community contributions. The main hesitation is around abuse - if the server code is public, it becomes easier for people to spam or abuse the system.
But we're leaning towards yes. Transparency is important, especially for a privacy-focused service. Watch this space.
Get In Touch
Questions? Suggestions? Found a bug? We'd love to hear from you.
Contact us here or email us directly at [email protected]