iGaming Platform Data Ownership & Exit Rights

The operator is the defensible controller and owner of player and operational data; EveryMatrix retains its software and derived-IP rights. AI terms also reserve performance data and, unless the customer opts out in writing, a license to use customer data to train or improve EveryMatrix AI. Retention and post-exit handling remain contractual.

DataHub can continuously replicate player, wallet, sports, casino, engagement and payment data into an operator-controlled environment; bet-at-home maintains its own data platform. A complete exit package covering credentials, KYC files, AML notes, bonus state, unsettled transactions and transition support is not established.

Exports include CSV, APIs and a dedicated Kafka stream. Power BI is a destination, not an export format; dedicated-server delivery is a topology rather than a format.

Transaction-level drill-downs, financial reporting, batch delivery and historical data replay are supported.

Standard for a licensed PAM. The operator holds the licence and acts as data controller; Playtech runs IMS as the processor. Exact ownership terms are contract-specific.

Operator control of the player relationship and PAM reporting make migration possible, but outbound database schema, self-service dump, transition SLA, deletion confirmation and assistance package remain contract-specific.

PAM+ is an open platform with integrations and detailed reporting; a complete raw player and transaction export API is not established.

A regulated PAM with reconciliation and detailed reporting exposes transaction records to the operator; the full exit-format schema and retention package are contract-specific.

The operator owns its player database at all times.

SOFTSWISS must assist transfer of the operator-owned database when the operator changes provider. Formats, timing and cost remain contract-specific.

Reporting exports and Affilka interfaces do not establish the format of a complete player-database exit dump; require the full schema and delivery method in the contract.

One 2023 customer agreement assigns Customer Data to the operator, consistent with the CPU model.

One 2023 customer agreement requires return of all Customer Data and up to six months of transition services; exact formats and fees remain deal-specific.

Data Lake includes defined views, and one executed agreement requires exit data transfer; the universal schema remains contract-specific.

Michigan required sole customer ownership and no-cost export; NeoGames' technical response did not meet the exclusive-ownership requirement. Final executed rights and the portfolio-wide standard remain unresolved.

Michigan provides a no-cost customer-specified extract within five business days. iGaming scope, schemas and equivalent rights are contract-specific.

The Michigan benchmark requires customer-specified extraction within five business days; exact formats for other products are contract-specific.

The Michigan contract requires customer-specified extraction but does not define a universal transaction-history export scope.

Legal data ownership is contract-specific across turnkey and white-label models. PAM visibility and behavioural-data storage do not establish ownership.

Player-database portability rights, format, completeness, timing and cost remain contract-specific.

Export formats, schemas, completeness and historical scope are contract-specific.

A complete operator export of transaction history is not established.

Operators own the player relationship and player data. Kambi uses aggregate betting data across its network to improve pricing and risk models.

The operator owns the player relationship whether it uses Kambi's PAM or an external PAM. Portability terms and export formats still need explicit contract protection.

Partner reporting and bet-level data are exposed through integrations and downloadable reporting; direct SQL access is not part of the managed-service model.

Bet-level reporting is available to partners; the bulk export format remains unresolved.

Contract-dependent export from OPS.

Pariplay processes game-session and campaign data needed to deliver Fusion, while the operator keeps the player account, wallet and master record.

Pariplay does not host the operator's player database.

The Client Area exposes game information, rules, certification and marketing assets; exact operational export formats are partner-gated.

Game-history/reporting data is available to the operator; the PAM remains the authoritative financial ledger.

Turnkey operators own their data, brand and roadmap. In a white-label structure the provider or licence holder processes and controls more of the player relationship. Exact controller, processor and exit rights depend on contract.

Turnkey operators own their data, but a complete player-schema export, delivery timetable and contractual right to migrate the database to a competing platform remain unresolved.

JSON/XML sportsbook and feed APIs, versioned endpoints and downloadable feed archives are available. They do not cover a complete player, KYC, wallet or ledger export for exit. CSV, SQL, SFTP or API scope, schema, retention and delivery timing remain contract-specific.

