Nothing is uploaded. Here is how to check.
Every online tool promises confidentiality. Here the promise does not have to be believed: it can be checked in thirty seconds, and this page explains how.
Three checks, in thirty seconds
Cut your network connection. Load a tool, then turn off Wi-Fi or unplug the cable. Drop a document in, merge, rotate, number, save. Everything keeps working, because everything was already happening on your machine.
Watch the “Network” tab. Open your browser's developer tools (F12), Network tab, then drop in a hundred-page file, reorder it, watermark it. Nothing goes out: no request, no background upload, no telemetry. Save, and you will see exactly one appear, `/compte?p=100`: the counter on the home page, which receives a number of pages. It weighs one line, and it is the only one on the whole site.
Read the content security policy. It is in the source of every page, and your browser enforces it. `connect-src 'self'` means the page cannot open a connection to any other domain: not a font provider, not a CDN, not an analytics tag. It is not a policy, it is a rule applied by the browser.
The one request, and what it carries
After an export, and only then, the page sends one request to this domain. It carries a number: how many pages were just processed. No byte of your document, no file name, no identifier, no cookie, not even which tool was used.
The server log for that endpoint writes two things: a date and that number. The format is in the repository, and a browser that asks not to be tracked sends nothing at all. We could have counted visits like everyone else; an analytics tag would have seen the page, the address, the device and the path taken, and none of that is needed to display “so many pages processed”.
What it changes for the GDPR
Your documents are never processed by us, since they never reach us. There is no processor to name, no transfer outside the European Union to declare, no retention period to set, and nothing to ask anyone to delete.
No cookie, no tracker, no third party, so no consent banner, because there is nothing to consent to. What a web server necessarily sees when you load a page (an IP address, a date, the page requested) remains true here as everywhere: that is how the web works, and it concerns the *page*, never your *documents*.
What we do not guarantee
This site does not make your computer safe, and it does not claim to.
- A tool is not an audit. Inspecting a PDF says what we were able to read in its bytes, not that the document is harmless.
- A watermark is not protection, and cropping a PDF does not erase what sticks out. Each tool says so on its own page.
- Redaction flattens the page into an image: what is covered is gone, but the page loses its selectable text.
- Everything happens in the memory of the tab. Past a hundred megabytes per file, the tab is what gives way.
- Signing here is not an electronic signature within the meaning of eIDAS: nothing certifies your identity or seals the document.
It works without us
The whole site is a folder of static files. It can be put on an intranet, a network share or a USB stick and it works unplugged: that package is what we sell, for organizations that would rather depend on no outside website at all.
Which is also the simplest answer to “what if this site disappears?”: nothing you did here depended on it staying up.