How to Prove a Web Tool Runs on Your Device

"Secure." "Files deleted after processing." "Your privacy matters." None of these tell you whether your bank statement was uploaded to somebody's server. Here is a test that does, and it takes half a minute.

The test

1. Load the tool's page and wait for it to finish loading.
2. Turn off your wifi, or unplug the network cable.
3. Use the tool.

If it works, nothing was being sent anywhere. It cannot be, there is no connection. If it fails, your file was going somewhere. This is conclusive in a way that no privacy policy is.

The more precise version

Open your browser's developer tools, go to the Network tab, and load a file. An upload is a request carrying your document's bytes; it is impossible to hide from that panel. If no such request appears, none was made.

Where the wording gets slippery

"Processed in your browser" is sometimes used for tools whose browser makes a request to a server. Technically the browser did it. Practically your file left.

"Deleted after processing" concedes the upload happened. Retention policy describes what happens next, not whether it went.

Scanned files often take a different path. Reading a scan needs OCR, which is heavy, so a tool that handles digital PDFs locally may send scanned ones to a server. That can be a reasonable engineering trade, but "never leaves your device" stops being true the moment it happens, and the honest thing is to say which files take which route.

Why it matters for these documents specifically

A bank statement is close to a complete profile of a person: employer, address, shopping habits, travel, rent. A closing packet holds full legal names and identifiers for several parties at once. A customer address list is other people's data that you are responsible for.

For a holiday photo, upload convenience wins easily. For these, it is worth spending thirty seconds to find out.