The hidden risk of online PDF tools
When you drop a PDF into iLovePDF, Smallpdf, or Adobe Acrobat Online, your file gets shipped across the internet to one of their servers. Once it lands, their software processes it, the result sits on disk for a few minutes, and then — they say — it's deleted.
'Temporarily' is doing a lot of work in that sentence. During that window, your document is on hardware you don't own. It might be in backups. It might be in a log. It might be intercepted in transit. An employee with the right access could open it. And 'deleted' is a promise, not a technical property — you're trusting their policy, not the architecture.
For a kid's soccer schedule, none of this matters. For a contract, a medical record, a tax filing, or anything with someone's SSN on it, it matters a lot.
How browser-based tools are different
Browser-based tools like PrivacyScanPDF run entirely as JavaScript inside your tab. The PDF is read into your browser's memory, manipulated on your CPU, and offered back to you as a download. There's no network round-trip with the file in it.
No server processes your file. No temporary storage. No 'we delete it later.' The impossibility is the guarantee — a browser-based tool literally cannot see your files, because the code that does the work is running on your machine, not theirs.
How to verify a tool is truly private
Pull your internet connection mid-operation. If it still completes, the tool is browser-based. If it fails, your file was being shipped off somewhere.
Or, less destructively: open DevTools (F12) → Network tab, then run the operation. If you see a request carrying your file's bytes to a third-party domain, it's uploading. If the only network traffic is the page itself loading, it's local.
You can also look at the source for libraries like pdf-lib or pdf.js. Their presence is a strong hint that real work is happening client-side.
When server-based tools might be acceptable
Server-based tools aren't evil. They're necessary for jobs that need compute your laptop can't provide — high-volume OCR on a 2,000-page deposition, say, or signing with a hardware HSM the browser can't touch.
The key is informed consent. Know what you're uploading. Trust the provider. Don't upload anything you wouldn't cc to a stranger. For everything else, use a browser-based tool.