Contact

Who you are writing to

Jsonviewpro is a small, independently run project rather than a company with a support desk. Messages go to one inbox and are read by the person who builds the site, which has one good consequence and one bad one: a well-described bug can be fixed the same week, and there is no rota covering replies, so a response is not instant.

That is also why the guidance below is specific. A message with a reproduction in it gets acted on; a message saying a tool is broken usually turns into three rounds of questions first.

What is useful to include

• For a bug: which tool, what you did, what happened, and what you expected instead.
• For a parse or conversion problem: the smallest document that reproduces it — never a real payload containing personal or confidential data.
• Your browser and operating system, if the problem looks visual or performance related.
• Anything unusual about the environment: an ad blocker, a strict privacy mode, a corporate proxy, or an extension that modifies pages. These account for a surprising share of reports.
• For a correction to one of the guides: the page and the specific sentence.

Please do not send us your JSON

Jsonviewpro is built so that your documents never reach us, and that principle does not change over email. A document pasted into a message *has* left your machine, and it lands in an ordinary mailbox with none of the guarantees the site itself makes.

If you need to share a reproduction, reduce it to a minimal fictional example first. In practice this helps twice over: shrinking a failing document to the few lines that still reproduce the problem usually identifies the cause before anyone else reads it.

Reporting a security issue

Security reports are welcome and taken seriously. Email them with Security in the subject line, and please do not post details publicly until a fix is out.

Useful things to include: the affected page, the steps to reproduce, what an attacker could achieve, and any proof-of-concept payload. Because every tool runs client-side, the interesting classes here are cross-site scripting through crafted document content, anything that escapes the Content-Security-Policy, and anything that causes data to leave the browser.

There is no bug bounty and no payment — this is a free site with no revenue beyond advertising, and it would be dishonest to imply otherwise. Credit in the release notes is offered gladly if you would like it.

Corrections to the guides

The tool pages and articles make specific factual claims — about number precision, YAML scalar coercion, CSV quoting rules, JSONPath dialects and more. They are written against tested behaviour rather than from memory, and they can still be wrong or go out of date as the underlying libraries change.

If you find an error, quoting the sentence is enough. Corrections are made directly on the page rather than in an appended note.

Privacy and data requests

The privacy policy is the full answer, and the short version is that there is very little to request. There are no accounts, no stored documents and no profile attached to you — the documents you open are never received in the first place, so there is nothing to export or delete.

Interface preferences live in your browser's local storage and are cleared whenever you clear site data for this domain. Advertising cookies, where an ad provider is configured, are set by that provider and are governed by its own policy and its own opt-out controls; we cannot delete them on your behalf.

If you have a question the policy does not answer, ask — gaps in it are worth knowing about.

Advertising and other enquiries

Jsonviewpro is free and supported by advertising, and enquiries about that are fine. So are questions about using the tools inside an organisation, which need no permission: everything runs client-side, so nothing is transmitted to us and there is no licence to negotiate for ordinary use.

Link exchanges, paid guest posts and sponsored-content offers are declined without reply.

What this address cannot help with

• Recovering a document you closed. Nothing is stored anywhere — if the tab is gone, the document is gone.
• Debugging your own API, schema or data pipeline. The analyzer and validator will usually tell you more than we could.
• Account or password problems. There are no accounts.
• Removing an advertisement. Ad selection is the provider's, not ours — though a report about an ad that breaks the page or behaves badly is genuinely useful.