Privacy Policy

Last updated 20 May 2026

Short version: JSON never leaves the browser. There is no server component, no upload step, and no account system — no third party has access to the JSON documents processed on this site. The rest of this page covers the specifics.

— S., [email protected]

What data I collect

None that identifies you. jsontoolskit.org is a static site. Every tool on this domain processes your JSON entirely in your browser using JavaScript and WebAssembly. Nothing you drop, paste, or open is transmitted to my servers, because there are no servers handling your file content.

What I don't do

No accounts or sign-up — ever.
No analytics scripts (no Google Analytics, no Plausible, no Mixpanel, no Hotjar).
No tracking cookies. The site does not set any cookies at all.
No advertising pixels.
No selling, sharing, or licensing of anything, because there's nothing to sell.

Third parties that see your IP

Your browser loads a few assets from third-party CDNs so the site stays small and fast. Those hosts necessarily see your IP address:

Google Fonts — fonts.googleapis.com and fonts.gstatic.com, for the Geist and JetBrains Mono fonts.
jsDelivr — cdn.jsdelivr.net, for the libraries loaded on demand by individual tools (Ajv, js-yaml, jq.wasm, papaparse, jsonrepair, jsonpath-plus, fast-json-patch, json-schema-faker, quicktype, etc.).
Your hosting provider (for jsontoolskit.org) can see standard web-server access logs: IP, user-agent, URL, timestamp. I don't use these logs for anything beyond debugging outages and keep them only as long as the host retains them by default.

None of those third parties see the contents of your JSON documents, because the content never leaves your browser. The library files are static JavaScript / WebAssembly downloads.

Local storage

The tools currently do not write your JSON to localStorage, sessionStorage, or IndexedDB. The site stores only your light/dark theme preference under the key theme in localStorage. Clear it from the browser dev-tools any time.

Contact

Privacy questions or concerns: [email protected]. Happy to take a bug report if you spot anything on this site that calls home and shouldn't.