Feedback wanted: a JSON formatter that lets you verify no pasted-content upload

[Json-Lee-git]

I'm building SafeJSON, a privacy-first JSON formatter and developer toolkit.

The core idea is simple: you should not have to trust the tool. You should be able to verify it.

Verification flow:

1. Open DevTools
2. Go to the Network tab
3. Paste JSON into SafeJSON
4. Confirm that no request contains your pasted content

SafeJSON currently includes:

• JSON formatting and validation
• JSON diff
• JWT decoding
• JSONPath queries
• JSON Schema validation

The product is open source and runs pasted JSON locally in the browser.

I'm looking for feedback from developers who regularly paste logs, API responses, config files, JWTs, or production
JSON into online tools.

Specific feedback I'd love:

• Is the "verify in DevTools" privacy model clear enough?
• What would make you trust this tool more?
• Which JSON workflow should be improved next?
• Are there any claims that feel too broad or need tighter wording?

Website: https://www.safejson.dev
Source: https://github.com/s01071233604-tech/safejson

[Json-Lee-git]

GitHub update

Added a new security guide:

https://www.safejson.dev/security/check-json-formatter-upload

The guide explains how to use DevTools Network to verify whether a JSON formatter uploads pasted content after

formatting, validating, decoding, or diffing. It also links into SafeJSON's local processing verification page and extension permissions page.

This fits the core SafeJSON principle: privacy claims should be verifiable, not just stated.

Related pages:

• https://www.safejson.dev/privacy/verify-local-processing
• https://www.safejson.dev/extension/permissions