Corrections Policy
Our commitment to accuracy and how we handle errors.
Our Commitment
Developers rely on our tools to produce correct output for their workflows. A JSON formatter that mishandles Unicode, a hash generator that produces wrong digests, or a Base64 encoder that drops bytes would be worse than useless. We take correctness seriously.
How to Report an Error
If you find an error in any tool's output, content, or behavior on ThisDevTool, please report it:
- Email: contact@thisdevtool.com
- Subject line: Include the tool name (e.g., "Error in JWT Decoder")
To help us investigate quickly, please include:
- The tool where you found the error
- The input you used (or a description if the input is sensitive)
- The output you received
- The output you expected (and how you verified it)
- Your browser and operating system
How We Handle Corrections
- Acknowledge: We confirm receipt of the report, typically within 48 hours.
- Reproduce: We attempt to reproduce the issue in the same browser and with the same inputs.
- Root cause: We identify whether the error is in our code, a browser API edge case, or a misunderstanding of the tool's scope.
- Fix and test: We correct the issue, verify the fix across browsers, and run our automated test suite.
- Deploy: The fix is deployed through our standard build and deploy pipeline.
- Update review date: The "Last reviewed" date on the affected tool is updated.
Priority Levels
- Critical: Tool produces incorrect output for valid input (e.g., wrong hash, corrupted encoding). Fixed within 24 hours of confirmation.
- Standard: Tool handles an edge case poorly, content is inaccurate, or a feature does not work in a specific browser. Fixed within one week.
- Minor: Typos, UI glitches, or cosmetic issues. Addressed in the next update cycle.
Transparency
When we make a substantive correction to a tool's logic, we update the "Last reviewed" date so users can see the page has been recently verified. We do not silently change tool behavior. For corrections that change how output should be interpreted, we add a note to the tool's content section.
Last updated: April 2026