How to how to check a tool does not upload
- 1. Open the network panel before you drop a file.
- 2. Run the tool and look for a request to any other origin.
- 3. Disconnect and run it again. It should finish.
Open the browser’s network panel, filter it, and note the origins before you add a file. Add a PDF and run the tool. New requests should stay on the same site, and they should be the app’s own files if any are still loading, not a POST of the document to an API. Then repeat with the network disabled after the ready state. A tool that passes both checks is not uploading. A tool that shows a progress label “uploading” has told you the truth. Ignore badges. A privacy policy is not a network log. This site expects to pass that test; if you ever see a document POST, treat it as a bug and stop using that build.
How to check a tool does not upload stays on this device. The download is the copy you keep, and Weesize does not store a second one. Close the tab when you are finished and the bytes are gone.
Questions
Does “How to check a tool does not upload” upload my file?
Performing the check does not require sending the PDF anywhere first.
What will “How to check a tool does not upload” actually change?
You are looking at requests, not at marketing copy. A document body in a request is a failure.
When is “How to check a tool does not upload” the wrong job?
A same-site request for the app’s script is not an upload of your file. A request that contains the file is.
How do I check the result of “How to check a tool does not upload”?
If you find a file upload, do not continue with a confidential document in that tab.
Can I run “How to check a tool does not upload” with Wi-Fi off?
The offline half of the check is decisive even if you do not enjoy the network panel.