Browser Tool Data-Handling Guide

First ask where the input is computed, which resources are downloaded to perform that work, and whether the feature itself must contact an API. A JSON formatter can parse input with browser JavaScript without sending that string to a server. The page still downloads HTML, JavaScript, fonts, and other assets before it can run.

An AI background remover or upscaler can download a model and runtime, then run inference on the selected image inside the browser. The existence of traffic is not the deciding fact; determine whether the browser is receiving a model or transmitting image data. A public-IP check cannot be fully local because a server must observe the connection to report the public address.

In a Chromium-based browser, open DevTools and select Network. Load the target page once and let required models or other resources finish. Clear the log, perform the action with test input, and inspect only the rows added afterward. Check Request Method, Request Headers, and the Payload or Request tab, not only the URL.

Use recognizable dummy data such as test@example.com, sample-token, or a tiny solid-color image instead of a real secret. Search request bodies for that value or for file-like binary data. Model downloads are often large GET responses ending in onnx, wasm, or data, while uploads often use POST, PUT, or PATCH with a body. These are clues, not proof, so inspect the actual transfer.

No request during one action does not prove that every state is local. Another button, error-reporting path, export, share feature, ad, or analytics integration may behave differently. Cached resources may not be downloaded again, and a Service Worker can answer requests without the ordinary network path.

HTTPS protects traffic in transit, while DevTools can show the content before the browser sends it. The panel cannot tell you how a recipient stores or later uses received data. Review the privacy policy, destination provider, retention, and deletion controls as well.

Even without an upload, clipboard history, shared download folders, browser session restore, screen sharing, and untrusted extensions can expose content. For sensitive work, use an updated, trusted device and a controlled browser profile, then manage generated files and the clipboard after the task.

Local output is not automatically correct. File formats, character encodings, browser implementations, and device memory affect results and capacity. Keep the original, open the generated file in its target application, and use a checksum or diff when the workflow requires it.

The IP checker requests the Site API so it can report the public address and connection country. A breached-password lookup runs only after an explicit click: it hashes the password with SHA-1 and sends the first five hash characters to the Have I Been Pwned range API using k-anonymity. It does not send the password or complete hash, and a missing match is not a safety guarantee.

Background removal, image upscaling, and OCR download models, runtimes, Workers, or language data as needed. The selected input is designed to be processed in the browser, but high-sensitivity work should still be checked in your own Network panel and evaluated against device-side risks.