Your input is your business.

Local processing.

Developer data can contain credentials, internal addresses, source code and unfinished ideas. All published tools process input in your browser. Tool inputs, outputs and uploaded files are not sent to DevXTools or a third party.

What the application stores.

The application saves your color theme preference. Search queries, tool inputs and results stay in memory. Reset clears the workspace; leaving the tool releases its state. There are no accounts, input analytics, advertising scripts or session replay.

The browser still loads a website.

Your browser requests pages and assets. The hosting infrastructure can observe normal request metadata such as your IP address and the page you request. Browser-local processing does not mean anonymous browsing or guaranteed memory erasure.

Page statistics.

The production site loads Google Analytics automatically on all pages to measure use of public pages. There is no analytics prompt or settings button in this application.

Google receives public page names and addresses, basic browser information and network metadata such as your IP address. Page addresses exclude query strings and fragments; referrers, search text, tool inputs, results and files are excluded. Google Analytics may store first-party analytics cookies, such as _ga, to distinguish visits. Tool content is never stored in these cookies. Advertising personalization and Google signals are disabled. See Google's privacy policy.

Clipboard and downloads.

Clipboard access happens only when you select Paste or Copy. A denied permission does not trigger a server fallback; you can use the editor directly. Files you explicitly download and data you copy remain under your control outside this application; Reset does not delete those copies.

Future network tools.

Any future operation that requires a server must explain what will leave your browser and where it will go before transmission. It cannot use a local-only privacy label. No remote MCP connectivity is available. MCP tools validate or generate configuration locally; they do not connect to servers or execute commands.