Privacy Policy

Privacy Policy — What Happens to Your JSON

The short version: it stays on your device. Here is the full, specific account of how the site works.

Last updated October 30, 2026

The short version.

jsons.site processes your JSONentirely in your browser. When you paste a document into any of the11 JSON tools, it is parsed and transformed by JavaScript running on your own device — it is never uploaded, never queued on a server, and never seen by us. There are no accounts, no cookies, no analytics and no advertising scripts on this site.

Where your data is processed.

Every operation happens locally, inside your tab. The only thing that crosses the network is the site's own static files:

Your browser
  1. Paste
  2. Parse
  3. Transform
  4. Render

Formatting, validating, repairing, diffing, minifying, converting to CSV, YAML or TypeScript, running a JSONPath query, building the tree view — all of it runs in this box. The only server involved delivers the page's files, which are static; there is no application server that could log your input.

The one deliberate exception

If you use the toolbar's fetch from URL action, your browser requests the URL you typed, directly from your browser to that address. That request never passes through jsons.site.

What is stored on your device.

Two things live in your own browser storage — and both stay there. Nothing else persists between visits.

  • localStorageTheme preferenceLight or dark mode — a single key, no identifier attached to it.To remove: Clear via site data in your browser settings.
  • IndexedDBFormatter history (optional)Up to 50 recent input sessions, only if you use the history feature.To remove: Delete per entry in the history panel, or clear all site data.

History is never synchronized anywhere — it is a convenience cache on your machine, nothing more.

What this site never collects.

Not on signup (there is none), not in the background, not ever:

  • Your JSON documents or any part of them — they never leave the tab
  • Accounts, email addresses or names — there is no sign-up
  • Cookies, analytics identifiers or advertising profiles
  • Third-party scripts, fonts or embeds — every asset is self-hosted
  • Keystroke logging, session replay or heatmapping

External links & policy changes.

Pages occasionally link to primary sources such as theJSON specification (RFC 8259). Following one of those links takes you to that site, which has its own privacy policy. If this policy ever changes, the update will appear on this page with a revised date; questions can be raised on the project'sGitHub organization — and if you're curious who builds this site or how it works, read theabout page. To see what all of this applies to, browse thefull JSON toolkit.

FAQ.

Is my JSON uploaded to a server?

No. Parsing, formatting, diffing, conversion and validation all run as JavaScript inside your browser tab. The document you paste is never transmitted, so no server ever receives it.

Does jsons.site use cookies or trackers?

No cookies, no analytics scripts, no ads and no third-party trackers. The only things stored on your device are your light/dark theme preference and, if you use the formatter's history feature, your recent inputs in local browser storage.

How do I delete the local history?

The formatter keeps up to 50 recent sessions in your browser's IndexedDB, on your machine only. Delete individual entries from the history panel, or clear all site data for jsons.site in your browser settings to remove everything at once.

When does a tool make a network request?

Only when you explicitly ask it to fetch JSON from a URL you provide — the request goes from your browser directly to that URL. Loading the page itself requests nothing beyond the site's own files, which are all self-hosted.