Security
Last updated 12 November 2026
The safest place for a sensitive document is the device it's already on. That's why we built LocalPDF so your files never leave it.
No server copies
Files are never uploaded, so there's no server copy to leak or breach.
No accounts
No passwords or personal data stored, so nothing to steal.
Open and auditable
Anyone can review the code that handles your files.
How it's built
- All processing runs inside your browser's sandbox, on your device.
- There is no server-side file processing, no document storage and no user database.
- The app is served over HTTPS from our own domain.
- No advertising or session recording. Optional analytics (Vercel and Google Tag Manager) measure page views only — never your files.
- Processing libraries ship with the app instead of loading from outside sources at runtime.
Passwords in PDF tools
When you protect or unlock a PDF, your password is used only in memory in your browser to encrypt or decrypt the file. It is never transmitted, logged or saved.
Verify it yourself
- Open your browser's developer tools and watch the Network tab while you use a tool.
- Load the app, turn off your internet connection, and keep working.
Tips for sensitive documents
- Keep your original file until you've checked the result.
- After redacting, run the redaction checker to make sure nothing is still hidden underneath.
- On a shared computer, close the tab when you're done.
Reporting a vulnerability
If you believe you've found a security issue, please email hello@editlocalpdf.com with a description, the steps to reproduce it and the browser you used. Please give us reasonable time to fix it before sharing details publicly.
We welcome good-faith security research and won't pursue action against researchers who report issues responsibly.