Resources

AN OPERATOR’S GUIDE

Player Data Ownership in White-Label Lottery: Access, Export & Exit Checklist

Many buyers negotiate launch timelines, product mix and revenue share before asking who controls the player relationship. Once the platform is live, changing the answer can be expensive. A white-label lottery agreement needs more than a sentence saying that the operator owns its data: it needs a workable plan for access, permitted use, exports and exit.

Monthly reports provide visibility. They do not, by themselves, let an operator rebuild CRM audiences, reconcile wallets or preserve customer-support history after changing vendors. Use this procurement checklist to turn broad promises into requirements that the business, technical and legal teams can evaluate together.

Reliable data access strengthens CRM, retention, segmentation and analytics. Weak access makes the operator dependent on the provider not only for infrastructure but for learning. The practical question is whether the relationship intelligence created after launch remains usable when commercial terms change.

Separate ownership, access, control and legal roles

Commercial ownership language, operational access and data-protection roles are different questions. An agreement may allocate rights in a database or reports while limiting API access. A user may see information in a dashboard without permission to export or reuse it. Neither arrangement automatically determines who is a controller or processor.

For the UK GDPR, the ICO distinguishes a controller that determines processing purposes and means from a processor acting on its behalf. Assess roles for the actual activities, not simply the contract label. Other jurisdictions and operating arrangements require their own assessment. Read the ICO explanation of controllers and processors.

Ask who decides how registration, payments, verification, fraud detection and marketing work. Record each answer against the platform modules and responsibility model. This is procurement guidance, not a legal determination of ownership or processing roles.

Inventory the data that keeps the business running

Identity, transactional, behavioural, support and marketing records have different purposes and restrictions. Fraud signals may include third-party information that cannot be transferred in the same way as your own transaction ledger. Specify the deliverable and any exclusions for each category.

Example data-access schedule for a white-label lottery procurement discussion
Data categoryEvidence to requestContinuity check
Player accountsStable identifiers, account status and field dictionaryCan authorised teams join records across systems?
Wallets and transactionsLedger entries, currency, timestamps and adjustment referencesCan finance reconcile balances and open items?
Tickets and eventsTicket lifecycle, draw references and event definitionsAre unresolved tickets and settlement states identifiable?
Marketing permissionsChannel, purpose, notice version, timestamp and withdrawal historyCan the receiving CRM preserve restrictions?
Support and verificationCase references, status and documented access limitationsCan teams handle ongoing cases without unsafe copying?
Risk and audit recordsAction history, retention schedule and export exclusionsWhat evidence remains accessible after termination?

Add owners, refresh frequency and retention decisions to this schedule. Use synthetic sample records during procurement, not live player information.

Make the export specification testable

“CSV export available” is not an acceptance criterion. Specify column names, encoding, identifier types, currency precision, time zones, null values, relationships and schema versioning. Request a data dictionary, sample files and an explanation of incremental updates, deleted records and historical corrections.

The W3C tabular-data model explains how metadata describes rows, columns and datatypes across tabular formats. It is a useful technical reference, not a guarantee that two CSV files are compatible. See the W3C model for tabular data and metadata.

Agree export frequency, delivery method, authentication, rate limits, failure notifications and support responsibilities. Separate routine access from a final exit export, and identify assistance fees in the platform pricing and total-cost discussion. Do not include production credentials or API secrets in sample exports.

Reconcile value, not just record counts

A file can contain every player and still fail a migration. Transaction records may use different settlement states, ticket references or timestamps. Define a finance-approved reconciliation pack: account totals, currency totals, unsettled tickets, pending withdrawals, adjustments and exceptions.

For example, 10,000 exported accounts do not prove that every wallet balance or unresolved payout is represented correctly. Use an agreed snapshot time, trace selected synthetic transactions end to end and record unexplained differences. Decide how updates between the snapshot and cutover will be handled. Include this work in the go-live readiness checklist, with a named acceptance owner.

Preserve CRM permissions without assuming portability

