Security at PDFPUMA

The safest file upload is the one that never happens. Here's how PDFPUMA is designed.

Documents stay on your device

All current tools process files in your browser, in an isolated background worker. Files aren't sent to our servers.
Files are checked by their contents, not their names, and damaged or unexpected files are rejected with a clear message.
Encrypted PDFs aren't modified, and PDFPUMA never bypasses passwords or document permissions.

Served over HTTPS with a strict Content Security Policy: scripts and workers load only from PDFPUMA itself and the sign-in service.
The site can't be embedded in other websites (clickjacking protection).
No third-party advertising or tracking scripts.

Sign-in is handled by Firebase Authentication. Every account request is verified on the server; your plan is decided on the server from Stripe's records, never by your browser.
Database rules ensure customers can read only their own records, and billing records can only be written by the server.
Deleting an account requires signing in again.
Payments are processed by Stripe; card details never reach PDFPUMA. Stripe notifications are verified by signature before they're trusted.

If you believe you've found a security issue, please contact us through the details on the privacy page. We appreciate responsible disclosure.