Your files never leave your device. Verify it.

How local processing works

The local tools are built on open-source engines compiled to WebAssembly: pdf-lib for page operations, pdf.js for rendering, qpdf for encryption and Tesseract for OCR. Your browser downloads the engine once, then processes your file inside the tab's memory. There is no upload endpoint in these tools — the code to send your file to a server simply does not exist.

Verify it in 2 minutes

1. Open a local tool, then open your browser's developer tools (F12) → Network tab.
2. Process a PDF. You will see no request containing your file — only the initial page/engine downloads (and nothing at all if already cached).
3. Or: load the tool page, disconnect from the internet, and process a file. Local tools keep working offline.

What about the AI tools?

AI translation, summary and Q&A need server-side AI compute. Even then, your PDF file is never uploaded: your browser extracts the text locally and sends only text strings. Results are returned to your browser and the rebuilt document is created locally. We do not store your text after the response is sent.

Account data

We store your email, password hash (PBKDF2), credit balance and a ledger of credit transactions. We do not store your documents — we never receive them.