I run 0807, a file host I host myself.
You drop a file, you get a short link, and you choose when it disappears.
I am posting it here because the whole thing is built around privacy, and because I would rather lay out the real threat model than call it "secure" and let you find the gaps later.
The privacy side:
- No account, no sign up. An upload is not tied to any identity.
- No ads, no third party trackers, no analytics. Nothing is loaded from outside domains, so no fonts or scripts phoning home.
- The server does not log IP addresses or requests. The rate limiter holds an IP in memory for a few minutes to count requests, then forgets it. Nothing is written to disk.
- Reachable over Tor through an onion service.
- Auto delete by time (one hour to thirty days, or never) or after a chosen number of downloads.
- Optional password on files and on text notes.
- Files up to 20 GB.
- Executable types like exe, bat and scripts are blocked so it cannot be used as a malware drop.
The honest part, which this community will and should ask about:
it is not end to end encrypted. The server can read what is stored, on purpose.
I want to be able to remove illegal uploads when they get reported, child sexual abuse material above all. A server that cannot see its own contents cannot act on those reports, and I am not willing to run one that cannot.
So I gave up that form of secrecy in exchange for being able to take that content down.
What that means for you in practice the password is casual access control, not protection from me as the operator or from anyone who breaks into the server.
If you need real confidentiality, encrypt the file on your own machine before uploading and share the key separately.
Treat 0807 as a way to move files around with self destructing links and no account, not as a vault for secrets you cannot afford to expose.
It is open source, and I host the code on my own server instead of GitHub, so there is no third party in that loop either.
You can read every line check the no logging claim yourself suggest a change, or open an issue all without an account:
Questions and criticism welcome. If you think the encryption tradeoff is the wrong call, I will read the argument
Very cool. Glad you're still working on it.
You can implement end-to-end encryption and simply delete anything that was flagged as csam, even without validating that it is. Do you really want to see that shit? No. So are you really going to spend the time validating before deleting? I know I wouldn't.
The worst that would happen is you'd end up deleting someone's actual file because someone else maliciously reported it. And it would have to be someone who knew the link was even there to find it and report it. That's a pretty unlikely scenario for a temporary file share.