How to verify our privacy claims
We are not asking you to trust us. Here are four ways to check it yourself, today, with no technical knowledge.
Four tests you can run
1. Turn off the internet and keep working
- Open the tool while online and wait for «Ready to use offline» under the workspace.
- Turn off WiFi and mobile data.
- Drop a PDF and process it: compress, merge, split or convert.
- Download the result.
If your file were uploaded to a server, none of this could work offline.
2. Watch the live meter
- Below the workspace there is a meter: “Sent to servers”.
- It counts any cross-origin resource and any data call (fetch, XHR or beacon) the page makes.
- Process a file and watch it: it should stay at 0 bytes.
3. Open your browser's inspector
- Press F12 (or right-click → Inspect) and open the “Network” tab.
- Filter by “Fetch/XHR”.
- Drop a file and process it.
- No request carrying your document will appear.
4. The browser enforces it, not our word
- The site ships a Content-Security-Policy header that includes connect-src 'self'.
- That means the browser blocks the code's connections to any other domain.
- We also set frame-ancestors 'none' and form-action 'self'.
The CSP does not stop the whole page from navigating elsewhere. That is why the PDF code also carries no external URL, and an automated test fails if anyone adds one.
What does leave your device
- The initial page download: HTML, CSS, JavaScript and fonts, served from the CDN. Same as any website.
- Nothing from your file. Not its contents, not its name, not its size, not a summary.
- There are no ads and no analytics: no third-party network is connected, and if one were, the CSP from proof 4 would give it away.
Where the work happens
- Your file opens in the browser's memory and is processed in a Web Worker: a separate thread, same origin, inside your own processor.
- We use pdf-lib and PDF.js (Mozilla), both open source, running on your machine.
- You can cancel any job midway. Close the tab and nothing remains.