Paydrom transaction management and platform reporting expose transaction data, but complete export of the retained transaction history, its format and retention window remain unresolved.

In operator-licensed PAM, traffic, transaction, personal and customer information belongs to the customer or its licensors; White Hat receives only processing rights needed to perform the services. Provider-licensed white label remains a separate model.

Operator-licensed PAM includes no-charge export of all Customer Information in a mutually agreed file format after termination or expiry. This right does not automatically apply to provider-licensed white label.

Exit export uses a mutually agreed file format; CSV, SQL and API availability remain unresolved. Kafka and Segment streaming are not the termination-export format.

Transaction Data is customer-owned and included in the contractual Customer Information export requirement.

Operators retain player-data ownership in API deployments; white-label access can be narrower and remains contract-specific.

Data ownership, export tools and migrations support portability, but a tested full exit pack and time-bound assistance remain contract-specific.

Transaction, casino and sportsbook monitors support controlled CSV exports and API access.

Standard CoreX customers are operator-licensees administering player accounts and operational data. Universal title and exit rights remain contract-specific; the residual SkyCity white label is a separate model.

Incoming migrations are established. Complete outbound player-database and handover rights remain contract-specific, depending on negotiated export scope, notice and fees.

SQL connectivity, API delivery and operational exports are available through CoreX and DataX. A complete exit export right is not established.

Real-time reporting and transaction visibility do not establish a contractual right to export the complete transaction history.

Operator owns its player relationship and operational data; Bragg processes data to deliver the service.

Exportable in principle for operator-licensed PAM customers; format, timing and exit fees are contractual.

Yes for operator reporting and audit obligations.

Turnkey operators control their own licensed operation, while white-label rights depend on the named licensed entity and contract; no single universal owner applies.

The turnkey operator owns its licence; full player/KYC/ledger export rights and portability commitments remain contract-specific and unresolved.

Reporting exports use CSV/XLS. Full player, KYC and ledger migration-out formats remain private; API and SQL export are not established.

Moneygrator exposes transaction history and BI exports CSV/XLS; complete transaction-ledger export remains unresolved.

The position is model-dependent: stand-alone and turnkey operators retain control through data replication, while white-label player data is processed inside BetConstruct's licensed and operated environment. Contract terms decide the exact controller, processor and exit rights.

The data-replication service gives operators control of player information. Full migration rights, formats and exit assistance remain contract-specific, and white-label portability depends on the agreement.

Back-office reports can be created and delivered automatically, and Swarm/Partner APIs expose operational data. Direct SQL dumps and the complete file-format inventory remain unresolved.

Operator-owned in turnkey and contract-dependent in white label. Client-base retention is contractual, while the licensed entity and its processors control parts of the operational data flow until migration.

Customer-base retention is contractual, but completed execution remains unresolved. Export mechanics are contract-specific, and several operator reviews allege difficult or costly exits.

Back-office reports can be exported; complete player-database export and its formats remain contract-specific and unresolved.

Yes, through back-office reporting.

Player-data ownership is contractual and must not be inferred from access or migration features.

Migration-in includes data portability; complete player/KYC/AML/balance/bonus/transaction export and a post-termination migration-out right remain contract-specific and unresolved.

APIs and evidence/report exports are available; the complete CSV/SQL/file-format matrix remains unresolved.

PAM and compliance tools provide transaction histories, reports, and regulator-ready evidence packs.

Migration-out service, handover scope and exit-team assignment are contract-specific.

One 2020 full-stack agreement could not terminate sooner than 48 months from launch. This is a single-contract benchmark, not a universal EveryMatrix term.

The contractual start period was 36 months, but the 12-month notice structure prevented ordinary termination before month 48. This should not be universalized across modules.

Technically feasible under the modular migration provisions in the Caliente reset, but only if export scope, parallel running, assistance hours, fees and deletion obligations are contracted.

Three years is not a universal minimum. It is the average period for contracts carrying setup fees; strategic platform, government and dedicated-product agreements can be materially longer.

