Contact Us
We would love to hear from you — whether it's a bug, an idea, or just feedback.
The best way to reach us is by email. A real person reads every message, and we aim to reply within two business days — usually sooner. There is no contact form, phone queue, or chatbot in the way: just write to us directly and we will get back to you.
JSON Wallet is an independently built and maintained developer tool. When you email us, you are reaching the same small team that designs, writes and ships the site — not an outsourced support desk.
Who you are reaching
JSON Wallet is built and maintained by Bhushan Kumar Singh, who also writes and tests the guides. There is no ticketing system between you and the person who can actually fix the problem — email lands directly with the maintainer. If you prefer a public record, you can also open an issue on the GitHub repository, which is the best place for bug reports and feature requests you are happy to discuss in the open.
What to expect after you write
We aim to acknowledge every email within two business days, usually sooner. Reproducible bug reports are treated as product bugs and prioritised — a clear, minimal example often means a fix ships the same week. Feature requests are read and logged even when we cannot build them immediately; knowing which problems come up most often directly shapes what gets built next. We do not run a marketing list and will not add you to one: your email is used only to reply to you.
What to write about
- Bug reports — found something that doesn't work? Tell us what you did, what you expected, and what happened instead. A sample of the JSON (with any sensitive values removed) helps a lot.
- Feature requests — is there a JSON operation or view you wish we supported? Let us know.
- Feedback — anything that felt confusing, slow, or delightful. It all helps us improve.
- Privacy questions — see our Privacy Policy first, then email us if anything is unclear.
Before you email
A few things that help us help you faster:
- Reproducing a bug? Tell us your browser and version, the steps you took, and paste a small (sanitised) JSON sample that triggers the problem. Bugs we can reproduce get fixed far quicker than ones we can only guess at.
- Suggesting a feature? Describe the problem you are trying to solve, not just the button you want. Knowing the underlying workflow often leads us to a better solution than the one first imagined.
- Asking about privacy or your data? Skim the Privacy Policy and Terms first — most questions about what we store (almost nothing) are answered there.
- Learning how to use a tool? Our guides walk through formatting, validating, comparing and repairing JSON step by step.
A note on your data
Remember that JSON Wallet processes your data entirely in your browser — we never see the JSON you work with. So when you report a bug, we won't have access to your document unless you choose to include an example in your email. Please remove passwords, tokens, and other secrets before sharing anything.
Looking for help using the tool?
Many common questions are answered in our guides, which cover formatting, validating, comparing and repairing JSON step by step.
Frequently asked questions
How quickly will I get a reply?
We aim to respond within two business days, and often faster. Bug reports that include a reproducible example tend to get the quickest and most useful replies.
Can you recover a document I lost?
Unfortunately no. Because JSON Wallet processes everything in your browser, your documents live in your own browser's local storage and never reach our servers — so there is nothing for us to restore. Clearing your browser data or using private browsing removes them permanently.
Do you offer a paid or enterprise version?
No. JSON Wallet is free for everyone, with no accounts and no paywalled features. If you have a specific need the tool does not cover, email us and tell us about it — it may become a future feature.
Can I report a security issue privately?
Yes. Please email help@jsonwallet.com with the details rather than opening a public issue, and we will respond as a priority.
Is my data safe if I include an example?
Only include what you are comfortable sharing. We recommend removing passwords, tokens and personal data first — the sensitive data detector can help you spot and redact them before you paste anything into an email.