When Hunch gets it wrong
Written September 6, 2026, before it was needed.
Hunch can be wrong. It can raise a flag on a message that was genuine, and it can stay quiet on one that was not. When someone shows us a specific case like that, we read and triage every report. We do not promise a fixed publish time. When we publish a correction, it says what Hunch got wrong, why it happened, and what changed because of it. Not a footnote somewhere else. Here, on this page, in the open.
We do this because being able to check our misses in public is part of how you can trust the rest. A tool that never admits a mistake is asking you to take its word for it. We would rather show you.
Seen a miss or a false alarm? Write to support@checkyourhunch.com . We read every one.
Why there is no green
Hunch shows one of three reads: stop, worth a check, or quiet. There's no green all-clear, because no tool can promise a message is fine. Quiet means we didn't find a specific sign in the text we checked. It doesn't verify the person or the deal. We'd rather tell you the truth than a comfortable lie.
Knowing your name, ID number or address does not prove who sent a message. Those details leak in data breaches and get traded. What tells you more is what the message asks you to do.
Known limits
A genuine sign-in notification can show as worth a check. It will not show as stop.
Rules version and extension version move independently. The policy decides the band.
Extension build 3.8.17. Detection rules version 3.8.16. Package sha256: 4e57f9432d824a5b787a84e6e2089e278adbbae55af0e0d5a0553387f61999b0