Corrections

Every publication gets things wrong sometimes. What separates a trustworthy one from an untrustworthy one is not the absence of mistakes — it is what happens after a mistake is spotted. This page explains exactly how TokenSpin handles errors: how to tell us about one, what we do next, and how you will be able to see, on the page itself, that something was changed.

We would rather be corrected in public than quietly wrong in private. If you have found an error anywhere on this site, please tell us. You do not need to be polite about it.

How to report an error

Send it through our contact page. The more specific you can be, the faster we can act. What helps most:

• The exact page URL where you saw the problem.
• The specific sentence, figure, date or listing that looks wrong.
• What you believe the correct information is.
• A source we can check for ourselves — an official announcement, a project’s own documentation, a block explorer, a primary filing. A link to someone else’s article is a starting point, not proof.

You do not have to give your name, and you do not have to prove anything about yourself. We assess the claim, not the person making it. If you are reporting something about a rewards programme listed on the Rewards Radar, telling us whether you are connected to that programme is useful context, but it will not stop us from checking.

What happens after you report it

The report goes to the editorial desk, and someone re-checks the claim against a primary source — the same standard we apply when we first publish something, described in how we vet. We do not simply take the reporter’s word for it, and we do not simply defend our original wording either.

One of three things then happens. If the claim is right, we fix the page. If the claim is wrong, we leave the page alone and, where we can, reply explaining why. If the claim is neither clearly right nor clearly wrong — the underlying facts are genuinely disputed, or the primary source is ambiguous — we usually edit the page to reflect that uncertainty honestly rather than pick a side we cannot back up.

Anything that touches reader safety jumps the queue. If a listing on the Radar or a warning on scam alerts may be putting people at risk of losing money, we would rather pull or flag the item first and finish the investigation afterwards. An over-cautious flag costs a reader an opportunity; an under-cautious one can cost them their funds.

Silent fixes versus noted corrections

Not every edit deserves a public notice, and pretending otherwise just buries the important ones in noise. We draw the line like this.

Silent fixes

Typos, spelling, broken links, formatting, clumsy sentences, a missing heading — anything where the meaning of the page does not change. We fix these as we find them and do not annotate them. If a fix changes what a reader would understand or do, it is not a typo, and it does not get treated as one.

Noted corrections

Anything that changes the substance: a wrong figure, a misstated eligibility rule, a mischaracterised project, a risk rating that was wrong, a date, a claim about who runs something, or a statement we can no longer stand behind. These get a dated correction note appended at the foot of the article or listing, describing what was wrong and what it now says. The note stays there permanently. We do not delete a correction once it has been up for a while, and we do not rewrite history by silently replacing the old wording.

Where the error is severe enough that the whole piece is unsound, we will say so plainly at the top of the page rather than patching around it. If a Radar listing turns out to be unverifiable, it is removed or flagged, with the reason and the date shown — that is the same standard the Radar is built on.

Updates are not corrections

Crypto rewards programmes change constantly. Terms shift, campaigns end, a project changes its rules. When we revise a page because the world moved on rather than because we got it wrong, that is an update, and we mark it with a revised “last reviewed” date instead of a correction note. We think blurring the two is dishonest in both directions: it lets a publication dress up a real mistake as routine maintenance, and it makes ordinary housekeeping look like a scandal.

Why we bother spelling this out

A corrections policy is easy to write and slightly uncomfortable to follow, which is precisely why so few sites in this space publish one. Ours exists so you can hold us to something specific. If you think we have failed to follow it, that is also worth reporting — same contact page. The rest of our standards, including how we source and what we refuse to publish, are in our editorial guidelines.

Nothing on this site is financial advice, and a correction to a page does not turn it into advice either.