Privacy & security
Last updated
Security built into every step — and described precisely, so you can check it. This page explains where your data goes when you use each tool.
Where processing happens
| Tool | Runs | Data sent to our servers |
|---|---|---|
| All PDF tools (merge, split, compress, organize, edit, convert, protect, unlock, stamp) | In your browser (Web Worker) | None |
| File converter and document editor | In your browser | None |
| Image compressor, resizer and converter | In your browser (Web Worker where supported) | None |
| Salary and paycheck calculators | In your browser | None |
There are no server-side upload or processing endpoints. Pages and the code that runs the tools are downloaded from our host like any website; after that, your files are handled entirely on your device. You can confirm this by opening your browser’s developer tools, selecting the Network tab, and processing a file: no request carries your document.
What is retained
- Files, outputs and passwords are kept only in the tab’s memory while you work, and are released when you start over, leave the page or close the tab.
- Temporary preview and download links (browser “object URLs”) are revoked after use.
- Nothing you process is written to cookies, local storage or IndexedDB.
Third parties
- Hosting: serves the website and processes standard request logs (IP address, browser, URL). It never receives your files.
- Analytics: not enabled.
- Advertising: not enabled. If it is enabled later, note that any advertising script runs inside the page.
- Fonts and libraries are self-hosted; no CDN sees which tool you use.
Protections in place
- A strict Content Security Policy that only allows our own origin plus explicitly enabled services; frames, plugins and form posts to other sites are blocked.
- File type checks based on file contents, not just extensions, plus size, page-count and pixel limits.
- Uploaded SVG and HTML are sanitized before use; scripts never run.
- PDF passwords are never placed in URLs, logs, analytics or storage. Incorrect passwords are rejected without automatic retries.
- Document restrictions set by a PDF’s author are respected. We do not crack or bypass passwords.
- Spreadsheet exports neutralize formulas in CSV cells to prevent formula-injection attacks.
- Dependencies are checked with
npm auditbefore each release.
Limits you should know
- Local processing protects your files from our servers, not from your own device. Malware or untrusted browser extensions on your computer can read web pages, including this one.
- Very large files are limited by your device’s memory; a tab can run out of memory and reload.
- PDF permission settings are advisory: some software ignores them. A password is the real protection.
- Covering text in the PDF editor does not remove it from the file.
Tips for sensitive documents
- Use a private browsing window and close it when done.
- Protect PDFs you share with a long, unique passphrase and send the password through a different channel.
- Remove document metadata before sharing (Compress PDF → Remove metadata).
Found a vulnerability? Please report it via our contact page.