<aside> 🧩

Optional. Configured entirely through the JWT token — no separate integration required.

</aside>

Splash can restrict a player's access to a game out of the box, using either or both of the mechanisms below. Both are set in the JWT described in Authentication (JWT).

Restricted flag

Setting "restricted": true in a player's JWT prevents that player from entering the game; omitting the field, or setting it to false, allows normal entry. This is the simplest option and covers straightforward cases — for example a self-excluded player or one flagged by risk management.

Tag-based restrictions

For more granular allow/deny logic, populate the tags array in the JWT with one or more free-text strings. Splash can then be configured to prevent or allow entry based on the presence or absence of specific tags:

• Block on presence — e.g. prevent players tagged self-excluded or region-blocked from entering.
• Allow only on presence — e.g. restrict a promotional instance to players tagged vip or beta-tester.
• Compound rules — e.g. block entry unless a player carries both an age-verified and a region-eligible tag.

Tag values and their restrict/allow behaviour are client-specific and agreed with Splash during integration, since tag names and how they're treated (block-list vs. allow-list) vary by operator.

Example (both mechanisms)

{
  "restricted": true,
  "tags": ["self-excluded", "region-blocked"]
}