We score hundreds of thousands of public posts, and some will be wrong. If our pipeline misread one of your calls, we'll fix it. Here's exactly what we review — and what we don't.
We correct a field only when the post text explicitly stated the correct value and a reasonable person would agree the stored value is genuinely wrong. We don't change scores based on assumptions, inference, or what you feel should have been understood — only on what the post actually said.
You can challenge any of these four fields when the post text explicitly stated otherwise:
Asset. We scored the wrong coin — e.g. an ETH call read as BTC.
Direction. We scored a bullish call as bearish, or vice versa.
Timeframe. You stated an explicit horizon (e.g. "by Friday," "within two weeks") and we read it wrong.
Trigger. The trigger level or condition you stated was misread — usually a chart price-axis error.
Anything that rests on inference rather than what the post explicitly said:
Inferred fields. If the post didn't state it outright — e.g. a timeframe we inferred from the chart or tone — we won't swap in your later interpretation.
Filtered posts. Posts with no clear, scoreable forecast aren't added back in after the fact.
Full removal. A correction updates the score — it doesn't erase a public call from the record.
Confirmed errors are corrected and the change is logged publicly. Every dispute is open to any forecaster we've scored — fairness across all 150 accounts is the standard we hold ourselves to.