Security & Privacy
PDFHope security design, threat boundaries, and responsible reporting.
Local-first architecture
The production design serves the application through Cloudflare Workers Static Assets. Protect PDF, Unlock PDF, Sign PDF, Header & Footer, and other local PDF tools process selected documents in your browser; conversions between PDF and Word, Excel or PowerPoint use server endpoints.
Protect PDF uses local AES-256 encryption with an opening password. Unlock PDF requires a valid password; it does not recover or bypass unknown passwords. Passwords and signature images are not uploaded or saved by PDFHope. Sign PDF adds a visible electronic signature, not a certificate-based cryptographic digital signature.
Conversion uploads are limited to 20 MB, checked by extension, MIME type, and file signature, rate limited, and streamed to ConvertAPI with a server-only secret. Results use no-store response headers and zero-storage provider mode.
Scope and limitations
Client-side processing reduces server exposure but does not secure a compromised browser, extension, device, or third-party provider. Complex document parsers can contain defects, so dependencies and provider controls require regular review.
Report a concern
Send responsible reports to livenewsuson@gmail.com with steps to reproduce and impact. Do not include live personal data or confidential documents.
