Your files never leave your device. Here's how to check.
We don't ask you to trust a privacy policy. The architecture makes uploading impossible, and you can verify every claim below yourself.
The 30-second verification
- Open any tool page, e.g. the PDF merger.
- Turn off your wifi (or enable airplane mode). If it's already loaded, the page keeps working — merge, compress, redact, everything.
- Or: open your browser's developer tools → Network tab, then process a file. You'll see zero requests while your document is processed. Nothing to a server, nothing to a CDN, nothing to an analytics pixel — because none of those exist here.
How it works
This site is static files: HTML, JavaScript and WebAssembly. When you pick a file, your browser reads it into memory and the processing libraries (the same kind of engines desktop apps use, compiled for the browser) do the work on your machine. The result is handed back to you as a download from your own memory. Our hosting serves the app and can't do anything else — there is no API, no database, and no endpoint that could accept a file even if we wanted one.
Enforced, not promised
- A Content-Security-Policy header (
connect-src 'self') instructs your browser to block this site from contacting any other server. Even a bug or a compromised dependency couldn't exfiltrate your file past it. - No analytics, no cookies, no third-party scripts, no external fonts. View source.
- The service worker caches the whole app on first visit, which is why it works offline afterwards.
- The only thing ever stored is your license key (if you buy one) in your own browser's localStorage.
What we can't protect you from
Honesty matters more than marketing: we can't protect against malware already on your device, a compromised browser, or you sharing the output with the wrong person. And for redaction specifically — always review the verified output before distributing it. Software has bugs; our verification report exists so you never have to take even our word for it.