Last updated 5 November 2026
GigaJSON (the website, its tools and the browser extension) is built so that your data stays on your computer.
What we collect
Your documents are processed locally and are not uploaded to GigaJSON or its analytics providers. There are no accounts and no ads. Extension settings that use browser sync are described below.
The website sends usage statistics and error reports to Google Analytics to measure use and fix errors. The extension has a separate opt-in setting, described below. Website statistics include:
- pages visited and features used, for example "opened a JSON file of 10–50 MB", "switched to the Table view", "exported CSV" or "ran a jq query";
- clicks on website links and controls, including Chrome and Firefox install links, with the public page name, action and location on the page; sections viewed, scroll milestones, selected display options and demo results; editor controls and views, operation outcomes and timings, and file-size or result-count ranges. Editing fields report use without their text; individual keystrokes and pointer coordinates are not recorded. Tool search records whether a search was used and the number of results, never the search text;
- errors: the kind of error and where in GigaJSON's code it happened, without the error message;
- browser/device information and approximate location (from your IP address, which Google Analytics doesn't store); when you allow analytics cookies, a cookie identifier to recognise visits.
They never include a document's contents, its keys or values, file names, queries you write, or addresses of documents you import or pages viewed through the extension. We record public GigaJSON page paths and the destinations of links published on our website, without query strings or fragments. We count use of the Inspector’s open-link and email controls, but never record the destination address or link text.
Europe: in the EEA, the UK and Switzerland, the website sends nothing to Google Analytics until you allow analytics. A banner asks on your first visit.
Visit counts: every page also sends one request to GigaJSON's own counter on Cloudflare, so we know how many people visit when Google Analytics is blocked or not allowed. It records the page path, the country (from Cloudflare), the domain of the site that linked to the page, whether you came from a Google ad or a campaign link (its utm_source), mobile or desktop, and whether Google Analytics loaded, was blocked or was off. To count returning visitors, it keeps a random visitor ID in your browser's local storage and sends it with each count. Outside Europe the ID is created by default; in Europe only after you allow analytics. The ID is not a cookie, isn't shared with Google and isn't linked to your name, IP address or documents. Your IP address is used only to limit requests and is not stored. Turning analytics off (for example with "Reject all") stops this count and deletes the ID.
Your choices: analytics and ad measurement are separate choices. In Europe both start off. Elsewhere both start on, and you can turn either off. An earlier saved analytics choice still applies to analytics cookies only; it never grants ad measurement. You can use every feature if you decline either or both.
Ad measurement: if you allow it, Google Analytics and Google Ads can use advertising cookies and click identifiers to connect an ad click to an action on GigaJSON, such as opening a file, and report campaign conversions. We retain only Google's fixed acquisition parameters (gclid, dclid, gbraid, wbraid, gclsrc, gad_source and gad_campaignid) in the analytics page address. Other query parameters and fragments, including document-sharing data and hand-off tokens, are excluded. Personalised advertising and remarketing remain off.
Outside Europe, with analytics cookies off, Google's consent mode can still send cookieless measurement pings; cookie-based identification and advertising use follow your choices. Choices are saved on this browser and can be changed here or in the web editor's Preferences → Privacy choices. Withdrawing consent stops the tag using the affected cookies; it does not delete previously collected data.
Feedback: Once, the second time you use a tool or open a file, the website asks whether GigaJSON is working well for you. If you answer, we store "Yes" or "Not really", any text you type (up to 500 characters), the page's address without anything after it (for example /json-formatter/) and the country (from Cloudflare) in Cloudflare Workers Analytics Engine. Nothing from your documents is included, and your IP address is used only to limit requests.
What is stored, and where
In your browser, on your computer:
- documents you open in the GigaJSON app, and their saved versions, until you delete them;
- your settings, such as the theme and code colours;
- your separate analytics-cookie and ad measurement choices in local storage;
- a random visitor ID for GigaJSON's own visit counts (described above), outside Europe or once you allow analytics;
- Google Analytics cookies (
_ga,_ga_…) when you allow analytics cookies, and advertising cookies (such as_gcl_*) when you allow ad measurement.
The free tools keep nothing: what you paste or open there is gone when you leave the page. Clearing the site's data in your browser deletes everything above.
Network requests
- Your browser loads the site's files from the server that hosts it. Like any web server, it may keep standard access logs (IP address, time, page requested).
- The main website analytics script and measurement requests pass through GigaJSON’s gateway on Cloudflare to Google Analytics. The gateway forwards browser information and the connection’s IP address for the existing visit and approximate-location statistics; it does not log request bodies or forward unrelated site cookies. Google’s tag may also make a direct script-health check. Cookie choices still apply, as described above. Google's own use of that data is covered by How Google uses information from sites that use its services.
- Each page sends one visit count to
/api/von this site (Cloudflare), described above. It is stored in Cloudflare Workers Analytics Engine. - When you open a document from a URL, your browser downloads it directly from that address.
- Images, video and audio that a document links to are loaded only when you click "Load", unless you turn on automatic loading in Preferences.
The browser extension
The extension checks a page's content type and uses its address to recognise data files, apply site exclusions and label the viewer. It reads JSON, supported plain-text data files and optionally XML to display them locally. It also reads text you explicitly select for the editor. It does not scan your browser history or send viewed page addresses or document contents to GigaJSON or analytics providers. A link or URL you choose to open is downloaded directly from its source.
Documents saved in the bundled workspace stay in the extension's local browser storage until you delete them or uninstall the extension. Automatic-viewing, site-exclusion and XML preferences use the browser's extension-sync storage and may sync through your browser provider. Theme information, Chrome analytics consent and the analytics identifier are stored locally.
When you remove the extension, the browser opens a page on this site with the extension's version and browser name in its address. It asks why you removed it, and answering is optional. If you send the form, we store your chosen reason, any text you type (up to 500 characters), the version, the browser name and the country (from Cloudflare) in Cloudflare Workers Analytics Engine. Your IP address is used only to limit requests and is not stored.
Once, after you've opened a few pages in the viewer, the extension asks whether it's working well for you. If you answer "Yes", it links to the store's review page and sends nothing. If you answer "Not really", we store that answer, any text you type (up to 500 characters), the extension's version, the browser name and the country (from Cloudflare) in the same Cloudflare Workers Analytics Engine dataset. Nothing from the page you're viewing is included, and your IP address is used only to limit requests.
In extension version 0.1.1 and later, usage statistics are off until you enable "Share usage statistics" in the extension's options after reading the disclosure. Firefox also requires its optional data-collection permission. You can turn the setting off at any time and continue using every feature. Earlier draft Chrome version 0.1.0 enabled statistics by default; its old setting does not grant consent in 0.1.1.
After consent, the extension sends feature counts, selected display presets, operation timings and outcomes, format names, size ranges (for example "opened a 1–10 MB response in the viewer") and error types to help improve the viewer and editor. A random installation identifier is created locally only after consent and sent with those events to recognise repeat use. It is not your name or email address. Events contain no document contents, file names, viewed page addresses, query text or error-message text.
Extension statistics pass through GigaJSON's relay on Cloudflare before reaching Google Analytics. Cloudflare receives the connection's IP address. The relay uses a salted, daily-changing hash of that address to limit requests, does not log event bodies, and does not forward the visitor's IP address, cookies, user agent or referrer to Google. Cloudflare may keep standard service access logs. Statistics are dropped when offline, when consent is absent or when delivery fails; they are not queued.
GigaJSON's use of information received from Google APIs follows the Chrome Web Store User Data Policy, including the Limited Use requirements. Extension data is used only to provide, improve and secure its disclosed functionality. It is not sold, used for personalised advertising or used to determine creditworthiness. Transfers to Cloudflare and Google Analytics are limited to these disclosed operational purposes.
Changes
If this policy changes (for example, if the site starts showing ads), the new version will be posted here with a new date before the change takes effect.