Security

Local processing

All PDF operations run in your browser. This significantly reduces the attack surface compared to a server that receives your document, because there is no upload step and no server-side storage of your file.

Untrusted file handling

Every PDF you open is treated as untrusted input. Before parsing, files are checked against the actual PDF file signature (not just their extension). PageFlow does not execute embedded PDF JavaScript, and does not automatically open external links found inside a document — you're warned first.

Password handling

Passwords used for the Protect and Unlock tools exist only in memory during that operation. They are never transmitted anywhere, never written to browser storage, and never included in analytics or diagnostic information.

Browser limitations

Browser-based processing has real limits: very large or unusual PDFs may exceed available memory, and some advanced PDF constructs may not be fully supported. When a document can't be safely processed, PageFlow aims to fail with a clear, safe error rather than a silent or misleading result.

No absolute guarantees

No system — ours included — can promise absolute security. We apply a strict security posture (input validation, filename sanitization, a restrictive content security policy, and dependency auditing) but encourage you to keep sensitive documents' final review as your own responsibility.

Reporting a concern

If you believe you've found a security issue, please contact support@pageflowpdf.com.