Privacy by architecture, not by promise
pdfnoupload is built so that violating your privacy is impossible, not merely against policy. Here's exactly how it works and how you can verify it.
There is no upload endpoint
Traditional PDF services upload your file to a remote server, process it there, and send it back. That means your document — and everything in it — sits on someone else's computer. pdfnoupload has no such server. The processing code is downloaded to your browser once, and from then on your files are read, transformed and saved entirely on your own device.
How the processing actually happens
Lightweight operations like merging, splitting and rotating use pdf-lib, a pure-JavaScript library running in your browser. Heavier jobs — compression, OCR — use WebAssembly engines that also run locally, inside a Web Worker so your interface stays responsive. None of these ever open a network connection to send your file anywhere.
Verify it yourself in 20 seconds
Open DevTools (F12 or right-click → Inspect), go to the Network tab, then process any file with any tool. Watch the request list: you will see the app's own assets load, but not a single request that uploads your document. You can even disconnect from the internet entirely after the page loads and every tool will keep working.
What we do and don't collect
We use privacy-respecting analytics to count page views and tool usage so we know which tools to improve. Analytics events never contain your file or its contents. We never see, store, or transmit your documents — there is no mechanism in the product that could.