Privacy policy

What happens to your files

Nothing on this site sends your files anywhere. When you drop a document into a tool, it is read by JavaScript running inside your own browser, processed by your own processor, and handed back to your downloads folder. The site is a set of static pages, and the single piece of server-side code behind it accepts one short message — the name of a tool that finished — and can do nothing with a file even in principle.

You can verify this rather than take our word for it. Open your browser’s developer tools, switch to the Network tab, and run any tool. You will see the page and its code load, one small request to /api/ops carrying the tool’s name and nothing else, and no request carrying your file.

What is stored on your device

One thing is stored locally, and only when you use it. If you follow a “next step” link to chain one tool into another, the intermediate file is held in your browser’s IndexedDB so the second tool can pick it up. It is claimed by that tool and deleted immediately, and any unclaimed leftover is discarded after thirty minutes. It never leaves your device.

If you change the theme, that choice is written to your browser’s local storage so the site does not start in the wrong colours next time. It is one word, it stays on your device, and clearing your browser data removes it.

There are no cookies. No accounts, no sign-in, nothing to log in to.

The operations counter

The footer shows how many files this site has processed for everyone who has ever used it. That number is the one thing here that is kept on a server, so it is worth being precise about how it is arrived at.

When a tool finishes successfully, the page sends a single request containing the tool’s name — “merge-pdf”, for instance — and nothing else. No filename, no file size, no page count, no setting you chose, no identifier of any kind for you or your browser. A counter is incremented and the message is discarded. A run that fails or that you cancel sends nothing at all.

It exists so we can tell whether the site is being used. It cannot tell us who used it, what they worked on, or anything that could be traced back to a person, because none of that is ever sent.

Analytics

The site uses Cloudflare Web Analytics, which counts page views. It sets no cookies, stores nothing on your device, and assigns you no identifier, so it cannot recognise you on a second visit or follow you to another site. What it records is the page address, the referring site, and coarse details your browser sends to every site anyway: country, browser and device type.

It measures pages, not files. The tools run entirely in your browser, and nothing about a file you open — its name, size, type or contents — is available to the measurement script or sent anywhere.

Server logs

Pages are served by Cloudflare, which like any web host records standard request information such as IP address, timestamp and which page was requested. This is ordinary infrastructure logging that happens before our code runs, and we do not combine it with anything or use it to build a profile. It contains no information about your files, because your files are never sent.

Third parties

No advertising networks, no social widgets, no embedded fonts loaded from elsewhere, no content delivery network beyond the one serving this site’s own files. Every byte the page loads comes from this domain, with one exception: the analytics script described above is served by Cloudflare. Nothing else is fetched from anywhere else.

Children

The site collects no personal information from anyone, of any age, because it collects no personal information at all.

Changes and contact

If this policy changes in a way that affects you, the change will be described here rather than buried. Questions can go to the address on the about page.