Privacy Policy
Last updated: October 2026
JSONDiffHub ("we", "us") operates jsondiffhub.com. This page explains what data we handle and the choices you have. The short version: both JSON documents you paste is processed on your own device and never leaves your browser.
What this policy applies to
JSONDiffHub is a JSON diff tool: it compares two JSON documents and shows added, removed and changed values in a visual diff. In practice, it walks both object trees in parallel, aligning keys rather than line numbers, so a reordered key is not reported as a change and a nested edit is located by its path instead of by its position in the file. This page should be read with that tool in mind, because the limits described apply to what it computes.
Everything the tool works with — both JSON documents you paste — is handled locally. It is usually reached for things like finding one value buried in a large payload, and because nothing is transmitted a visitor can close the tab knowing no copy was made anywhere.
Data you give the tool
This site has no backend that receives what you type. The page reads your input to compute an answer, shows it to you, and forgets it — because nothing was ever sent anywhere in the first place. The arithmetic is identical regardless of who is looking at the screen.
Cookies, ads and advertising partners
The only cookie we set ourselves is a small preference flag for the consent notice. Advertising is served by third parties, and those partners may place their own cookies to tailor the ads you see. You can refuse or clear them in your browser without losing any functionality — the tool itself has no dependency on cookies.
What our statistics cover
Where analytics are enabled they record aggregate usage only — page views and approximate region. We do not build individual profiles, and analytics providers are never given access to what you enter into the tool.
The snippets you drop in
Anything you paste — a payload, a token, a configuration file — is processed in the browser. There is no upload step, which is rather the point: a private key stays exactly as private as it was before you pasted it.
Retention and security
Because your inputs are never transmitted, there is no store of personal measurements to retain or protect. Standard security practice applies to the site itself, including HTTPS on every page.
Children
The site is not designed for, or marketed to, children under 13, and we do not knowingly collect their personal information.
The rights you have
Regional privacy law may grant you rights of access, correction, deletion or objection. Write to us to exercise them: because most of what the tool handles never reaches a server, there is rarely anything on file to act on.
When this policy is revised
If the way we handle data ever changes, this page will be revised and the date at the top adjusted accordingly. Continuing to use the site after an update means you accept the revised policy.
What is collected automatically
Delivering a page necessarily produces some technical detail at the edge: an IP address, a browser string, the path requested and when. JSONDiffHub uses that only to serve and protect the site. It is not stitched together with whatever you enter into the tool.
Getting in touch about privacy
Questions about this policy can be sent through the contact page.