How to verify that tool input is not uploaded

This guide helps developers confirm the privacy claim by watching the browser Network panel while a tool runs. Use a fake sample, not real sensitive data, when testing any web tool.

Step-by-step verification

Open a tool page, such as JSON Formatter.
Open your browser developer tools.
Go to the Network tab.
Enable Preserve log if you want to keep all requests visible.
Click the clear button in the Network panel.
Paste a harmless fake sample into the tool editor.
Run the tool and watch for new network requests.
Click any request that appears and inspect the payload, query string, and request body.

What you should expect

You may see requests for static JavaScript chunks, the favicon, manifest, or future analytics/ad scripts if enabled. You should not see your sample JSON, CSV, XML, YAML, JWT, Base64, URL, or text content being sent to a backend endpoint for tool processing.

What would be suspicious?

A request body that contains the exact text you pasted.
A query string that includes your pasted sample.
A POST request to a processing endpoint immediately after clicking the tool action.
A share/save URL that stores your result online.

Important limitation

This check confirms behavior in your current browser session. If the source code changes in the future, repeat the check. Also remember that browser extensions, corporate proxies, and other installed software may observe page content independently from this website.

Next step

Read the privacy architecture page to understand how the browser-side workflow is designed.

Read how privacy works