Two web tools, one says "your data never leaves your device". This explains the privacy difference between local processing and cloud upload, when to choose local, and how to verify no upload happens.
Local vs cloud
Many online tools upload your file to a server, process it there and send the result back — meaning sensitive content (IDs, passwords, docs, recordings) leaves your device and may sit on someone else's disk. A local-processing tool does everything in your browser with JavaScript / Canvas / WebAssembly, so your data never leaves the device.
When to insist on local
Anything involving identity, finances, privacy or internal data should favor no-upload local tools.
How to verify no upload
- Check the copy for "local / no upload / works offline";
- Open DevTools → Network while processing; no large upload request usually means local;
- Look for a "clear local data" option;
- Be wary of tools that require sign-up or upload before giving results.
Limits of local tools
Local isn't magic: very heavy computation or huge files can hit browser limits, and cross-device sync or collaboration still needs a server. A sensible rule: process sensitive data locally, and use cloud services for non-sensitive collaboration after reading their privacy policy.