Research Methodology

Six steps for every page

1. Define the question. Each page answers one practical question for an operator team, set out in its opening sentence.
2. Read the primary source. We read the regulator's page, the code provision or the law itself. We use a law firm or news summary only when the primary text cannot be read, and we say so on the page.
3. Quote exactly. Rules are quoted word for word in quotation marks. Where we summarize, we do not use quotation marks.
4. Scope the claim. Each rule is tied to its market and, where it matters, to license types, such as "remote casino, bingo and betting licensees in Great Britain".
5. Label examples. Worked examples, sample records and API calls are marked as illustrative. They do not describe any operator.
6. Date everything. Each source shows the date it carries, or "no date shown", and every source was read on the date in the source list.

What we cannot do

We do not have access to operators' systems, so we do not report measured results, failure rates or performance. Where a rule's status was unclear when we read it, such as US rules on consent revocation, the page says what we could confirm and from where.

Evaluating software

We do not review named products. Instead, our evaluation method sets out requirement-based tests and an evidence scale that buyers can run themselves.

Interactive tools

The consent decision demo applies a fixed, conservative decision order. Every build runs each case in its published test matrix, and every combination of inputs, against the explorer's decision code, and the build fails on any mismatch. It does not give advice and never approves a send.

Review and updates

Pages are reviewed when a cited source changes or a reader reports an error. The full source list is on the data sources page, and correction handling is in the editorial policy.