Skip to content

Privacy

What DevTools collects, what it does not, and exactly which tools send data to a server.

Short version: no accounts, no cookies, no analytics, no advertising, no third-party scripts. Most tools never send your input anywhere.

What runs where

68 of the 76 tools execute in your browser. Text you paste into them is processed locally and is never transmitted to us. These tools continue to work with the network disconnected, which is the clearest demonstration that nothing is being uploaded.

The remaining tools require a server and are labelled Server on their page:

For these, the value you submit (a hostname, IP address, password or image) is sent to our server, used to perform the lookup, and discarded when the response is returned. It is not written to a database and not retained. Uploaded images are parsed in memory and never stored on disk.

Server logs

The web server keeps standard access logs containing IP address, timestamp, requested URL and user agent. These are used to operate the service and to apply rate limits, and are rotated on a short schedule. They are never sold or shared.

Local storage

Your theme preference, favourite tools and recently used tools are stored in your browser's LocalStorage under keys beginning dt.. This data never leaves your device and is not readable by us. Clearing site data in your browser removes it permanently.

Cookies

DevTools sets no cookies of any kind. That is why there is no cookie banner.

Third parties

There are none. No CDN, no font service, no analytics, no error reporting, no embedded widgets. The Content-Security-Policy on every page blocks requests to any external host, which is enforced by your browser rather than only promised here.

Sensible caution

Even where processing is local, treat live credentials carefully. A JWT is a working credential until it expires. If you paste a real token, a real password or a personal photograph into any online tool - including this one - rotate or reconsider afterwards.