Privacy, written as a list of facts
Most privacy pages are promises. This one is an inventory: what the site does with a file, what it does with a visit, and what it cannot see even if it wanted to.
A file you drop in is never transmitted
The file is read by JavaScript running in the tab you are looking at. It is parsed, the metadata is removed, and the cleaned copy is handed back to your browser's download mechanism. At no point is it sent over the network.
This is not only a policy, it is a restriction the browser enforces. The site's Content-Security-Policy allows the page to connect only to this domain and to one analytics endpoint. A script that tried to post your photo somewhere else would be blocked by the browser before it left the tab. You can confirm it in the network panel: drop a file, and no request appears.
What is recorded, and by whom
| Thing | Collected? | Detail |
|---|---|---|
| Account or email | No | There is no sign-up and no form that accepts an address |
| Cookies set by this site | No | No scripts on the page write cookies, and nothing is kept in local or session storage |
| Advertising or retargeting | No | No ad network, no pixels, no third-party scripts beyond the one below |
| Page views | Yes, in aggregate | Cloudflare Web Analytics: no cookies, no fingerprinting, used to see which pages get read |
| Your IP address | Seen by the CDN | Every website on earth sees this in order to answer you; Cloudflare terminates the request before it reaches the files |
Where this claim stops
The site's own files live on a server. Your documents never do. Cloudflare serves the HTML and the scripts — that is why the CDN sees a request at all. Your documents are a different matter: they are read in the tab and never become part of a request, so there is nothing on the server for anyone to retrieve, subpoena, or leak.
A browser extension can see more than the page can. Extensions you install can read pages and, in some cases, files you open. That is outside this site's control, and it is the single most common way a "local" tool stops being local.
A saved copy behaves like any local file. If you save this page and use it offline, the processing happens on your machine with no network at all — the strictest version of the same guarantee.
Nothing, because there is nowhere for it to go
No contact form, no upload endpoint, no comment field, no API. The site is a folder of static files; there is no application server behind it. If you want to inspect the claim rather than read it, open the network panel, or read the scripts — they are small and unminified.
What this page is not
It is not a legal document drafted for a jurisdiction, because no personal data is collected to have a jurisdiction over. If a tool here ever needs an account, this page will change before the feature ships, not after.