Skip to content
iGamingX

Responsible gaming

In production

Protection the server enforces.

Deposit, loss and session limits, reality checks, cool-⁠offs and self-⁠exclusion, checked on every stake and deposit. One definition of a protected player is read before bonuses, messages and rewards.

What it does

  • Limits that hold

    Daily, weekly and monthly deposit limits, a daily loss limit, session time and reality checks. Tightening applies at once; relaxing waits at least 24 hours, for players and staff alike.

  • Cool-off and self-exclusion

    Breaks of 1 to 168 hours and self-⁠exclusion from 24 hours to permanent. An excluded player can still see the balance and history, withdraw, file a complaint and reach support. Play and offers stay closed.

  • A register that follows the person

    Exclusions are stored as keyed hashes of identity, email and document, checked at sign-⁠up, sign-⁠in and KYC, shared across one owner's brands. Compliance can load a national list.

  • One gate for incentives

    Bonuses, rewards, CRM messages, pop-⁠ups and grants made by staff all ask the same question before acting: is this player protected right now?

  • Rules per jurisdiction

    Waiting periods, break ranges and exclusion options are set per operator and per country, never below the legal floor the platform holds.

  • In pilot

    Default limits at sign-up

    Limits an operator applies to every new player, with a durable notice to the player. Built and deployed, switched off until an operator turns it on.

By the numbers

  • Limit types

    6

  • Self-exclusion

    24 h to permanent

  • Wait to relax a limit

    24 h

    minimum; 72 h in Spain

Details

Checked at the stake, not on the page

Every vertical debits a stake through the same wallet function, and that function checks the loss limit, the break, the session time and a due reality check before the money moves. Deposit limits are checked when the deposit starts, over rolling 24-hour, 7-day and 30-day windows.

The daily loss is read from a stake journal under a per-player lock, so parallel bets cannot slip past the limit.

Per operator, per jurisdiction, with a legal floor

Compliance writes the periods per jurisdiction, each change with its reason and its before and after in the audit trail. Each player falls under their own country and the licence's, and the most protective rule wins.

The incentive policy is Balanced or Strict per operator. Strict is the floor in demanding jurisdictions, and only a platform administrator can change that, citing the legal validation.

What is earned is never lost

A protection decides where money is paid, never whether. Prize money for a self-excluded or paused player goes to a withdraw-only balance that no bet, provider or bonus can read.

Two people for the sensitive steps

Lifting a self-exclusion early is refused by default. Where a jurisdiction allows it, one person asks and another approves, and a permanent exclusion can never be lifted from the console. Exempting a namesake from a register match follows the same rule and expires.

  • Every limit change keeps the previous value, the requested value, who asked and when it applies.
  • Not available yet: wager limits, weekly or monthly loss limits and a problem-gambling score.

Contact

Tell us what you are building.

Markets, brands, verticals. We show you the platform with your case in mind.

Talk to sales