Docs
Privacy and data handling
The reason to use a local JSON viewer is that production payloads contain things that should not be pasted into a stranger’s server. Here is precisely what happens to yours.
The viewer
- Files are read with the browser File API and parsed in a Web Worker on your device.
- No document content is transmitted. There is no upload endpoint for the viewer to call.
- Generated TypeScript, JSON Schema, beautified output and copied subtrees are all produced locally.
- You can verify this: open your browser devtools Network panel, load a file, and watch that nothing leaves.
What is stored on your device
| Store | Contents | Cleared by |
|---|---|---|
| localStorage | Settings: theme, indent, parse mode, expand depth. | Clearing site data. |
| IndexedDB | Opened documents, only while "keep documents" is enabled. | Turning the setting off, removing an entry, or clearing site data. |
Analytics
The site loads Google Analytics to count page views and which features get used. It records the usual page and device metadata. It does not receive file names, file contents, search queries or generated output, because none of that is ever passed to it. Browser-level tracking protection and content blockers stop it entirely, and the viewer works identically without it.
Where the HTTP API is different
The HTTP API and the MCP server exist so automated tools can use JSONParse, and they necessarily receive the JSON you send them. They are a separate surface from the viewer with a separate promise:
- Request bodies are processed in memory and are not written to disk or a database.
- Payload contents are not logged. Operational logs record method, path, status, duration and a truncated request id.
- There is no account, no retention and nothing to delete afterwards.
- If a document must never leave your machine at all, use the viewer, not the API. That distinction is the whole reason the viewer exists.
Third parties
The site is served from Vercel, which terminates TLS and keeps standard request logs. Google Analytics is the only other third party. There are no advertising scripts, no A/B testing services and no session recorders.
Frequently asked questions
Can I use JSONParse with confidential production data?
The viewer is built for that case: the document never leaves the browser tab. Your own organisation’s policy is the thing to check, and pointing a reviewer at the Network panel is usually the fastest way to settle it.
Does the site work with analytics blocked?
Completely. Analytics is loaded from a separate script and nothing in the application depends on it.
Is there a self-hosted option?
Yes. The project is MIT licensed and the build produces static files — clone the repository, run the build and serve the output from anywhere.
Last updated .