Privacy policy: what happens to the data you paste
What this site does and does not do with data, and what third-party advertising may set.
This privacy policy explains how this site handles data. In one sentence: the content you type into a tool is not collected, not stored and not transmitted. The rest of this page breaks that down, and also describes the cookies that third-party advertising may set.
Last updated: September 26, 2026. If this policy changes in a way that matters, that date will be revised and the change will be described on this page, so that the version you are reading stays accurate about what the site actually does.
What you type into a tool
Every tool here — JSON formatting and validation, conversion, encoding, hashing, regex testing, timestamp conversion — does its work in the browser. No part of the code sends your input to this site or to any third party. The consequences are worth spelling out: this site cannot see the API response you pasted, cannot read the JWT you decoded, and does not hold the plaintext behind a hash you computed, so it cannot log, index, sell or leak any of it. This is verifiable rather than a promise. Disconnect from the network and keep using an already-open page: everything still works, which would not be possible if the input had to reach a server. The browser's own developer tools show the same thing — open the network panel while using a tool and no request carrying your input will appear.
What is stored on your device
So that a refresh does not wipe work in progress, the most recent input is saved in the browser session storage, which the browser clears when the tab or window is closed. A few interface preferences — the light or dark theme, and whether you dismissed the language suggestion — are saved in local storage so they survive a later visit. None of it is transmitted anywhere and no server can read it. You can remove all of it by clearing site data in your browser settings, by using a private or incognito window, or by pressing the Clear button inside a tool. This site sets no first-party tracking cookies of its own.
Third-party advertising and cookies
Display advertising pays for the domain and the hosting. Ads are served by third-party networks such as Google AdSense, and those networks may set cookies or read device identifiers when you visit this site, in order to measure impressions, detect fraudulent or repeated clicks, and select ads that are more likely to be relevant to you. Two limits are worth stating precisely. First, this site cannot read the contents of those cookies; they belong to the ad network, not to this site. Second, the identifiers they contain cannot be connected to what you type into a tool, because that input never leaves the browser in the first place. If you would rather not receive personalized advertising, you can turn it off on the ad settings page provided by the network that served the ad — Google publishes one, reachable from the information link attached to its ads and from your Google account settings — and you can also block third-party cookies in your browser's privacy settings. Neither step affects any tool: everything on this site works with ads blocked.
Traffic statistics
This site may use a traffic statistics service to understand how many people visit each tool page, which is how decisions about what to improve are made. Those statistics are aggregate. They typically cover the page address, the referring link, browser and operating system type, a coarse region and the time of the visit. They never contain anything you type into a tool, and they cannot be used to identify a specific person — a statistics service of this kind reports numbers, not individual sessions.
Frequently asked questions
- Can this site see the JSON I process?
- No. All parsing, formatting, conversion and hashing is performed in your browser, and there is no endpoint that receives those contents. You can confirm this yourself with the browser developer tools: open the network panel and use a tool — no request carrying your input is made.
- Why does a tool site need a privacy policy at all?
- For one thing, when a site shows third-party advertising, the ad networks require it to disclose how cookies are used. For another, a privacy policy is how anyone judging an online tool decides whether it can be trusted. For a developer who has production data on the clipboard, knowing that the input is never uploaded matters more than one more feature.
- Can I use an ad blocker?
- Yes. This site does not detect ad blockers and does nothing to work around them; with ads blocked, every tool functions exactly as it does otherwise. Revenue depends on those ads, so adding this site to an allowlist is the best way to support it if the tools are useful to you — but that is your choice, not a condition of using them.
- Can I request a copy of my data, or ask for it to be deleted?
- There is nothing on this side to export or delete. This site has no accounts, no user profiles and no personal information about you; tool input never reaches it, so there is no stored copy to hand over. The only copy of your recent input and preferences lives in your own browser, and clearing site data removes it. If the question comes from a privacy law such as the GDPR or the CCPA, the practical answer is the same: there is no personal data held here to disclose or erase. Data held by ad networks, or by other sites you visit, is governed by their own policies; this site does not receive that data and cannot act on it.