Privacy Policy
flarePDF is built on a zero-knowledge commitment: your documents are processed directly on your device and are never sent to our servers.
Last updated: March 2025 • Effective date: January 1, 2025
1. Zero-Knowledge Processing Architecture
When you use any of flarePDF’s core tools (PDF Editor, Merge, Split, Compress, Organise, Convert, Sign), your files are processed in-memory using client-side JavaScript and WebAssembly executing within your browser tab.
- No document content or files are transmitted to any flarePDF server during processing.
- Files disappear from memory the moment you close, navigate away from, or reload the tab.
- You can verify this live via your browser’s Developer Tools Network inspector (learn more on our Security page).
2. Information We Do Not Collect
We never access, index, store, or sell any of the following:
- Contents of your uploaded PDFs, images, or documents.
- Text inputs, form signatures, or annotations created in the editor.
- Cross-site advertising tracking cookies or biometric data.
3. Information Handled Locally or for Service Operation
Depending on how you interact with flarePDF, limited operational information may be handled:
Local Browser Storage: We store minimal local preference flags (such as whether you have selected Dark Mode or Light Mode) directly in your browser’s localStorage. This data never leaves your device.
Server Logs: Standard web hosting infrastructure automatically logs basic technical request metadata (such as IP addresses, requested page URLs, browser user-agents, and timestamps) strictly for DDoS mitigation, caching performance, and error diagnostics. These logs never contain document data.
Optional Account Information: If you choose to register an account or subscribe to DocuSign Pro, we securely store your email address and authentication state. Billing is handled through certified PCI-DSS compliant payment providers.
4. DocuSign Pro & Electronic Signature Workflows
While flarePDF’s core tools are 100% client-side, users initiating certified multi-party signing workflows via our DocuSign integration utilize DocuSign’s compliant cloud infrastructure. Transmission is protected by 256-bit TLS encryption, and audit certificates comply with ESIGN, UETA, and eIDAS requirements.
5. Contact & Questions
If you have any questions regarding this Privacy Policy or wish to inquire about our data practices, contact us at [email protected].