Source policy
How RTPBoss chooses between sources, records where each value came from, and decides when a figure is trustworthy enough to publish.
Source priority
When more than one source is available for a field, we prefer them in this order:
- Official game rules — the provider's own rules for the specific game.
- Official provider catalogue — the studio's own catalogue or game page.
- Official API — a first-party feed such as the Stake Engine outcome tables.
- Independent database — a reputable third-party database, used as secondary confirmation.
- Legacy import — an earlier bulk import, kept only until a better source is found.
Official game rules rank highest because they are the authoritative statement of how a game behaves. Provider catalogues come next; they are first-party but occasionally lag the rules. An official API is used where a provider exposes exact figures directly. Independent databases are only ever used to corroborate — never to certify.
A secondary source is not an official one
When an independent database agrees with a value, we mark it secondary_verified, not official. That distinction is deliberate and it is visible on the game page. RTPBoss does not, and cannot, buy or sell confidence status — a source's weight comes only from what it is.
Conflicts
If two sources disagree, we record the conflict and keep both values rather than silently overwriting one. Where the disagreement is material, the field is marked conflict_detected and the published figure is the higher-priority source, with the alternative retained. Nothing is resolved by guesswork.
When a value is set to unknown
A field is left blank / unknown when:
- no documented source supports it;
- the only value available is implausible and no source proves a correct one;
- sources conflict and none can be treated as authoritative.
Unknown is an honest answer. We never fill a gap with an estimate.
Dead links and archiving
Source pages move and disappear. When a source link dies, the value keeps the record that it was once checked, but we do not present a dead link as a live citation. RTPBoss does not currently maintain a public archive of every source document; where a value's provenance can no longer be confirmed, it is treated as legacy and flagged for re-verification. See the corrections policy for how re-checks are triggered.
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.