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 tracking, no accounts, no analytics scripts
We do not run third-party analytics on tool pages. There is no login, no cookie wall, and no upload storage — because there is nothing to store. If we ever add a measurement tool, it will be mentioned here and on the page where it runs, and it will never receive file content.
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.