Privacy
Last updated . This page describes exactly what JSON Bench stores and what it transmits. It is short because the tool does very little.
Your JSON documents are never uploaded
JSON Bench has no backend, no API and no upload endpoint. Anything you paste into the editor, drop onto
it as a file, format, explore, query, diff or convert is processed by JavaScript running inside your own
browser tab - most of it inside a Web Worker that contains no networking code of any kind. Files you drop
are read with the browser's own FileReader, which reads from your disk into the tab and
makes no network request. There is no code path in this application that sends document content
anywhere, and you can verify that: the source is served unminified and the network panel of your
browser's developer tools will show no request carrying it.
What is stored on your machine
JSON Bench sets no cookies. It writes two entries to localStorage, which is storage that
belongs to your browser and never travels with a request:
-
json-bench:v1- an object with two parts.settingsholds the panel you had open, the indent width, whether Sort keys was on, the query mode and the last query text, the conversion target, the CSV delimiter and BOM options, the TypeScript root type name, and whether the diff was showing unchanged rows.documentsholds the text of the last document in the editor and, if you used the Diff panel, the text of the left and right documents - stored only when a document is one million characters or smaller, so a very large file is never written to disk by this page. -
json-bench:theme- the stringdarkorlight, so the page does not flash the wrong theme on your next visit.
The Clear button on the Format panel empties every editor and deletes the
json-bench:v1 entry. Clearing site data in your browser removes both entries. A service
worker also keeps a copy of the page's own files - the HTML, the stylesheet and the scripts - in the
browser cache so the tool keeps working offline after the first load. That cache holds only the
application's files. It never holds your documents.
What is transmitted
One thing, and it is not your data. The page loads a web-analytics SDK (Tencent RUM) which reports
anonymous technical information about the visit: page load and paint timings, resource load timings,
JavaScript errors, the browser and operating system as the browser reports them, and a traffic-channel
label derived on first paint from the referring page and any UTM parameters in the URL - for example
search / google, ai / perplexity, social / reddit, or
direct. That label exists so the people who published this build can tell how visitors
found it. No document content, no query text, no file name and no field value from anything you paste is
attached to any of those reports.
No personal data is collected. JSON Bench has no accounts, no sign-in, no email field and no form that asks you for anything about yourself. If you would rather send nothing at all, a content blocker or an offline session stops the analytics request without affecting any feature of the tool - every panel works with the network switched off.
Third parties
The analytics SDK is fetched from a content delivery network, so that CDN and the analytics endpoint see your IP address and user agent as they would for any web request. No other third-party script runs on this page, and there are no advertising, tracking-pixel or social-embed scripts anywhere in it.
Children
JSON Bench is a developer utility with no accounts and no personal-data collection, so it is not directed at children and does not knowingly collect information from anyone.
Contact
This build was generated and deployed with Quodara. Questions about it belong on the case page: quodara-ai.com/showcase/json-bench.