Don’t take our word for it — check
Claiming “we don’t upload your files” is cheap. Here are three ways to confirm it, in increasing order of paranoia. All of them use tools already built into your browser.
1. The aeroplane test (10 seconds, no technical knowledge)
- Open any tool, for example Merge PDF, and wait for it to finish loading.
- Turn off Wi-Fi, or switch the device to flight mode.
- Use the tool. Merge two PDFs, convert a photo, generate a QR code.
It works. Software that uploaded your file could not possibly work with the connection off. This is the whole argument, and it needs no expertise to run.
2. The Network tab (30 seconds)
- Press F12 (or ⌥⌘I on a Mac) and select Network.
- Press the clear button so the list is empty, then load your file into the tool and run it.
- Read the list. You will see requests for the tool’s own code the first time — JavaScript, a WebAssembly module, perhaps a font — and after that, nothing.
Sort by Size and look for anything outgoing that is as large as your file. There is nothing to find: every request is a GET for our own static assets. There is no POST, because there is no endpoint to post to — this site is a folder of static files on a rented server, with no upload handler at all.
3. Read the code (as long as you like)
The pages are plain static files. Use View source, or the Sources panel in developer tools, and read what the tab is running. The heavy lifting comes from open-source libraries you can recognise and check yourself — pdf.js, libheif, ffmpeg, Tesseract — all listed with their licences on the licences page.
What we do collect
The web server records the ordinary access log every web server records: which page was requested, when, from which IP address and with which browser. That is how we know which tools are worth improving. It contains no file names and no file contents — the files never reach the server, so they cannot appear in a log. There are no cookies, no analytics script, no fingerprinting and no third-party tags on these pages.