GearCheck Lab currently uses the public project issue tracker for technical feedback, broken tools and factual corrections. Public reports are useful because they create an auditable record of reproducible problems and fixes.
Use the GearCheck Lab GitHub issue tracker for a broken diagnostic, incorrect technical explanation, browser compatibility problem, accessibility issue, or reproducible result that appears inconsistent with the tool's stated methodology.
If a page overstates what a browser measurement can prove, uses an incorrect technical term, contains an outdated compatibility claim or gives misleading troubleshooting guidance, please report the exact sentence or section.
Corrections are evaluated against the implementation, browser behavior, authoritative technical documentation and the site's published methodology.
New tool ideas are most useful when they describe a real diagnostic problem, what a browser can measure, why existing tools are insufficient and how a user would interpret the output.
Requests that would produce a thin or nonfunctional page may be declined even when the search term appears popular.
The current public contact route is not appropriate for confidential requests containing identifying or sensitive information. Do not post personal data simply to ask a privacy question.
Non-sensitive questions about the published Privacy Policy can be raised publicly. A dedicated private support inbox is not currently published.
For results that appear to indicate a hardware fault, repeat the test first and compare another browser, USB/Bluetooth mode, port or computer when practical. Include those comparisons in the report because they help distinguish a site bug from a platform- or device-specific behavior.