Player protection that cannot be argued with.
Deposit, loss, wager and session limits, reality checks, cooling-off, timeouts and self-exclusion — with national register integration and the right asymmetry.
Responsible Gaming, precisely
Limits
Deposit, loss, wager and session, per period, enforced at the money boundary rather than in the interface where they can be skipped.
Correct asymmetry
A decrease applies immediately. An increase serves its cooling-off period first. Getting this backwards is a licence problem.
Reality checks
Configurable intervals with the acknowledgement recorded, because the acknowledgement is the evidence.
Cooling-off and timeouts
Player-initiated breaks that gate play without closing an account or losing history.
Self-exclusion
Including a port to national registers, with propagation rules and an explicit answer for the accepted-before-effective case.
Evidence
Every limit change, acknowledgement and exclusion is an audited record with a named authority behind it.
Contracts it exposes
- Commands
- SetLimit · ScheduleIncrease · ApplySelfExclusion · StartCoolingOff
- Reads
- GetLimits · GetExclusionStatus
- Events
- LimitChanged · SelfExclusionApplied · RealityCheckAcknowledged
What it never does
- Be bypassable by a support agent
- Apply an increase without its cooling-off
- Lose the record of a limit that has since changed
Every module on this platform is defined as much by what it is forbidden to do as by what it owns. That is what makes a boundary auditable instead of aspirational.
Regulators rarely ask whether you have limits. They ask you to show that a specific limit was in force at a specific moment for a specific player.
See it running
Every module here surfaces as screens an operator uses on a Monday. Ask for a walkthrough of the ones that decide your week.