Canadian casino intelligence

    Corrections & ranking changes

    Track every change to our casino rankings: dated score moves with plain-language reasons, fact corrections from registry checks and player feedback, and how to report an error.

    Updated 2026-06-11

    Most casino review sites never change a score, and never admit when they were wrong. This page exists so you can check that we do both. Every material change to our rankings is logged here with a date and the reasoning in plain language: scores cut after we review player complaints, facts fixed when our registry checks catch an error, movements when an operator genuinely improves or slips.

    If you are wondering whether you can trust a ranking, this log is the quickest test we can offer. Scroll down, see what changed, and judge the reasons for yourself. Changes come from three places: our own testing and registry re-checks, the public record, and what Canadian players keep telling us in forums and through the contact page. When that evidence moves, the scores move, and the trail stays here permanently. Nothing in this log is ever quietly edited or removed.

    What counts as a correction

    A change is "material" when it touches a fact you might act on: licensing status, payout windows, payment availability, scores, or market statistics. Typo fixes and wording polish don't make the log.

    How to report an error

    Use the contact page and include the URL and the fact you believe is wrong, ideally with a source. We aim to review reports within two business days. Confirmed corrections are fixed on the page, noted here with the date, and, where the error was significant, annotated on the page itself.

    Correction log

    June 11, 2026 — five scores adjusted after complaint-pattern review

    We completed a structured review of Canadian player discussions on public forums (2024–2026) and adjusted scores where recurring complaint patterns were strong enough to warrant it. Individual reports are not independently verified; adjustments reflect the consistency of patterns, not single complaints. Every affected review now carries a "What players report" section describing the pattern.

    • ToonieBet: score 8.6 → 7.9 (now #10). Recurring verification-loop reports, capped promotional winnings, unresponsive support.
    • 888casino: score 9.4 → 8.7 (now #4). Canadian withdrawal friction: wire-verification details Canadian banks cannot supply, Interac option disabled on some accounts per player accounts, multi-week processing reports.
    • Jackpot City: score 9.0 → 8.4 (now #9). Auto-applied deposit offers with high playthrough, prominent reverse-withdrawal design, 48-hour pending window.
    • Betway: score 8.8 → 8.5. Limited but pointed fairness/support reports; under watch.
    • LeoVegas: score 8.8 → 8.6. Withdrawal-flow usability reports; minor trim.

    No score was raised in this review. Operators with thin recent complaint data (Casino Days, TonyBet, Royal Vegas, bet365, FanDuel) were left unchanged; absence of complaints is noted in their reviews as a low-certainty positive.

    June 5, 2026 — Ontario revenue figure corrected to the primary source

    Our draft market statistics carried Ontario iGaming gross gaming revenue of "$2.9 billion" for FY2024–25, taken from media coverage. Checking the iGaming Ontario year-three report directly, the figure is CAD $3.2 billion; the $2.9B number is a transcription error that propagated across several outlets and still appears in coverage today. Corrected on our market statistics page, with a note flagging the wrong number for anyone else citing it.

    May 29, 2026 — Betano's Alberta status set to "not registered"

    Multiple secondary sources listed Betano as registered for Alberta's launch. Our parse of the AGLC registrant list (May 29, 2026) does not show Betano or its operator Kaizen Gaming. We set Betano's Alberta status to not registered until a primary AGLC document shows the entity, and noted the conflict on the review. Betano has publicly signalled interest in the province; we will re-check the register before July 13.

    May 27, 2026 — "$20,000 Alberta betting limit" claim removed

    A "$20,000 maximum bet" figure for Alberta's new market circulated widely in coverage of Bill 48. We could not find it in the Bill or in the AGLC's Standards and Requirements for Internet Gaming, so it was removed from our Alberta drafts before publication. If a primary source for the figure appears, it will be restored with a citation.

    May 21, 2026 — Ontario market size clarified: 44 operators, 77 gaming sites

    Coverage of Ontario's market uses "44" and "77" interchangeably, and our early drafts had inherited the confusion. They are different units: as of our May 21 parse of the iGaming Ontario directory, 44 licensed operators run 77 gaming sites (one operator can run several brands). Our dataset now labels the two separately everywhere, and our operator database tracks brands against their operating entities so the numbers reconcile.

    May 5, 2026 — Alberta wording tightened: registered is not licensed

    After Google opened its ad platform to Alberta gambling advertisers on May 4, coverage increasingly described operators as "licensed in Alberta." Nothing is licensed in Alberta until the market opens on July 13; what exists today is a pre-launch register. We went through our Alberta drafts and relabelled every claim: brands are "AGLC-registered," not licensed, until launch day. Pedantic, but it is exactly the kind of distinction this site exists to keep straight.

    April 24, 2026 — the verification log opens

    Start of the pre-publication verification programme behind this site: a baseline snapshot of the iGaming Ontario operator directory, the working rule that registered ≠ licensed ≠ live, and the policy that every licensing claim we publish carries the date we last checked it against a primary registry. Everything above this line happened after that rule was in force.

    Entries dated before June 11, 2026 record corrections made during pre-publication verification of the dataset, logged here for completeness when the site launched.