Privacy Policy — JSON Tree — Viewer & Export

Last updated: September 2026

What the extension does

JSON Tree — Viewer & Export detects when the page you're viewing is a raw JSON response (by inspecting the page content, not the Content-Type header) and renders it as a collapsible, searchable tree. It also offers export to CSV/YAML/TypeScript, JWT decoding, a JSON diff tool, and a local history of recently viewed JSON pages.

Data collection

This extension does not collect, transmit, or sell any personal data, browsing history, or page content to the developer or any third party. There are no analytics, no remote servers, and no external network requests made by the extension itself.

The only data stored is kept locally on your device, using Chrome's chrome.storage.local API (never storage.sync, so it is not synced to any account or server):

• History — a list of the last 50 JSON pages you viewed (URL, title, a short preview, and the JSON text itself for pages under ~500KB), so you can quickly reopen them from the popup. You can clear this at any time from the popup.
• Diff hand-off — when you click "Compare (diff)", the current page's JSON text is briefly written to local storage so the diff tool (opened in a new tab) can read it, then immediately removed.

None of this data ever leaves your browser.

Permissions

• content_scripts matches (<all_urls>, file:///*) — the extension needs to inspect the content of any tab to determine whether it's a raw JSON response. It has no effect on regular web pages: the script only activates when the page body consists of exactly one <pre> element whose text parses as valid JSON. No host_permissions and no webRequest are used.
• storage — used only for the local history and diff hand-off described above.
• web_accessible_resources (diff.html) — the diff comparison page is opened from whatever site you're viewing, so it must be explicitly allowed to be navigated to from any origin. It is a static local page with no network access of its own.

Contact

Questions about this policy can be sent to the developer via the Chrome Web Store support page for this extension.