Privacy-first PDF tips, guides, and product updates.
Encrypt a PDF with AES-256 encryption in your browser — no upload required. Here's why AES-256 matters and how to do it in under a minute.
Read more →Uploading PDFs to cloud tools triggers GDPR data processing obligations. Client-side tools avoid this entirely — here's how to stay compliant.
Read more →Processing PDFs with PHI requires HIPAA-compliant tools or a signed BAA. Client-side processing eliminates the requirement entirely — here's why.
Read more →Adobe Acrobat Online uploads your files to Adobe's cloud. For confidential documents, that's a problem — here's what to use instead.
Read more →ILovePDF uploads your files to remote servers and has a history of XSS vulnerabilities. Here's what that means for your documents.
Read more →Smallpdf uploads your files to Google Cloud. Here's what that means for your privacy, and what you can do instead.
Read more →We built PDF tools that process everything in your browser. No server. No upload. No trust required. Here's why.
Read more →Online PDF tools can put attorney-client privilege at risk. Here's what bar ethics rules say, and which tools lawyers can safely use.
Read more →We removed Google Analytics and replaced it with Umami. Here's what we track, what we don't, and why it matters for a privacy-focused tool.
Read more →Privacy claims are easy to make. We open-source our code so you can verify ours. Here's what to check, and why verifiability matters more than promises.
Read more →From server uploads to fake redaction, these PDF security risks are common, underestimated, and easy to avoid once you know what to look for.
Read more →Most PDF tools upload your files to remote servers. This guide covers the tools that process everything locally — no upload, no server, no risk.
Read more →The WiFi test is the only honest proof that a PDF tool isn't uploading your files. We pass it. Most tools don't. Here's why that matters.
Read more →