Themes ›
Data & Privacy

Data & Privacy

Data localisation, KYC data handling, retention and cross-border transfer.

Flags
38
Jurisdictions
35
Read order
Theme-major

5 further jurisdictions with flags in this theme are in expert review and not shown until published.

Cross-jurisdiction posture cluster

38 flags across 35 jurisdictions. Posture mass: Rules 18 · Risks 7 · Reality 13.

Worked examples

Each links back to the full jurisdiction page — the theme view is a projection of those country ledgers.

🇲🇲 Myanmar →
Junta-linked SOE engagement

SAC entities under targeted OFAC sanctions (E.O. 14014).

1 data & privacy flags on this jurisdiction · see full country page
Michigan — State →
Accepting out-of-state wagers

Participant must be within Michigan; geolocation is mandatory.

1 data & privacy flags on this jurisdiction · see full country page
Quebec — Canada (province) →
Law 25 data protection regime

Any future entrant must comply with stringent QC privacy law.

2 data & privacy flags on this jurisdiction · see full country page

Rules · Risks · Reality across the cohort

Lens · which facet of each jurisdiction’s flags:
Showing all facets.
Accepting out-of-state wagers

Participant must be within Michigan; geolocation is mandatory.

Junta-linked SOE engagement

SAC entities under targeted OFAC sanctions (E.O. 14014).

Mishandling biometric/sensitive data

Ley 25.326 classifies biometric data as sensitive and restricts international transfers.

Tax-rate change conflicts with baseline spec

Downstream analyses using 15% mobile figure will be wrong.

Non-GDPR-compliant processing

GDPR + Bulgarian DPA apply.

GPS geo-gating required

Out-of-state wagers must be blocked at the device level.

GDPR / AKI player-data enforcement

Player data processing must meet GDPR and Estonian DPA.

DPC registration and cross-border transfer approval

Data-flow constraints under Act 843.

NIK cross-checking of accounts

Players identifiable via national ID linkage.

Holding PK player data for gambling

Data tied to unlawful activity compounds criminal exposure.

No DPO/NDPA registration

NDPA 2023 obligations and NDPC investigations

SRC-NG-002
Ignoring Ley 81/2019 obligations

APDATOS supervises data protection; non-compliance risks sanction.

Incomplete transaction history

Complete account history must be available to the government on request.

Mandatory in-state geolocation

No interstate liquidity; breach risk under Wire Act.

Western scrutiny over DR Congo/M23

Aid-threat and reputational pressure raise banking and macro risk for inbound investors.

Collecting Saudi player data for gambling

PDPL and cybercrime exposure compound gambling-prohibition risk.

Improper personal data handling

Data protection embedded in licensing.

Assuming no localisation/operation requirements

Decree 147/2024 requires cross-border providers to establish domestic operations.

Serving players outside Spain on .es licence assumptions

Operators must geo-restrict and comply with foreign rules.

Non-compliance with PDPA No. 9 of 2022

Software compliance with data protection law required.

Operating in 'sensitive geographic areas'

GCGRA designates sensitive zones where access is blocked.

Failing bettor data protection

Statutory confidentiality duty.

Law 18-05 hosting/.com.dz requirements

Domestic hosting / domain requirements add compliance friction.

Ignoring FIPPA/PIPEDA obligations

Data handling is governed by FIPPA/PIPEDA.

No dedicated gambling data-protection rules

Reliance on sectoral cyber/telecom laws creates compliance ambiguity.

Overreliance on PRODHAB protections

Limited enforcement; not a gambling-specific framework.

Data localisation status not yet assessed

Published specs do not confirm localisation requirements.

Weak data-protection regime (Ley 172-13)

Player-data governance rests on an underdeveloped law.

Operating telecom-adjacent service

Cybercrime Law Art. 2 mandates 180-day user-data retention.

KDPA 2019 cross-border transfer rules

Data transfers outside Kenya require adequate protection.

Data retention duties S.L. 583.12

Compliance overhead for record retention.

Active licensee count dynamic

Confirm count against MLGCA database before commercial reliance.

Law 25 data protection regime

Any future entrant must comply with stringent QC privacy law.

Geolocation confinement to QC residents

Technical geo-gating required for any compliant offering.

Unpublished fee point-figures

Budgeting uncertainty.

Cross-border data transfer authorisation (Law 2004-63)

Adds compliance overhead for any data processing

Data Protection and Privacy Act 2019 obligations

Compliance overhead for player data handling.

Mandatory database registration / breach notification

URCDP obligations apply to entities operating locally.