iGaming CRM software versus a customer data platform: what Optimove, Fast Track, Xtremepush, Smartico and Solitics do, what a CDP adds, and what to ask vendors.
Updated
A customer data platform (CDP) can connect player records, consent and risk signals across brands. Your licences and local rules shape the design. Review limits, exclusions, data location and audit records. Use these guides to prepare tests with your compliance team.
Who this is for: CTOs, compliance leads, heads of CRM and data protection officers at licensed operators running more than one brand or licence.
Licensing geography defines the architecture
Regulatory drivers at a glance
Scroll horizontally to compare all columns ↔
| Driver | What regulators ask for | Examples — Checked on 2026-10-17 | Guide |
|---|---|---|---|
| Hosting and localisation | Gambling system or data in-country, or provable access | Sweden main rule; Brazil Article 4; Malta replica; Spain inspection access | Residency |
| Regulator data access | Records the authority can inspect directly | UK licence condition 2.1.1; Germany Safe-Server | Residency |
| Identity across accounts and operators | Link accounts; join shared registers | UK 3.9.1, GAMSTOP, GamProtect; Germany LUGAS; Netherlands CRUKS | Single customer view |
| Real-time safer-gambling action | Monitor, intervene, evaluate, allow contest | UK 3.4.3; Ontario Standards 2.10 and 2.11; Alberta | Interventions |
| Financial risk | Checks on high spend and vulnerability | UK GBP 150 per 30 days check; staged risk assessments announced 7 July 2026 6 | Interventions |
| Marketing suppression and consent | Fast removal of excluded players from marketing | UK two-day rule; Alberta | CRM vs CDP |
| Retention | Fixed record-keeping periods | Germany five years, Spain six, Alberta logs seven archived | Residency |
Architecture patterns that follow
- In-country core where a market localises the system or data.
- Regulator-accessible replica where hosting is open but live access is required.
- Per-jurisdiction tenants so one market's rules never force a migration elsewhere.
- Central analytics on pseudonymised data, with re-identification keys held in the licensing country.
A customer-owned deployment (on-premise, in your own cloud account, hybrid or sovereign) lets you place each pattern where the rule requires; see on-premise, private cloud and self-hosted customer data platforms. PrivyCDP's reference deployment with a sovereign iGaming operator in the Middle East and North Africa runs air-gapped AI inference with in-region decisions at low latency; details are shared under evaluation on our cases page.
Guides in this section
- Player data residency by jurisdiction: hosting, regulator access and retention rules for the UK, Malta, Ontario, Alberta, Germany, Sweden, Spain, Brazil and more.
- Single customer view for gambling operators: GamProtect in 2026, its legal basis, and what an identity layer must do. General concept: single customer view.
- Responsible gambling interventions in real time: markers of harm, financial risk assessments, latency and audit.
- iGaming CRM vs customer data platform: vendors, differences, and questions to ask.
Scoping checklist
- List your licences, brands and the residency rule in each.
- Identify which data stores count as the regulated system or database.
- Check that exclusion, limit and consent state reach every channel in time.
- Confirm you can answer a regulator request from the licence boundary.
- Decide who owns the identity graph and the audit record.
Related terms
- Self-hosted customer data platform
- Customer data platform
- Single customer view
- Data residency
- Identity graph
Explore this collection
gaming
iGaming data residency by jurisdiction: what the UK, Malta, Ontario, Germany, Sweden, Spain and Brazil require for hosting and regulator access (Oct 2026).
Updated
Responsible gambling technology in 2026: what the UKGC, Germany, the Netherlands, Ontario and Alberta require, markers-of-harm models, latency and audit.
Updated
Single customer view for gambling: GamProtect status in 2026, the data it shares, its ICO-backed legal basis, and what a customer data platform must do.
Updated
Frequently asked questions
What is a customer data platform for iGaming operators?
It is a platform that unifies player identity, consent and risk state across brands and licences and feeds other tools. For regulated operators the key questions are where it runs, who holds the keys, and whether it can evidence every decision to a regulator.
Does the UK require player data to be hosted in the UK?
No. The Gambling Act 2005 triggers licensing by where remote gambling equipment sits or where the facilities are used, but sets no hosting location. Licence condition 2.1.1 instead requires licensees to permit inspection of remote equipment and supply data copies on request 12. Residency still matters in other markets, such as Sweden and Brazil.
Can one customer data platform serve several licences?
Yes, if it can enforce different rules per market: in-country stores where a market localises data, regulator replicas where live access is required, and pseudonymised central analytics for the rest. A single shared tenant in one region struggles with that mix, because one market's rule becomes every market's constraint.
Is a customer data platform the same as an iGaming CRM?
No. A CRM decides and delivers campaigns, bonuses and rewards; a customer data platform governs the identity, consent and audit data underneath and feeds the CRM. Most operators need the CRM and, with several brands or licences, also a data layer they control. Our comparison covers vendors and the questions to ask each.
Where should we start?
Map your licences to the drivers table above, note which data stores each rule touches, then run a deployment qualification to test whether a customer-owned deployment fits your licence set, your teams and your timelines. Read the residency guide first if you are entering a new market.
Sources
- Gambling Act 2005, section 36 Open source
- UK Gambling Commission, Licence conditions and codes of practice (version effective 29 July 2026) Open source
- Portaria SPA/MF 722/2024 Open source
- Medida Provisória 1.394/2026 Open source
- Spelinspektionen guidelines for SIFS 2022:3 Open source
- UK Gambling Commission, Financial risk assessments update, July 2026 Open source
Put this evaluation into practice.
Assess your deployment requirementsThis article is general information, not legal advice.
Further reading
- Deployment patterns
- Deployment readiness checklist
- Self-hosted and on-prem CDPs
- iGaming CRM Software vs a CDP
- iGaming Data Residency by Jurisdiction
Published: · Updated:
Editorial dates describe content changes. Confirm current sources before making legal, security or purchasing decisions.