RTPBOSS
Data & methodology

Corrections policy

If a figure is wrong, we want to fix it — and we want to fix it the right way, with a source, not on assertion alone.

How to report an issue

Email a data correction with:

  • the game or casino name and a link to its page on RTPBoss;
  • the field you believe is wrong and the value you expected;
  • a link to a source (ideally the provider's own rules or catalogue).

The source is the important part — it is what lets us verify rather than guess.

What happens next

  1. Reported — we receive the issue.
  2. Triaged — we confirm which field and page it affects.
  3. Investigated — we compare the claim against the value's current source and any higher-priority source.
  4. Confirmed or rejected — a value is not changed simply because someone says it is wrong; the sources have to support the change.
  5. Corrected — if confirmed, the value is updated and the original is preserved internally for audit.
  6. Validation rerun — automated checks run again over the changed record.
  7. Published — the corrected value goes live.
  8. Changelog — material corrections are logged.

The rules we hold ourselves to

  • A value changes only when an available source proves the correct figure. See the source policy.
  • If we cannot prove the right value, the field is set to unknown rather than left showing a suspect figure.
  • changedAt updates only on a real change to the value — never on a routine deploy.
  • We do not hide a correction by backdating the page. A material change moves the “last updated” date forward, honestly.

For how figures are sourced and rated in the first place, see the data methodology.

Maintained by the RTPBoss Data Team — Maintains the game database, validation rules and source records. Last materially updated 2026-07-16. Spot something wrong? Report a data issue.