iGaming Responsible Gambling
Compliance
Self-exclusion architectures, mandatory limits, customer-interaction triggers and the safer-gambling rulebooks across 17 regulated markets. Primary-source guidance on what you must do, when, and how.
Two architectural models
Two Models. One Player-Protection Obligation.
Every regulated iGaming market protects players through either a national cross-operator self-exclusion register or an operator-level self-exclusion mechanism. The two architectures produce materially different operator obligations, supervisory expectations and integration costs. Both demand mandatory deposit and time limits, reality checks, customer-interaction triggers and a designated responsible-gambling officer.
National Self-Exclusion Register Model
Used by: UK (GAMSTOP), Denmark (ROFUS), Sweden (Spelpaus), Germany (OASIS), Spain (RGIAJ), France (Interdiction Volontaire), Colombia (single-CC register), Brazil (centralised under Portaria 2.579/2025)
Operator-Level Self-Exclusion Model
Used by: Curaçao (post-LOK), MGA (Maltese B2C), most US states (NJ DGE, MGCB, PGCB, OCCC), Peru (DGJCMT MINCETUR), Ontario (AGCO BetGuard transitioning to cross-operator)
Quick reference
Key Thresholds at a Glance
Side-by-side comparison of mandatory reporting thresholds, program requirements, and compliance obligations across both frameworks.
| Obligation | 🏛️ National Register Model | 🏢 Operator-Level Model |
|---|---|---|
| Self-exclusion architecture | Cross-operator register operated by the regulator | Per-operator register maintained under regulator standards |
| Register query at login | Mandatory real-time check against national list | Operator queries its own customer base only |
| Cross-operator block | Yes, by design (single exclusion blocks every licensed operator) | No (unless a national list exists separately) |
| Minimum exclusion term | Set by regulation (e.g. UK 6 months / 1 year / 5 years; Sweden 12-month default) | Set by regulation (e.g. NJ DGE 1 year / 5 years / lifetime) |
| Reality checks / session limits | Mandatory under social-responsibility code | Mandatory under operator standards |
| Mandatory deposit limit | Mandatory in most national-register markets (DE, FR, ES, SE pending; UK affordability framework) | Voluntary tools mandatory; default cap by operator under regulator standards |
| Customer-interaction triggers | Codified in operator licence conditions plus algorithmic detection | Operator-defined risk-detection mandated by the regulator standard |
| Marketing suppression on exclusion | Mandatory across every licensed operator in the jurisdiction | Mandatory by the operator on whose list the bettor self-excluded |
⚠ Jurisdiction-specific rules apply within each model; the table above identifies the architectural differences, not the local rule for any individual operator decision. Always verify against the regulator instrument that applies. Not legal advice.
Browse by topic
Coverage by Topic
Each topic section below curates articles from the Responsible Gambling pillar. Click a chip to jump straight to that topic.
Self-Exclusion Registers
National vs operator-level self-exclusion architectures: GAMSTOP, ROFUS, Spelpaus, RGIAJ, Interdiction Volontaire, Registro de Personas Prohibidas and cross-channel mechanics.
- Curaçao Post-LOK: What Operator-Level Self-Exclusion Now Actually Demands Under the CGA
- Peru’s Registro de Personas Prohibidas: Cross-Channel Self-Exclusion Obligations Under MINCETUR DGJCMT
- Coljuegos and the Cedula-Based Single-Account Rule: How Colombia Achieves Cross-Operator Self-Exclusion
- Brazil Portaria SPA/MF 2.579/2025: The Centralised Self-Exclusion Register and Mandatory Autolimits Decoded
- Cross-Operator Self-Exclusion: Comparing GAMSTOP, ROFUS, Spelpaus, and OASIS Across Jurisdictions
- SIFS 2026:3: Spelinspektionen Formalises Spelpaus API Requirements for Swedish Licensees
Deposit, Loss & Time Limits
Mandatory affordability mechanics: deposit limits, loss limits, time limits, single-bet caps and the regulator-set vs operator-set frameworks.
Reality Checks & Session Controls
Session-time notifications, net-position reminders, cooling-off, take-a-break, mandatory pause mechanics.
No articles published yet — first article on Reality Checks & Session Controls is coming. Check back soon.
Problem-Gambling Markers
Behavioural-monitoring markers of harm, PGSI screening, at-risk-bettor identification and disordered-gambling indicators.
No articles published yet — first article on Problem-Gambling Markers is coming. Check back soon.
Customer Interaction
Mandatory operator-to-bettor intervention triggers, outbound contact, safer-gambling messaging and the customer-interaction code provisions.
No articles published yet — first article on Customer Interaction is coming. Check back soon.
RG Marketing & Advertising
RG-protective advertising standards: whistle-to-whistle bans, vulnerable-customer targeting prohibitions, bonus disclosure, mandatory safer-gambling logos.
No articles published yet — first article on RG Marketing & Advertising is coming. Check back soon.
VIP & High-Value Customer Rules
VIP-scheme controls, enhanced affordability for high-value customers, account-management restrictions and the VIP-ban regimes.
No articles published yet — first article on VIP & High-Value Customer Rules is coming. Check back soon.
RG Officer & Training
Mandatory RG officer designation, senior-management responsibility, RG training cadence and policy-document requirements.
No articles published yet — first article on RG Officer & Training is coming. Check back soon.
Treatment, Helpline & Levy
Treatment funding, statutory levy, helpline signposting, GamCare / BeGambleAware / Adictel partner integration.
No articles published yet — first article on Treatment, Helpline & Levy is coming. Check back soon.
Cross-Channel & Cross-Operator
Cross-channel land-based-to-online RG mechanics, cross-operator player-level data sharing, single-account rules and unified protection frameworks.
- Peru’s Registro de Personas Prohibidas: Cross-Channel Self-Exclusion Obligations Under MINCETUR DGJCMT
- Coljuegos and the Cedula-Based Single-Account Rule: How Colombia Achieves Cross-Operator Self-Exclusion
- Single Customer View: Building One Across Brands Without Breaching GDPR
- Cross-Operator Self-Exclusion: Comparing GAMSTOP, ROFUS, Spelpaus, and OASIS Across Jurisdictions
Latest analysis
Latest Responsible Gambling Compliance Guides
Curaçao Post-LOK: What Operator-Level Self-Exclusion Now Actually Demands Under the CGA
The CGA's 2025 RG Policy replaces master-licence-era non-enforcement with nine binding obligations. Here's exactly what self-exclusion, marketing suppression, and behaviour tracking now…
Responsible GamblingPeru’s Registro de Personas Prohibidas: Cross-Channel Self-Exclusion Obligations Under MINCETUR DGJCMT
Peru's Registro de Personas Prohibidas spans land-based and online channels under Ley 27153 and Ley 31557. Know what operators must verify, when,…
Responsible GamblingColjuegos and the Cedula-Based Single-Account Rule: How Colombia Achieves Cross-Operator Self-Exclusion
Colombia's Coljuegos uses cedula identity to enforce a single-account-per-concesionario rule that produces cross-operator self-exclusion as a structural outcome. Here is how it…
Corpus
Primary Sources Indexed
Every article in this pillar cites the primary regulatory text directly — not summaries or secondary commentary. The sources below are fully indexed in our compliance corpus.
All articles cite primary regulatory text. Updated May 2026. Not legal advice — verify obligations with qualified AML counsel before implementing a compliance program.