Contact
The best way to reach DevDecoder is by email: contact@devdecoder.net.
DevDecoder is maintained as a side project, so non-urgent replies may take some time. Security reports and bug fixes are prioritized.
What to include in a bug report
If something on the site isn't working, a quick note with the following will get you a fix much faster:
- Which tool you were using (Decode, Hash, JWT, JSON, Regex, Utils).
- What you were trying to do.
- What happened instead.
- Browser and version (e.g. "Chrome 127 on macOS").
- A sample input that reproduces the issue, if you can share one safely. Please do not send production tokens, secrets, or personally identifying data — a redacted or synthetic example is always fine.
Feature requests
Proposals for new tools are evaluated against three questions: is it routinely useful to day-to-day development, can it run entirely in the browser, and is there an educational angle that makes the page worth reading. If you've got an idea that fits, send it over. A sentence or two is enough — no formal proposal needed.
Privacy and security reports
If you've found a security issue — something that could let a malicious script leak tool input, bypass CSP, or otherwise violate the "nothing leaves your browser" guarantee — please flag it in the email subject line (e.g. [security]) so it gets prioritized. Coordinated disclosure is appreciated.