Compliance

Status#

• Certification. None of the four games is certified yet. The documentation for a test laboratory is ready — the model, the generator versions, the rounding policy, the simulation gate — and is shared on request, under NDA. The laboratory and the scope of certification are agreed with the distribution partner.
• Licence. We do not hold a supplier licence yet.
• Demos. The public demos are free play, with virtual credit that has no cash value.

Responsible gaming#

The operator's platform is the primary source. Deposit limits, self-exclusion and the operator's own session and loss limits stay with the operator. A stake the operator refuses as blocked, or over one of its limits, is shown to the player with that reason.

On top of that, the RGS enforces its own controls, per room. The defaults in operator builds are below; each can be changed per room on request.

• Time counts only while the game is connected and visible: it is credited by the server, not by the player's device. A session is continuous play: a 30-minute absence ends it and the next presence starts a new one; if the launch carries the operator's sessionId, a new value starts a new session too. A reconnection continues the same one.
• The last 24 hours of play are kept per player for 30 days, so the figure survives reconnections and redeploys. The session net result and the loss cap, instead, live in the memory of the game process and restart at zero after a redeploy: the integration guide (§10) says the same, and it is a known limit, not a surprise.
• The game's settings show the time played in this session and in the last 24 hours, the net result and the minutes left, and link the operator's responsible-gaming page.

Limits and controls#

• Per room: minimum and maximum stake, maximum win per position, maximum exposure per round, RTP, and the length of the betting window. In a room played on several tables the exposure cap holds for each table, so the room's worst case is the cap times its tables (at most 20 with players), a figure the operator confirms in writing.
• Per operator: limits set in our registry can only tighten a room's, never raise them.
• Before the wallet. A stake that breaks a limit is refused before the operator's wallet is called.
• Kill-switch, operated by us. A single room can be paused: open positions are refunded at once. An operator can be suspended: new stakes are refused in all of its rooms, while open positions can still be cashed out.

The player is the operator's#

• The only player identifier we need is the operator's pseudonymous player id. An optional display name, chosen by the operator, becomes the in-game alias.
• What we hold per player: that pseudonymous id, the alias, the times of the first bet and of the last visit, the promotion opt-out flag, and the game history needed for fairness and disputes. No name, email address, identity document or payment data ever reaches us.
• We run no communication with players.

No simulated activity with real money#

Demo rooms have simulated participants and scripted chat, marked [BOT]. Real-money rooms have neither. The server enforces it: it is not a setting to remember.

The room chat#

Every room has a chat. The server masks profanity, insults and slurs in English, Spanish and Italian before any other player reads the message: the first letter stays, the rest becomes asterisks. It is a word filter, not moderation: it does not read context, and it does not change player aliases.

Promotions#

• Free bets exist today in demo rooms only.
• Per-player opt-out. One signed call excludes a player from every promotion, present and future. It is meant to mirror the operator's harm indicators (UKGC Social Responsibility Code 3.4.3, requirement 10).
• Bonus balances, wagering and withdrawal rules stay with the operator. When free bets reach the operator's wallet, they will be marked as such on the wallet calls, never accounted by us.
• A new player who never cashes out raises a signal to the operator, who decides what to do with it. We pay no bonus of our own on an operator's players.

Audit trail and disputes#

• Every round is stored after settlement with its revealed seed, generator version and configuration, and can be re-derived at any time: see Provably fair.
• Every player command, accepted or refused, is stored append-only with the time the server received it.
• Operators read rounds, bets with their timeline, daily reports and a settlement export through signed reads. A dispute is settled on the same data.
• Every administrative action in our console is recorded in an audit log, including the ones taken on an operator's written request.

Privacy#

The privacy policy of this site covers the public demos.