๐ ๐ฅ๐ฒ๐๐ฟ๐ผ๐๐ฒ ๐ฆ๐ฎ๐ณ๐ฒ๐๐ฆ๐ข๐กโ๐ ๐ฃ๐ฟ๐ถ๐๐ฎ๐ฐ๐ ๐๐ผ๐ฝ๐
I changed the wording on SafeJSON today.
I did not change the design. I changed how I talk about privacy.
I used to say SafeJSON is a privacy-first JSON toolkit.
That phrase is too vague. It asks you to trust me. For a developer tool, trust is not enough.
Many JSON tools ask you to paste API responses, logs, or JWTs into a text box. This data often contains tokens, customer info, or credentials.
Most tools do not tell you what happens to that data.
- Does the tool process data locally?
- Does it send data to a server?
- Does it store your logs?
Most users do not check. Most websites do not want you to check.
I want to fix this.
I removed the vague claims. I replaced them with a technical fact: No pasted content uploads.
SafeJSON processes your JSON in your browser. Your data does not go out in any request.
I want to move from blind trust to verifiable privacy.
You do not have to take my word for it. You can test it yourself.
- Open your browser DevTools.
- Go to the Network tab.
- Paste your JSON into SafeJSON.
- Use the formatter or validator.
- Look at the requests.
If you see no requests containing your pasted data, the tool works as promised.
JSON tools are boring until the data is sensitive. A formatter is just a tool until you paste a production log or a webhook payload.
SafeJSON is a browser-based toolkit. It includes a Formatter, Validator, JWT Decoder, and more.
The goal is simple: Use a JSON tool without blind trust.
SafeJSON is still small. I had 51 users in the last 28 days. This is not a big launch. It is a note on how I position my product.
I am testing if verifiable privacy is a real need for developers.
One thing is clear. Privacy copy for developer tools should be testable. It should not just be reassuring.