Skip to main content

Privacy Policy

Your JSON stays on your device. This page explains exactly what that means, and what the site does collect.

The short version

The JSON, YAML and schema documents you paste, upload or drop onto Jsonviewpro are processed entirely inside your browser. They are never transmitted to a Jsonviewpro server, never written to a log, never placed in a URL, and never sent to analytics or an error tracker.

This is a property of how the tools are built rather than a promise about how we behave: there is no server-side JSON processing in this application to send your documents to.

What runs locally

All of the following happen in your browser tab, using JavaScript and a Web Worker:

  • Parsing, validation and error reporting
  • Formatting, beautifying and minifying
  • The tree view, the table view, search and JSONPath queries
  • Structure analysis and data-quality findings
  • Comparing two documents
  • Converting to CSV and YAML, and converting YAML to JSON
  • JSON Schema generation and JSON Schema validation
  • Code generation for TypeScript, JavaScript, Python, Java, Kotlin, Go, C#, Rust and PHP
  • Copying to the clipboard and generating downloads

What is stored on your device

Jsonviewpro stores a small set of interface preferences in your browser’s local storage: indentation width, whether keys are sorted, tree display options, search options, converter options and the width of the editor/result split.

Document content is never written to local storage, session storage, cookies or IndexedDB. Closing the tab discards it.

Files you open

Files opened with the Upload button or by drag-and-drop are read with the browser’s FileReader API. The contents stay in the page’s memory. No upload request is made, and the file is not copied anywhere.

Analytics

If a privacy-conscious analytics script is enabled on this deployment, it records anonymous product usage only: which tool page was opened, and which action was taken — for example that a document was formatted, or that a CSV export happened.

This is enforced in code rather than by policy. Events pass through a single function that accepts only a fixed list of event names and a fixed list of properties (the tool slug, the output language or format, the view, a coarse size band, and which built-in example was loaded). Every other property is discarded before anything is sent, and non-scalar values are dropped.

The consequence is that there is no code path by which JSON content, JSON keys, JSON values, file contents, file names, error text, API keys, tokens or passwords could reach an analytics provider. The size band is deliberately coarse — “under 100 KB”, “under 1 MB” — so a document cannot be identified by its length.

Advertising

Jsonviewpro is free and supported by advertising. When an ad provider is configured for a deployment, that provider’s script is loaded from its own domain and may set cookies or use similar technologies to select and measure ads, subject to that provider’s own privacy policy.

The ad provider receives ordinary web request information such as your IP address, user agent and the page URL. Because Jsonviewpro never puts document content in a URL, no part of your JSON is exposed to it.

Every tool continues to work with an ad blocker enabled, or if the ad provider is unreachable.

Cookies

Jsonviewpro itself sets no cookies. It uses local storage for the interface preferences described above. Any cookies present come from the configured advertising provider.

Third parties

  • Hosting and content delivery — serves the application files and standard server request logs (IP address, user agent, requested path, timestamp). These logs contain no document content.
  • Advertising provider — only when configured for the deployment, as described above.
  • Nothing else. Fonts, the Monaco editor and every library are served from this domain, so browsing Jsonviewpro does not contact a third-party CDN.

Data retention

Jsonviewpro retains no document data, because none is ever received. Interface preferences remain in your browser until you clear your site data. Standard hosting request logs are retained by the hosting provider under its own retention policy.

Children

Jsonviewpro is a developer tool and is not directed at children. No accounts exist and no personal information is collected by the application.

Changes to this policy

If this policy changes, the updated version will be published on this page with a new revision date. Material changes to how data is handled will be reflected here before they take effect.

Questions

See the contact page for how to get in touch about anything on this page.