Source hierarchy
For regulatory statements, prefer the competent regulator and its current register. For game rules, prefer the exact provider documentation and in-game rules. Operator terms can establish what the operator publishes, but do not independently prove payout performance. Third-party reviews are useful leads, not substitutes for a licence check. Sources belong beside the factual statement so readers can inspect the basis.
Minimum evidence for a factual field
Before publishing a licence, payment method, bonus, payout duration or provider attribution, record the exact operator/domain, applicable market, source URL, check date and scope. The rendering layer suppresses historical casino fields without dated field-level evidence. Public bonus research is kept separately: cards distinguish freshly retrieved operator pages, indexed operator offers and independent review reports. Amounts retain their published currencies and distinguish first deposits from whole packages; we do not convert currencies or blend terms from conflicting offers. A language route or affiliate campaign’s country code is not proof of local eligibility.
What a genuine hands-on test would require
A defensible test record should identify the tester, date, jurisdiction, exact game/provider, account conditions, action performed, result and supporting screenshots or records. Never expose personal documents or financial identifiers. If no lawful, documented deposit-and-withdrawal test was performed, do not write “we deposited”, “I cashed out” or a precise tested payout speed. No such test is claimed for the current commercial directory.
Ratings and comparison order
No numerical casino rating is published merely because one existed in an older data file. A rating needs a documented scoring rubric and test record. The commercial directory retains its agreed inventory order; that order is not presented as an independent score. Comparison tools show only supported fields and identify missing information rather than estimating it.
Tools and mathematical examples
The demo is a simplified, independent virtual-credit simulation. The verifier covers the implementation named in its interface, not every provider. A synthetic test vector can validate a calculation without proving that a real operator used those inputs. Examples of RTP or net return are mathematical illustrations, not forecasts. See fairness verification.
Dates, translation and corrections
A page’s update date changes when its content is substantively reviewed or edited, not automatically when the calendar advances. Country-specific statements must be checked locally rather than translated as universal law. New evidence can change a conclusion. Submit a correction with the page, quotation and supporting source through Contact; there is no guaranteed response deadline.