Plain-language privacy
Your documents are not our data.
PrivatePDF is built around a simple boundary: for local tools, your document bytes stay inside your browser. We provide the tool; your device does the document work.
What travels over the network
Your browser downloads the application code, fonts, and interface assets needed to run PrivatePDF. During local PDF operations, the selected document itself is not sent to a processing server.
- No account is required
- No filenames, document text, signatures, or form values are collected
- No document bytes are attached to errors or analytics
What stays on your device
Source files, generated previews, passwords, and outputs stay in browser memory unless you explicitly download the result. Source documents are not persisted by default.
- Clear Files Now removes the active local job
- Temporary object URLs are revoked after use
- Outputs are generated and reopened locally
How to verify the claim
Open your browser developer tools, switch to the Network panel, select a small sample PDF, and run a tool. You should see application assets—not a request containing the PDF. Filtering by Fetch/XHR makes the check easier.
Future online services
If a future feature genuinely requires a server—such as recipient e-signature delivery or high-fidelity Office conversion—it will be clearly marked as an online, opt-in tool before file selection. It will never be silently substituted for a local operation.
Ready when you are