Corrections Policy

We publish a lot of numbers, and we want every one of them to be right. If you spot a mistake, tell us. Here's how to report it and what happens next.

Last updated

Accuracy is the whole point of a math-honest site, so we treat error reports seriously. If you think something on OnlineCryptoGame is wrong, whether it's a probability, a house edge, a rule, a helpline number, a USDT network detail or a broken link, please tell us.

How to report an error

Email [email protected] with:

  • the address (URL) of the page;
  • what you think is wrong, quoted or described as precisely as you can;
  • what you think it should say, and your source if you have one.

You don't need to be an expert. "This table says X but the text says Y" is a useful report. If you've re-run one of our calculations and got a different answer, tell us what you did, so we can compare. Our testing methodology lists the scripts, seeds and parameters behind our figures.

How we check a report

The editorial team checks each report against the same evidence we used to write the page:

  • figures we calculated are checked against our simulation and calculation output, and re-run if needed;
  • figures from a source are checked against that source;
  • if the source itself has changed, for example a rule, a regulation or a helpline number, we update to the current version and note the date.

If the page is right, we'll tell you why if you'd like. If it's wrong, we fix it.

How fixes are made and logged

When we correct a page:

  1. We fix the error in the text, table or chart.
  2. We update the page's "last updated" date.
  3. On articles, we describe the change in the "What changed" note at the bottom of the page, for example which figure was corrected and what it was changed to.

We don't quietly rewrite figures. If a correction changes a number readers may have relied on, the "What changed" note says so. Small fixes that don't change meaning, such as typos, may be made without a note.

If a correction to one of our scripts affects several pages, we re-run the script, update the downloadable data on our data page, and update every page that uses it.

How quickly we respond

We aim to look at every report promptly and to fix confirmed errors as soon as we've checked them, starting with anything that could cost readers money or affect their safety, such as wrong helpline numbers or wrong network details for USDT transfers. We're a small team, so we can't promise a specific response time.

For anything that isn't a correction, see our contact page. Our editorial policy explains how pages are checked before they're published.