The operator owns the player database, and SOFTSWISS must assist transfer to a replacement provider.

Negotiate a transition period aligned with database export, PSP/content replacement and regulatory notifications.

The standard minimum term remains unresolved.

One executed agreement provides orderly data transfer and up to six months of transition services; current standard scope and price are deal-specific.

Migration & Onboarding services; QuinnBet is a documented migration onto the platform.

Historical customer-specific convenience mechanics, not a current standard policy.

Initial term in one 2023 customer agreement.

The Michigan customer-specific benchmark permits transition assistance for up to 90 days at existing contract rates.

Michigan customer termination-for-convenience benchmark; not a universal supplier notice period.

This is an iLottery range, not a standard private iGaming commitment.

The Palms Bet migration was inbound to Altenar; contractual migration-away support remains unresolved.

Palms Bet received hands-on inbound replacement and go-live support; outbound exit assistance remains unresolved.

The termination-notice period is contract-specific.

The initial and minimum contract term is contract-specific.

Kambi cooperated on DraftKings' 2021 migration to its own technology and structured Kindred's phased transition, so leaving is achievable and has happened repeatedly.

Repeatedly taken over books from other suppliers (e.g. Pickwin replacing its prior sportsbook; OLG PROLINE from FDJ Gaming Solutions).

Kindred's migration was announced years ahead and DraftKings' transition was coordinated, indicating planned rather than abrupt separation.

Strategic partnerships use multi-year or long-term terms; exact initial terms are contract-specific.

Contract-dependent.

Yes for OPS/OGS onboarding.

Operator retains PAM/player data; exit is primarily a content/API replacement and game-ID/certification exercise governed by contract.

Yes for content catalog, game-ID, wallet callback and certification transition; not a player-database migration.

Inbound migration into Centrivo is supported; outbound migration service, transition team and post-termination assistance remain unresolved.

MagicBetting Online completed a migration to Centrivo, while Winmasters transitioned onto Digitain across Greece, Romania, Cyprus and Malta. Inbound migration is established; outbound assistance remains unresolved.

The termination-notice period remains unresolved.

The minimum contract term remains unresolved.

Operator-licensed PAM includes commercially reasonable transition services, continued access and functionality for a mutually agreed run-off period of up to one year.

VIP Play retired ZenSports on 28 April 2025 and launched its White Hat-powered app on 12 May. Complete player-balance and account migration quality remains unresolved.

The known operator-licensed PAM terms are four years initially, automatic two-year renewals and 180-day non-renewal notice. Transition can continue for up to one year at the operator's cost.

Followed by automatic two-year renewal terms.

GR8 supports inbound migrations and operator data ownership; outbound assistance remains contract-specific.

The termination-notice period is contract-specific.

The minimum commitment period is contract-specific.

Incoming migration specialists and middleware are available; outbound transition assistance remains contract-specific.

Customer agreements generally require six months' notice before ending the current term.

Available as a negotiated exit service; the standard package is contract-specific.

Yes, subject to source-system cooperation and data mapping.

The Bragg termination-notice period is contract-specific. Contract length and renewals do not establish notice mechanics.

Migration-out service, handover checklist and a named exit team are unresolved.

Implementation support exists; competitor-specific data mapping and migration guarantees are unresolved.

The termination notice period is contract-specific and unresolved.

The minimum commitment period is contract-specific and unresolved.

Data replication and operator control are positives; an explicit outbound-migration service is not established.

The termination-notice period is contract-specific and unresolved.

The minimum term is contract-specific and unresolved.

Partial and contract-specific. A path from white label to independent operation exists, but the migration-out SLA, checklist and guaranteed deliverables are unresolved.

Partial and assessed per project. Custom integrations and independent migrations are supported; a standard inbound migration package is not established.

The minimum contract term remains unresolved.

No verified migration-out commitment.

The standard notice period is contract-specific and unresolved.

Contract-specific and unresolved.

Legal ownership of player accounts between the brand, B2C licensee and technology supplier is contract-specific.

