Privacy
The short version: nothing you enter into a tool on this site is stored, logged or shared. Today every tool does its work inside your browser, so there is nothing to keep even if we wanted to.
What happens to what you enter
Whatever you enter is not stored, logged or shared. That is the commitment, and it holds regardless of how a given tool is built.
As things stand, every tool here does its work inside your browser. When you paste JSON into the formatter, generate a password, or decode a JWT, that happens on your own machine and no request carrying your input is made at all. If a tool is ever added that genuinely needs a server - a DNS lookup, for instance, which cannot work any other way - its page will say so plainly, and the request will still not be retained.
This is a property of how the tools are built rather than a promise about how data is handled after collection: there is no collection step to trust. You can confirm it yourself by opening your browser developer tools, switching to the Network tab, and watching that nothing is sent as you type.
The practical consequence is that it is safe to use these tools with material you would not normally paste into a website, such as production API responses, access tokens, or unpublished text.
Advertising, analytics and cookies
There are no user accounts, so there is nothing to sign up for and no profile associated with you.
This site shows advertising through Google AdSense, and loads Google Tag Manager. Both are third-party scripts served from Google's servers. Everything else the pages need is served from this domain.
Those Google scripts can set cookies in your browser and report your visit to Google, which uses that data under its own policies rather than ours. This site sets no cookies of its own, and your language is decided by the address you are visiting rather than by anything stored on your device.
There is no session recording and no heatmapping, and nothing you type into a tool is passed to Google or anyone else - see the first section.
Third-party vendors, including Google, use cookies to serve advertising based on your previous visits to this site or to other sites on the internet. Google's use of advertising cookies enables it and its partners to serve ads to you based on that history.
You can turn off personalised advertising from Google entirely at www.google.com/settings/ads. To opt out of the use of cookies for personalised advertising by many vendors at once, see www.aboutads.info/choices, or www.youronlinechoices.com for the European equivalent. Opting out does not remove advertising; it makes what you are shown less specific to you.
What is saved on your device
One tool can save data on your own machine, and only if you ask it to. The wheel spinner has a checkbox that remembers your list of entries so you do not have to retype it. It is off by default.
That list is kept in local storage, which belongs to your browser on your device. It is never transmitted, so this site never receives it and never sees it. It is not a cookie and is not sent with any request.
Untick the box, or use the Forget it link beside it, and the saved list is erased immediately. Clearing your browser data removes it too. Because it is stored locally rather than in an account, it will not follow you to another browser or another device.
No other tool on this site stores anything, and nothing you enter into any tool is ever sent to us.
What a web server necessarily sees
Being honest about the limits of the above: any web server records basic technical information about the requests it receives. That includes your IP address, the page you asked for, the time of the request, and the browser and operating system your browser reports.
This is standard server logging that happens before any page code runs, and it applies to every website you visit. It does not include anything you type into a tool, because that never leaves your browser to become part of a request.
Cloudflare
This site is served through Cloudflare, which acts as a network in front of the origin server for performance and protection against attacks. Requests therefore pass through Cloudflare before reaching the site.
As part of that, Cloudflare may set a bot-management cookie and processes technical request data such as IP addresses. That processing is governed by Cloudflare, not by this site. Their privacy documentation describes what they retain.
Changes to this page
If the site ever starts doing something this page does not describe, such as adding analytics, this page will be updated before that change ships. The date below reflects the last revision.
Last updated:
