Responsible Gaming

Player-protection controls are only worth what they enforce. This chapter says exactly where the guards run, and where they do not.

What a player can set

Each of the three money limits can be set per 24 hours, per 7 days and per month. The limits page is one card with a row per kind, and each active limit has a usage meter ("$120.00 of $500.00", the amount left, and the rolling window it counts: the last 24 hours, 7 days or 30 days). The meter turns amber from 80% and reads Limit reached at the cap. Open deposit intents, and tips received from other players, count toward the deposit meter, exactly as they do when a deposit starts. Editing opens a per-kind dialog that tags each field Applies now or In 24 hours as the player types, so the asymmetry below is visible before the confirm step. A longer period may never carry a lower limit than a shorter one (the weekly limit cannot be below the daily, the monthly not below the weekly), and the same check applies again when a waiting raise lands. If an exchange rate is missing the meters are hidden, but the limits themselves still show and still enforce.

One limit covers every wallet

A limit governs all of the player's play, not just the wallet in its own currency. The player sets limits in USD, and every deposit, stake and win in every other wallet — fiat or crypto — is converted into the limit's currency and counted against it, so a player cannot step around a limit by switching currency. A crypto stake placed through a fiat-priced game is counted at the exchange rate frozen on that round when the game prices in the limit's currency, so a retried check reaches the same verdict.

If an exchange rate the check needs is unavailable, the action is refused rather than decided at a guessed rate — counting an amount at the wrong rate would silently widen the limit, which is the failure that harms the player.

The asymmetry rule

Tightening a limit takes effect immediately. Loosening it does not.

A player lowering their deposit limit is protected from that moment. A player raising or removing it waits 24 hours first, and can cancel the pending change from the limits page. Saving any change to a limit also cancels a raise still waiting for it, so a stale raise cannot land over a later, stricter limit. This is the behaviour regulators require, and it is implemented in the limit-change logic rather than left to the interface.

Where the guards actually run

This is the part worth scrutinising, because a limit that is collected, stored and displayed but never consulted is worse than no limit at all — it looks like protection.

The guards run on:

• Sports bet placement
• Game launch
• Every casino provider wallet callback — so a player cannot bypass the launch check by keeping a session open
• Casino settlement
• Deposit initiation

Deposit limits additionally count in-flight deposit intents, not just settled money, so two concurrent deposits cannot jointly breach a limit that either alone would respect.

A tip another player sends is money arriving in the recipient's account, so it answers to the recipient's own deposit rules: their verification standing and region, self-exclusion, and deposit limits with open deposits counted. A tip the recipient could not deposit is refused, and the sender is only told the recipient is unavailable, never why. Received tips count toward the recipient's deposit limit usage.

When a deposit is refused for a limit, the player sees the amount and window that caused it and a link to the limits page. Starting a break signs the player out; they can sign back in at any time to withdraw. A timed break reads as a break, with its end date and a note that withdrawals stay open; only a permanent exclusion uses the self-exclusion wording.

Self-exclusion additionally suppresses the reward surfaces — streaks, missions and reward prompts — which disappear entirely rather than rendering greyed out, and an excluded player accrues no progress toward them. See Gamification & Rewards.

Concurrency

Checking a limit and then acting on it is a race: two simultaneous bets can each read a passing total. The platform takes a row lock on the player's limit scope inside the same money transaction as the debit, on all three paths — bet placement, casino debit, and deposit initiation. Concurrent operations cannot both observe a passing total.

Operator controls

Deposits that breach a responsible-gaming rule land in a flagged-deposit queue in the backoffice for staff review. Staff can also suspend a player outright, which revokes their sessions.

Scope & Roadmap

Implemented. Deposit, loss and wager limits per timeframe; self-exclusion; cool-off (which signs the player out); limits ordered day <= week <= month; tips held to the recipient's deposit rules; the tighten-now/loosen-later asymmetry; limits counted across every wallet currency with refusal on a missing rate; enforcement on bet placement, game launch, every provider callback, casino settlement and deposit initiation; in-flight intent counting; lock-protected check-then-act on all three money paths; the flagged-deposit review queue; player-facing pages for every control, with usage meters, cancellable pending raises and a single reality-check control, plus a public help section.

Partial. The player-facing limits page sets limits in USD only; enforcement already converts every wallet into the limit's currency, but a player cannot yet choose to set a limit in another currency. A missing exchange rate blocks the affected action until a rate is available again.

Only stakes from the player's cash wallets count toward spend and loss limits; wagers funded from a bonus balance do not. That follows from how the limits are measured rather than from an explicit, documented policy decision — confirm it matches your licence conditions.

On test environments, the staging-only top-up tool skips limit checks when it credits a player, but its credits still count toward that player's deposit allowance, so heavy use can make a test account hit its own deposit limit.

Reward suppression covers self-exclusion and cool-off breaks but not a player who has hit a deposit, loss or wager limit. The platform now reports how much of each limit is used, but only for display on the limits page; it is deliberately never fed back into a gate, and "has a limit" is not "reached a limit" — treating them as equivalent would hide rewards from every player who ever set one.

Not built. Reality checks are stored and configurable but never delivered — the player can pick an interval and sees a preview of the reminder, but nothing emits it during a session. There is no national self-exclusion register integration (GAMSTOP, OASIS, ROFUS, SPELPAUS), which is a licence condition in most regulated markets. There is no behavioural risk detection — loss-chasing, escalating stakes, night-time play — feeding interventions, and no age verification distinct from identity verification.