Contact GearLint

Email

General questions, bug reports and partnership enquiries: hello@gearlint.com. Data or privacy requests (access, deletion, a copy of anything held about you): privacy@gearlint.com. Both inboxes are read by the same person, so pick whichever fits and skip the CC.

Reporting a test that reads wrong

The tests read raw browser APIs, so a wrong number usually means the browser, the driver, or the device is doing something unusual — and that is exactly the kind of report I want. To make it actionable, include:

• Which test, and the URL of the page you were on.
• Browser and version (for example “Firefox 141 on Windows 11”), plus whether it is a laptop or desktop.
• The device under test: exact model if you know it, and whether it is wired, Bluetooth or a dongle.
• What you saw versus what you expected. “Stick rests at 0.02 but the game drifts” is a perfect report.
• The copied result text, if the page you used has a copy button. It carries the numbers and the thresholds that were applied.

Screenshots help. Screen recordings help more for anything involving timing — chatter, double clicks, or a value that flickers only occasionally.

Response times

This is a side project, not a company with a rota. Expect a reply within a few days; test bugs get looked at first, partnership mail last. If a week passes with nothing, send the message again — mail does occasionally get buried.

What I cannot do

I do not repair hardware, and I cannot rule on your warranty claim. What I can do is give you the numbers: run the relevant test, use the copy-result button, and send that record to the manufacturer or retailer. The guides explain what a normal reading looks like and which figures support staff actually ask for.

I also do not accept paid placements inside guides, and I do not sell or share email addresses. If you write in, your message is used to answer you and nothing else.