Don't trust us. Check.
Every PDF site says “your files never leave your device.” The sentence is free to write and impossible to see. So instead of asking you to believe it, here are three checks you can run yourself in under a minute.
Check 1 — the airplane test (10 seconds)
- Open any tool on this site, for example the merger.
- Turn on airplane mode, or pull the network cable.
- Merge your PDFs. It works — because nothing was ever going to a server.
A tool that uploads your file cannot survive this test. Ours are ordinary static pages; after your first visit they are cached and run entirely offline.
Check 2 — watch the network panel (30 seconds)
- Press
F12(or right-click → Inspect) and open the Network tab. - Load a tool page, then process a file — a big one, so it would be obvious.
- Watch the request list while the tool works: no POST, no upload, no request whose size could possibly contain your file — during or after processing. The only requests you'll see are the page's own assets and small page-view analytics pings (more on those below), all a few kilobytes, none carrying your document.
Check 3 — the browser enforces it (for the skeptical)
Every page on this site is served with a Content-Security-Policy that limits where the page may send requests to a short, published allowlist: this site's own origin plus Google Analytics' endpoints. That is an instruction your own browser enforces — a hidden “backup service” or “error reporting” endpoint that receives documents simply cannot exist on these pages. And because there is no server-side processing, there is nothing for us to log, retain, or “delete after one hour”.
You can confirm the header in the same DevTools window: Network tab → click the page document → Headers.
What we deliberately don't have
- No accounts, no quotas that need to identify you, no cookies set by us.
- No file-related telemetry — we don't know what files you process, their names, sizes or contents, and the code to collect that doesn't exist here.
- No external fonts, tag managers or CDN scripts beyond the one analytics script below.
The honest edges
Here is the complete list of what does touch the network, so this page never overclaims. The site itself has to be downloaded once (that's the point of the web), and app updates fetch the same way. We run standard page-view analytics (Google Analytics and Vercel Analytics) to see which pages and guides people use — the same counters nearly every website runs. Those events contain the page URL, never anything about your files, and you can watch exactly what they send in the Network tab. The tools keep working with analytics blocked or offline — block them with any ad-blocker and nothing breaks. If we ever ship a tool feature that needs a network call of its own — say, trusted timestamping of signatures — it will say so on the tool, in front of the button, before anything happens.