The PAM gives operators operational visibility over player behaviour, preferences and activity from registration through gameplay; complete export rights, legal ownership and post-termination access remain contract-specific.

The exact player-funds holder is partner- and contract-specific. It may be the licensed B2C partner, merchant entity or PSP; Altenar is not the universal fund holder.

White-label operators can transition to a more independent operating model without changing providers. This is an in-platform transition path, not unrestricted external exit rights, player-database portability or post-termination access.

Turnkey operators own their data and brand. White-label ownership, CRM rights and post-termination use depend on the operating entity and contract.

White-label operators receive operational access to player profiles and reporting, but unrestricted raw-data access, bulk export and post-termination use are not standard entitlements. Turnkey provides stronger data control; legal and portable access remains contract-dependent.

The white-label licensed entity, merchant account holder and PSP settlement chain remain contract-specific. Turnkey is operator-licensed and operator-held, but no universal white-label fund holder can be assigned.

White label is a shared platform with limited technical ownership and control. Brand, domain, player-data and balance portability therefore require explicit contract rights; unrestricted exit is not included by default.

The brand partner owns the commercial brand relationship, while White Hat is licensed operator and data controller in provider-licensed white label. Exact database and post-termination rights remain contractual.

White-label access covers operations and reporting rather than unrestricted raw database access or post-termination reuse. Full ownership and export rights apply to operator-licensed PAM.

In provider-licensed white label, White Hat Gaming Limited is the B2C licensee responsible for player liabilities; the safeguarding account or PSP structure remains unresolved. In operator-licensed PAM, the operator holds the liability.

A white-label migration depends on controller roles, player notices or consent, regulator approval, PSP settlement and the partner agreement. Operator-licensed PAM includes customer-owned data, free export and up-to-one-year transition rights.

The operator builds the brand and acquisition base, while the licensed white-label entity controls regulated player relationships. Contract wording can shift the balance.

GR8's platform supports real-time reporting and export; white-label contracts must preserve access and exit rights explicitly.

The Light White Label B2C entity, merchant account holder, PSP settlement chain, safeguarding terms and player-funds holder remain unresolved.

Technical migration is supported, but moving a white-label player base depends on consent, licence, KYC and contract terms.

Database ownership, marketing-consent ownership, controller/processor roles and post-termination player rights are contract-specific and unresolved for white label.

A centralized back office is supplied; complete export and post-termination portability remain private.

The white-label licensed entity, merchant-account holder, safeguarding arrangement and settlement chain are unresolved. Slotegrator cannot be assumed to hold funds universally.

A new licence/entity, PSP setup and player/KYC transfer may be required; migration-out commitments are contract-specific and unresolved.

The operator can manage player accounts and transactions through BackOffice. 'Full' describes operational access, not a right to export every field on exit; portability is contract-specific.

The fund holder varies across white-label markets. The licensed affiliated operator, merchant entity and PSP settlement chain must be named in the contract; turnkey operators maintain their own licence and wallet.

Full operational access; export scope contract-specific.

The provider entity and PSPs hold funds in white label; the operator and PSPs do so in turnkey. SoftGamings supplies white-label financial infrastructure. Crypto wallets are non-custodial to SoftGamings, but fiat settlement and reserve arrangements remain contract- and PSP-specific.

Operator independence and customer-base retention are contractual, but completed exit execution remains unresolved. Allegations of difficult exits make explicit handover clauses essential for databases, domains, balances, creative assets and timing.

Commercial relationship, account, database, CRM and post-termination rights are contract-specific. Provider licensing does not by itself transfer player ownership.

Operators receive scoped partner access, CRM, PAM, analytics, and audit views; legal ownership remains contractual.

Fund custody depends on the exact B2C licensee, merchant, safeguarding institution, PSP and contract. The white-label label alone does not establish physical or legal custody.

Technical migration-in and portability are supported; external brand-migration rights, player-data handover, regulator transition and post-termination support remain contract-specific and unresolved.