1. Fundamental Architecture: Zero Document Collection
At PDF Protector (accessible via https://pdfprotector.app), we believe the only truly secure data is the data that is never collected.
Unlike conventional PDF converter websites that upload files to backend cloud servers, PDF Protector executes 100% of document processing on your local client device. All encryption, password hashing, and PDF byte construction are performed in your local browser sandbox via WebAssembly and JavaScript.
- We do not upload, transmit, or store your PDF documents on any server.
- We do not see, record, or store the passwords you choose.
- We do not log document metadata, file titles, or page counts.
2. Data Ingestion & Network Requests
When you drag and drop a PDF file into PDF Protector:
- Your operating system grants the browser permission to read the file into local memory (RAM).
- No HTTP POST, PUT, or WebSocket transmissions containing file contents are initiated.
- When you close or refresh your browser tab, all temporary in-memory objects are immediately purged by the browser's garbage collection.
3. Cookies and Local Storage
PDF Protector uses minimal client-side localStorage strictly to persist your chosen visual theme preference (Light or Dark mode). We do not utilize tracking cookies, profiling beacons, or third-party marketing trackers.
4. Institutional Compliance (GDPR, HIPAA, CCPA)
Because PDF Protector never acts as a Data Processor or Data Controller for your documents, organizations subject to GDPR (General Data Protection Regulation), HIPAA (Health Insurance Portability and Accountability Act), and CCPA (California Consumer Privacy Act) can use PDF Protector without executing third-party Data Processing Agreements (DPAs).
5. Questions Regarding This Policy
For privacy inquiries or technical auditing questions, contact our security team at:
privacy@pdfprotector.app