ClearUtils

Contact

Contact ClearUtils

Use this page when a tool is broken, a result looks wrong, a page has unclear instructions, or you want to suggest a practical utility that would help real users. Clear, specific reports are the easiest to act on.

Email support

Email: hello@clearutils.com

Include the tool URL, what you pasted or selected if it is safe to share, what you expected to happen, what actually happened, and your browser/device if the issue looks visual or interactive. Do not email passwords, private tokens, regulated records, or confidential customer data.

Privacy and safety when reporting

Most ClearUtils tools are designed for browser-local processing, but support email is not a secure place for secrets or private records. If a bug depends on sensitive input, describe the pattern with a small made-up example instead of sending the original content.

What to send

  • Bug reports: broken buttons, copy failures, wrong calculations, formatting errors, or confusing output.
  • Corrections: typos, unclear examples, outdated guidance, or missing limitations.
  • Tool suggestions: small utilities that fit ClearUtils workflows and can run safely in the browser.
  • Privacy questions: questions about local processing, analytics, advertising, or data handling.
  • Accessibility issues: keyboard traps, missing labels, focus problems, low contrast, or mobile layout problems.

What ClearUtils can fix fastest

The most actionable reports include one page URL, one clear expected result, one actual result, and a safe sample that reproduces the issue. Reports about high-use tools, privacy wording, accessibility barriers, mobile layout problems, and incorrect examples are prioritized because they improve the public site for everyone.

If a page feels repetitive or unclear, include the exact URL and the context that would make the tool easier to use. ClearUtils uses those reports to improve examples, limitations, instructions, and workflow links on existing pages.

Response expectations

ClearUtils is a small site, so responses are not guaranteed and may not be immediate. High-impact bugs, privacy questions, and clear corrections that improve public pages are prioritized. A public form is not enabled because email keeps the support path simple without collecting extra form-submission data on the site.