How privacy works

What in your browser means

Every tool here is a program that runs on your device. The heavy parts, the image codecs, the PDF engines, the OCR engine, the MP3 encoder, are compiled to WebAssembly and downloaded once from this site, like any other part of the page. When you drop a file, the browser reads it into memory and hands it to a Web Worker, a background thread that works while the page stays responsive.

The file stays in that memory, is processed there, and the result is written to a new file in your Downloads. No server takes part: the site has no address that accepts files.

How to verify it yourself

You do not have to take our word for it. Under every result a counter shows the bytes transferred while the tool worked; it reads 0 B. For a stricter check, open the browser's developer tools (F12), go to the Network tab, run a tool on a real file and look for a request the size of your file. There is none.

Stricter still: load a tool page, go offline and run it again; it still works. The guide Check that a tool does not upload your files walks through both checks, and our test suite runs a network guard that fails the build if any request carries file data.

What the site does collect

No cookies, so no cookie banner; no advertising or tracking scripts; no third-party scripts at all. The site keeps anonymous, aggregated counts on its own server: how many times each tool ran per day, the language, the country, whether the run succeeded, how long it took and a rough size bucket. Page views are counted by a self-hosted, cookie-free instance of Umami.

When a tool fails, the browser sends an anonymous error report with any file name removed, kept for 90 days. Text you type on the request page or in the feedback box is stored so we know what to build. The privacy policy lists every column.

Offline, after the first load

A service worker keeps a copy of the site's pages and engines in your browser. After you have opened a tool once, it opens again without a connection, on a train or with mobile data off, and works the same, because nothing in it needed a server in the first place. The copy contains the site's own files only, nothing of yours.

The site can also be installed as an app from the browser's menu; that is the same cached copy with an icon. Clearing the browser's site data removes it, and the next visit downloads it again.

What this means for the GDPR

The GDPR governs personal data; a file that never leaves your device is not processed by us, so there is nothing to consent to, transfer or delete on our side. The counts we keep are anonymous and cannot be linked to a person. The one place where you can give us personal data is text you type in a request or in feedback, which you can ask us to remove; the About page says who operates the site and is responsible for it. This is a plain description of how the site works, not legal advice.