Privacy

Local processing

All 63 tools run in your browser using client-side libraries (pdf-lib, PDF.js, and similar). When you merge, compress, redact, OCR, or convert a file, the bytes are read and written on your machine. We do not operate a file-upload API for PDF processing.

What we never collect

• PDF contents, filenames from tools, or document metadata
• Passwords you type into Encrypt / Unlock
• Accounts, emails, or phone numbers for using the tools
• Advertising profiles built from your documents

Analytics

We use Google Analytics for anonymous page-view metrics and privacy-tool events (starts, completes, downloads on Privacy scanner, Auto-redact, and Confidential Send). Events never include PDF bytes, passwords, or filenames. You can block analytics with browser extensions or tracking protection; the tools still work.

Verify it yourself (Network tab)

1. Open DevTools → Network (filter: Fetch/XHR).
2. Run Auto-redact PII or Confidential Send on a sample PDF.
3. You should not see multipart uploads of your PDF to our servers. Heavy work stays in Web Workers / WASM on your device.
4. After install (PWA), many tools keep working offline.

That Network-tab proof is the best 20–40s demo when sharing mypdf with privacy communities (r/privacy, Indie Hackers, Show HN) — show the tool running with zero document upload.

Guides

• Redact PII from a PDF
• Send a PDF privately