Upcoming regulatory changes
LLM-extracted from regulator announcement pages across 12 jurisdictions. Review each impact before pushing tickets to your team.
Upcoming changes detected
4
Impacts pending review
9
LLM-processed
4
Changes
| Regulator | Effective | Summary | Confidence | Impacts | |
|---|---|---|---|---|---|
| UKGC | 7/31/2026 | UKGC publishes amendments to RTS 14E (game-information display) requiring an in-session player-spend summary panel to be visible within two clicks at all times. Operators have 90 days from publication to comply. Existing RTS Annex A reporting requirement expanded to include the new panel-availability metric. | AI 92% | 6 5 pending | Open → |
| CA-ON-AGCO | 8/15/2026 | AGCO announces that game-certification renewal cycle extends from 24 to 36 months effective Q3 2026 for non-major-revision titles. Major revisions still require fresh full certification. Operators may apply for retroactive extension on existing certs expiring after the effective date. | AI 94% | 2 2 pending | Open → |
| MGA | 8/31/2026 | MGA publishes amendment to Player Protection Directive Part II §3 — bonus-wagering requirements may no longer exceed 35x for new players (down from 50x). Free-spin bonuses must disclose maximum-conversion ceiling at the point of acceptance. MGA expects operator self-attestation within 90 days. | AI 88% | 2 2 pending | Open → |
| FR-ANJ | 9/28/2026 | ANJ publishes décret tightening online-casino bonus regulation: maximum welcome-bonus capped at €100 (down from €200). Players must wait 14 days between bonus acceptances. Effective in 120 days; operators expected to update T&Cs and bonus engines. | AI 86% | 0 | Open → |
How this works
KURAL watches official regulator announcement pages across all configured jurisdictions daily. When the page hash changes, the LLM extraction pipeline pulls the summary, effective date, and cited clauses out of the regulator's text via Claude Sonnet, then maps cited clauses to existing controls in your library via the source-citation index. Every extraction is logged with token cost + prompt hash in LlmCallLog.
AI-assessed fields show their confidence — anything below 85% waits in the per-impact review queue (open a change to triage). Once impacts are approved you can push them to Jira as future_compliance_gap findings — due date is set to the effective date minus 30 days.