An email address and a Boolean opt-in are rarely enough to understand a marketing permission. Request its channel, purpose, capture source, timestamp, relevant notice version and subsequent changes. Preserve withdrawals and suppression rules so an import does not reactivate people who opted out.

Ask whether the receiving system can retain that context, and have the privacy team assess whether the planned use and transfer are permitted. Do not assume a new platform, brand or purpose inherits permission automatically. Likewise, a contractual bulk-export arrangement is not the same question as an individual’s statutory portability rights. Migration plans need both technical mapping and appropriate privacy assessment.

Control staff access, vendor access and AI use

Specify who can view, change and export each category. Include privileged provider access, approval workflows, access removal, authentication and audit-log availability. Ask what logs show who exported information, when, for which authorised purpose, and whether that evidence remains accessible during an incident or exit. Tie these requests to the security and SLA evaluation.

Ask separately about aggregated analytics, fraud networks and AI systems. Which data enters each system? Is it used only to deliver your service, or for another purpose such as training a shared model? What are the retention, third-party access and contractual restrictions? Request the claimed anonymisation method and its review basis rather than treating the word “anonymous” as sufficient evidence.

Write and rehearse the exit process

Before signing, agree notice periods, export scope, delivery deadlines, migration support, charges and access during transition. Identify records that may need retention, who holds them, and how authorised retrieval works. Do not promise universal deletion: retention obligations and permissible transfers depend on the data, jurisdiction and arrangement.

The ICO’s UK controller-processor contract checklist covers processing scope, security, sub-processors, assistance, end-of-contract provisions and audits. Its guidance is currently marked as under review following the Data (Use and Access) Act; use it as a scoped reference and obtain advice for your arrangement. Read the ICO contract checklist.

  1. Export an authorised synthetic dataset through the proposed process.
  2. Import it into a separate test environment and validate identifiers, states and permissions.
  3. Reconcile the agreed totals and document gaps, costs and delivery time.
  4. Record acceptance, remediation and a repeat-test trigger for material schema changes.

Attach the results to your provider evaluation and RFP pack. A rehearsed exit reduces uncertainty; it does not establish that a live transfer is legally or operationally approved.

Define an export that can actually be restored

An exit clause is not operationally useful if the export lacks relationships or cannot be interpreted. Specify a documented schema, a consistent extraction point and the evidence required to restore a usable operating state. A file download alone is not proof of portability.

  • Include stable identifiers linking player controls, wallet postings, tickets, draw references and outstanding obligations.
  • Document field meanings, currencies, timestamps, status values and rule versions, including how deleted or restricted records are represented.
  • Define the initial snapshot and subsequent changes so events during transition do not disappear or get imported twice.
  • Use synthetic records to restore the export into an isolated environment and reconcile balances, entitlements and unresolved operations.

Link the export specification to the migration acceptance plan and integration data contract. Agree who resolves missing references and differences before terminating access; readable tables and a usable restored state are different acceptance criteria.

Frequently asked procurement questions

Does a white-label operator automatically own every player record?

No universal answer follows from “white label”. Review commercial rights, processing roles, permitted uses and third-party restrictions for each activity and data category. The operating model alone does not settle those questions.

Is receiving monthly reports enough to avoid vendor lock-in?

No. Reports can support management but may omit the identifiers, history, permissions and transaction detail needed for continuity. Evaluate usable exports and transition assistance, not reporting access alone.

When should we test exports?

During due diligence where practical, then before accepting the integration and before a live migration. Use synthetic or otherwise authorised test data. Agree when material platform changes require another scoped test.

Bring a data-control schedule to the fit call

White-label arrangements can support a strong operator business when responsibilities and continuity requirements are explicit. Bring your market, operating model, current systems and required data categories; request evidence for the specific configuration rather than assuming any vendor includes every feature. Discuss your platform and data-control requirements with WhiteLotto.

Wojciech Lysak is the Managing Director of WhiteLotto.com. LinkedIn