Protect players at every operator, not just one.
One exclusion register, shared with every licensed operator. When an excluded player plays anywhere in your market, the right officer knows, and operators never see a name.
Player protection
ExclusionEX-2026-0412
Recorded byAn operator · self-exclusion
Shared withEvery licensed operator
Sent asplayer token
Excluded players playingThe token turned up in another operator's feed
AlertThe problem
An exclusion only works if every operator knows.
A player who excludes themselves at one operator can open an account at the next. Each operator keeps its own list, and nobody checks one against another.
Sharing names to fix that creates a new risk. The register has to reach every operator without handing out who is on it.
How it works
One register, every operator, no names.
- 01RecordSelf-exclusions from operators, exclusions your officers record, and groups from other agencies.
- 02ShareEvery operator receives the register as player tokens, never as names.
- 03MatchPlay in the feeds is matched against the tokens, however your office chooses to identify players.
- 04ActAn alert, then a case, then the violation the library sets for letting an excluded player play.
What's included
From the register to the penalty.
One exclusion registerEvery exclusion in the market in one place, whoever recorded it, with its term.
Player tokensOperators check players against the register without ever learning who is on it.
Excluded players alertRaised when a token turns up in any operator's play.
Identity checksAlerts when an operator's player tokens look wrong, and an audit of how players are identified.
Banned personsLists of people banned from gaming, screened by ID across licensees and their owners.
A penalty set in advance"Underage or excluded players allowed to play" is in the violation library with its demerits and penalty.
Used by
The register, and everyone it reaches.
Player protection officersRecord exclusions, review them, and lift them on the record when their term ends.
Compliance officersFollow up the alerts and open a case when an operator lets an excluded player play.
OperatorsReceive the register as tokens and check every player against it.
FAQ
About player protection.
Do operators see who is excluded?
No. Operators receive player tokens, not names. They can tell whether a player is on the register, but not who else is.
How are players identified?
Your office chooses which details identify a player, and the tokens are built from those.
What happens when an operator lets an excluded player play?
The alert can become a case, and the case can end in the violation the library sets for it, with its demerits and penalty, so every operator is treated the same.
Share one register across your market.A three-month pilot on your own register and operators.
Ask about a pilot