Editorial policy

Evidence classes

Every factual claim on this site falls into one of four categories, kept visually distinct throughout.

Sourcing

• Licence numbers checked against public registers where one exists
• KYC positions read from operators' published terms, not marketing pages
• RTP figures taken from operators' own game pages or published statements
• Legal matters taken from court filings and regulator publications, or from established reporting on them
• Deposit volume from public on-chain sources, rounded and labelled as indicative

Unverified fields

Where we cannot verify something to a citable standard, the page says so. We do not fill gaps with plausible guesses, and several profiles carry visible gaps as a result.

A page showing where our knowledge ends is more useful than one that hides it.

Language

We distinguish between allegation, finding and conviction, and we use those words precisely. We report what courts and regulators determined, we report what operators say in response, and we say when a matter is unresolved.

We do not name private individuals in allegation contexts, even where published reporting does. It adds nothing a reader needs and creates risk without benefit.

Corrections

• Report an error through contact
• We verify it against primary sources
• Corrections are made and the change is dated
• Substantive corrections are noted on the page rather than made silently

Operator disputes

Any operator we cover may respond to anything we publish. We will publish a response where one is given, alongside the original material rather than replacing it.

We correct factual errors promptly. Where a matter is disputed, unresolved or concerns a corporate entity that no longer operates a brand, we may retire the coverage rather than leave a contested claim standing, and we would rather publish nothing than publish something we cannot currently stand behind.

Commercial separation

Rank and standing are computed from operator data and ranking data only. Commercial terms live in a separate file the ranking build does not read. The full explanation

What we refuse to publish

• Techniques for circumventing identity verification or anti money laundering controls
• Invented ratings, testimonials or player quotes
• First hand experience we did not have
• Accusations we cannot source
• Fake urgency, countdown timers or manufactured scarcity