What stays in the browser
On a tool marked as locally processed, the transformation or calculation runs with browser APIs and JavaScript already delivered to the tab. For example, an image converter can decode a selected image, draw it to a canvas, and create a new downloadable blob without posting the source file to an upload endpoint. A text counter can segment pasted text in memory without sending the text away for counting.
MyTool0 exposes this distinction on the relevant tool page. If a future tool requires remote processing, that behavior should be disclosed before the data is sent rather than hidden behind the same “local” wording.
What loading a website still involves
Visiting a website creates network requests for documents and assets. Hosting and security systems can therefore receive technical request information such as an IP address, requested URL, time, browser details, and security signals. That is different from uploading the file selected inside a local tool.
The current privacy policy describes those categories separately so “nothing is uploaded” is not misread as “no network metadata exists.”
Temporary browser objects are still data
Local tools may hold text, decoded pixels, generated blobs, or object URLs in memory while a tab is open. Clearing the workspace or closing the tab removes ordinary in-memory state, but operating systems, browsers, extensions, clipboard history, downloads, and backups have their own behavior. Treat highly sensitive material according to the security rules of the device you are using, not only the behavior of one webpage.
How to inspect the claim yourself
- Read the tool's privacy note and supported limits before selecting a sensitive file.
- Open browser developer tools and inspect Network while running the operation.
- Look for requests triggered after the file or text is provided, not only page-load requests.
- Check whether the tool works after the page assets are loaded and the network is disabled.
Local processing is useful because it reduces an important class of data transfer. It is not a promise about every component of the device, browser, hosting provider, or future site configuration.