Privacy by architecture
FoldPDF never sees your files
Most "private" tools ask you to trust a company's promise not to look at your documents. FoldPDF is built differently: the processing engine ships to your device, so there is nothing to trust. This page explains exactly how — and how to verify it yourself.
There is no upload
Traditional PDF sites receive your file, process it, and (hopefully) delete it. FoldPDF can't leak what it never receives: your document is read into browser memory with the File API and processed by WebAssembly code served once with the page.
We can't see your files even if we wanted to
There is no server-side processing endpoint. No file data is included in any network request. Open DevTools → Network while processing a file and watch: zero payload transfers.
It works offline
Once the page is loaded, the PDF engine (pdf-lib + pdf.js/WASM) runs without any connection. Turn off your Wi-Fi mid-task and everything still works.
Passwords never leave either
The Protect tool encrypts your PDF locally, and the Unlock tool decrypts locally. Your password is used in memory on your device and is never transmitted, stored, or logged.
Results download from memory
Output files are created as in-memory Blobs and handed to you via a local download. When you close the tab, everything is gone — there is no cache to subpoena.
What we do collect
Nothing personal. No accounts, no analytics, no cookies for tracking, no fingerprinting. If we later add anonymous aggregate usage counters, they will be opt-in and documented here.
Verify it yourself in 30 seconds
- Open any tool and press F12 → Network tab.
- Drop in a file and run the tool.
- Watch the requests: no file bytes leave your machine.