How to check that an online file tool really keeps your files on your device

You can check whether an online file tool uploads your files by watching its network requests in your browser’s developer tools. A tool that works on your device does not send the file contents to a server while you work on them.

What to look for

An upload shows up as a request that carries the file inside its body, usually a POST with a size close to the size of your file. A page also loads its own scripts, styles and images, so you are looking for a request that holds your file, not for every request.

Steps

  1. Load the tool page first Open the tool while you are online and wait for the page to finish loading, so the scripts it needs are already downloaded.
  2. Open the Network tab Press F12, or Cmd+Option+I on a Mac, to open developer tools, then choose the Network tab. Press the clear button so the list starts empty.
  3. Process a file Add a file and run the tool. With Merge PDF, add two PDFs and press Merge PDFs. Wait until the result is ready.
  4. Read the list Look at the requests made after you pressed the button. Check the method and the size. Open a suspicious request and read its payload. A request that contains your file means the file left your device.
  5. Try it offline (optional) After the page has loaded, switch the browser to offline and run the tool again. A tool that works locally still produces the result. If it fails, that does not prove an upload happened. Load the page online again and retry.

What Keel sends

Keel counts page views with one small request to /api/hit each time you move to another page on the site. The body contains only the page path, such as /tools/merge-pdf. It does not contain the file name, the file contents, or the output of the tool. In the list you should see that beacon, and nothing that carries your file.

Why a check beats a promise

A privacy statement describes what a site intends to do. The request list shows what the page actually sent during your session. Repeat the check for any tool you use with sensitive documents, and treat a file that appears in a request as an upload.

Limits of this check

The check covers one session in one browser. It cannot show what a server does with data it never received, and it cannot prove that a page will behave the same way next month. Browser extensions can also make requests of their own, so check with the extensions you normally use turned off when the file is sensitive.

Try it: run this check on Merge PDF

Related

FAQ

What request does Keel send while I use a tool?

Only the small page-view beacon to /api/hit, which carries the page path. Your file is not in it.

Does a request with a large body always mean an upload?

Not always. Look at what the request carries. If your file is in the body of a request, the file left your device.

Do I need special software for this check?

No. Desktop browsers such as Chrome, Edge and Firefox include developer tools with a Network tab.