Privacy proof
This page is a live test, not a policy document. Run a tool, watch the counters, and check the claim yourself.
Live counters on this page
What the counters mean
- Files uploaded — how many outbound requests carried file content. This number is the whole ballgame. It must stay at zero, and if anything ever tried, our own guard would block it and flag it in red.
- Outbound requests — any network activity the page initiated. Loading a stylesheet counts. Sending a file would count — which is why it must be zero.
- External requests — requests leaving privafile.net. We intend this to be zero, so nothing about you reaches a third party.
No accounts, no cookies, no tracking scripts
There is no login, no cookie wall, and no upload storage — because there is nothing to store. We do not sell, share, or retain your files: we never receive them in the first place.
Our intent is that tool pages make no third-party requests at all. The live counter above measures this on the page you are currently viewing, so you can check it rather than trust it. If that number is ever non-zero, something has been added to the site that we did not intend, and the counter is how you would catch it.
How we count visitors without tracking you
We do want to know roughly how many people use the site, so we count page views on the server, not in your browser. There is no analytics script on this page. The count is incremented when your browser asks for the page — a request it was making anyway — and your browser is told nothing extra.
What we store is a number, per day, per page. That is the whole record. We do not keep IP addresses, cookies, user agents, referrers, or session identifiers. Because nothing identifying is retained, there is no way to reconstruct an individual visit from our data — which is deliberate. It also means we can tell you how many visits a page received, but not who visited it, and that suits us.
We are hosted on a CDN and fronted by a server-side counter, so our infrastructure necessarily processes ordinary request metadata — your IP address and the page you asked for — in order to serve a response and increment a count. That is true of any website. What our host and counter never see, and cannot see, is the contents of your files.
Verify it independently — three ways
- Watch the counters above. Use any tool from this page. The uploaded-files counter stays at zero.
- Open developer tools. Press F12, go to the Network tab, clear it, then run a tool. Filter for "Fetch/XHR" and "Doc". You will see no request carrying your file.
- Go offline. Load a tool page, then disconnect your internet and use the tool. It still works — which is impossible if processing happened on a server.
What we would need for this to be false
It would require our own network guard to be bypassed. That guard wraps the browser's fetch API, XMLHttpRequest, and sendBeacon, inspects every outbound body, and rejects anything that looks like a file. Its source is readable here — you do not have to trust a summary of it.