The core risk: the upload
The moment a tool uploads your document, a copy exists on a server you do not control. That copy can be logged, cached, scanned, retained longer than you expect, or exposed in a breach. For a throwaway flyer this rarely matters. For contracts, IDs, tax forms, medical records, or anything with personal data, it is the whole ballgame.
What to check before you upload
- Does it upload at all? Open your browser's Network tab and watch when you add a file. A large outbound request means it is leaving your device.
- Is there a clear retention policy? Look for how long files are kept and whether they are deleted automatically.
- Is it HTTPS? Encryption in transit is the bare minimum; it protects the upload but not what happens on the server.
- Does it demand an account? Requiring sign-in to edit a file ties your documents to an identity and a profile.
The safer alternative: on-device tools
Client-side tools sidestep the entire risk. They read your file straight into your browser's memory and process it there, so nothing is ever transmitted. There is no server copy to leak, no retention policy to trust, and nothing left behind once you close the tab.
You can verify it yourself: load a client-side tool, turn off your Wi-Fi, and it still works. That's the clearest possible proof your file isn't going anywhere.
How PDFNEO handles your files
PDFNEO never uploads. Every tool — password protection, compression,merging, and the rest — runs entirely in your browser. Files are processed on-device and discarded from memory when you leave. Read the technical detail on thesecurity page or ourprivacy policy.