Skip to main content

Player protection

A recommender in a casino must never nudge someone who has asked to stop or whom the responsible-gambling team has flagged. Kaleido GRE treats this as a gate before any scoring: a suppressed customer gets an empty list, whatever the settings say.

The list​

recommender.suppressed_customer holds CustomerId, Reason (up to 200 characters) and an optional Until. It is written by the platform's responsible-gambling system:

MethodPathEffect
PUT/suppressed/{customerId} { reason, until? }Add or update; in force on this instance at once
DELETE/suppressed/{customerId}Remove
GET/suppressedFirst 1,000 entries

An entry whose Until has passed no longer suppresses. A compacted Kafka topic suppression is created alongside the event topics for a future streamed feed of the same list.

Failing closed​

SuppressionCache reloads the whole list into memory every 5 seconds. If the list has never loaded, or has not refreshed for 60 seconds, every request returns an empty list with the reason "The suppression list is unavailable, so no recommendations are shown." "We could not check" must never mean "show them".

Request sequence​

Observability​

SignalUse
kaleido.gre.suppression.age (gauge, seconds)Alert well before 60: past it the gate is closed for everyone
kaleido.gre.suppression.size (gauge)Customers on the list
kaleido.gre.suppression.refresh.failures (counter)Failed refreshes
kaleido.gre.recommend.duration{result="suppressed"}How often the gate closes

What it is not​

The recommender obeys a list; it does not detect risky play. The casino's player-protection system has to fill the list.