Reality Checks and Game Notifications

1) What Reality Checks are and why they're needed

Reality Check is a periodic, unobtrusive notification that returns the player to awareness: reminds of the time in the game, the current result (win/loss), the available self-control tools and offers to pause or adjust the limits.

• Harm reduction and support for responsible behaviour.
• Compliance with license requirements and RG standards.
• Reduced complaints/chargebacks, increased brand credibility.

2) Typology of game notifications

1. Temporary Reality Checks - in N minutes/hours or by session thresholds.
2. Financial notifications - when the net loss threshold, total rates or deposit is reached.
3. Behavioral triggers - "chasing" after a loss, frequent lead cancellations, non-linear rate increases, night sessions.
4. System prompts - a reminder of an incomplete timeout, expired limit, active self-exclusion in the registry.
5. Informational notifications - RTP/odds, bonus rules, policy changes.

3) Design and UX principles (without "dark" patterns)

Neutral tone: no pressure to "get back in the game."

Visible pause: "Break 15 min "/" Take time out "button next to "Continue."

Transparent numbers: game time, net-result for the period (honest score).
Availability: large typography, contrast, localization.
No promos in the Reality Check window.
Delayed increase in limits ("cooling" 24-168 hours).
The easy way to the center of self-control: limits, timeout, self-exclusion.

• "You play 60 minutes. Current total: − €35 (from the beginning of the session). Take a break for 15 minutes or set up limits? [Break 15 min] [Limits] [Continue]"

4) Thresholds and frequencies (recommendations)

Time: first Reality Check in 30-60 minutes, then every 60 minutes.
Losses (net loss): soft tips at a − of €20/ − €50; tougher - at a − of €100/ − €200 (calibrate for currency/ARPPU).
Behavior: notification when the average rate rises> X% after losses; for ≥3 consecutive output cancellations, propose a timeout.
Night sessions: after 02:00 local time - enhanced prompts.
Frequency of impressions: frequency cap, so as not to cause irritation: no more than 1 notification every 10-15 minutes.

5) Gradations of interventions (ladder of actions)

1. Soft nujas: neutral Reality Checks, time/total counters.
2. Enhanced notifications: offer timeout/limits, risk explanation.
3. Mandatory pauses: 5-15 min lock with countdown timer.
4. Limits: temporary limit on deposits/rates.
5. Self-exclusion: recommendation or launch if risk thresholds are consistently exceeded.
6. Support contact: personal communication with reason-codes and the magazine.

6) Content guide: finished texts

• 'A break is fine. You play 60 minutes. Session total: − €35. Do you want to take a break for 15 minutes or set up a limit?

• "You have reached a loss limit − €100 for today. We recommend setting a daily limit or taking time out until tomorrow"

• "We see a rapid rise in rates after losses. It can be impulsive. Pause or reduce limits"

• "Late timing raises the risk of impulsive bets. A break of 15 minutes will help you maintain control"

7) Communication with limits, timeouts and self-exclusion

From the Reality Check window - direct buttons: "Set limit," "Time out 24 hours," "Self-exclusion...."

With the limit on, display progress (X% of the limit).
With active timeout/self-exclusion - do not show game prompts, only informational.

8) Personalization and fairness

Adapt the thresholds to the player's history (responsibly: without "fluff" for the game).
Store reason-codes for any automatic restrictions.
Provide an appeal to the person and an understandable explanation of the logic (explainability).

9) A/B testing rules (ethics and compliance)

Test wording/placement/timings, do not test "bypass" restrictions.
The main metric is a decrease in harmful patterns, not an increase in turnover.
Any tests should not impair the availability of the Break/Limits buttons.

10) Performance metrics and SLOs

Prompt Seen Rate: The proportion of users who saw the notification.

Action Rate: share of clicks on "Break/Limits/Timeout."

Harm-Signal Reduction: decrease in repeated signals (chasing, night sessions) in 30 days.
Time-to-Intervention: from the first signal to the action taken (<24 h).
Return-with-Control: proportion of returnees without relapse at 30/90 days.
Complaint/Chargeback Rate: Decline after implementation.

False Positive Rate: Proportion of complaints "too intrusive."

Availability SLO Reality Engine: ≥99. 9%.

11) Logging and provability

Logs of impressions/actions (time, trigger type, UI option, selected option).
WORM-log for regulatory checks (immutable).
Comparison with RG cases and outcomes (pause, limit, self-exclusion).

12) RACI (roles and responsibilities)

13) Checklists (operating)

Before launch

• Time/loss/behavior thresholds defined.
• Approved texts, locales, net-result format.
• Break/Limits/Timeout/Self Exclusion buttons are available in one click.
• Logs are enabled (impressions/clicks/exits), WORM log is connected.
• DPIA conducted for profiling and notifications.

In operation

• Monitor Action Rate and Harm-Signal Reduction.
• Weekly calibration of thresholds and frequencies.
• Verifies that there are no promo/bonuses in the windows.
• Suppression checking in marketing for high-risk.

Incidents/Failures

• Fallback mode: hard pauses when the notification engine is unavailable.
• Alerts on SLO and the rise in complaints.

14) Technical architecture (reference)

Event Bus (bets/deposits/sessions) → Risk Signals Service (rules + models) → Reality Checks Engine (timers, frequencies, texts, phicheflags) → In-App/Push Layer (UI, locales).
RG/Consent Layer: access to limits, timeouts, self-exclusion statuses, consideration of consents.
Audit/WORM: unchanging logs of impressions/solutions.
Admin Console: setting thresholds, texts, A/B options, viewing metrics.

15) Frequent mistakes and how to avoid them

Intrusive windows every 5-10 minutes → frequency cap and smart thresholds.
Promo in Reality Check is → prohibited; RG options only.
A complex path to the limits → a one-click button from the notification.
Dishonest net-result → take into account bonuses/conclusions/freespins.
Absence of → logs is impossible to prove compliance.
There are no reason-codes for enhanced measures → difficulty with appeals.

16) Implementation Roadmap (6 steps)

1. Policy and thresholds: define triggers, texts, DPIA.
2. Architecture: implement Risk Signals + Reality Checks Engine + logs.
3. UX/content: locales, availability, quick actions (break/limits).
4. Integrations: link with limits/timeouts/self-exclusion and suppression in CRM.
5. Monitoring: Action/Harm-Reduction/SLO metrics, alerts.
6. Improvement: A/B tests of formulations and timings, calibration of thresholds monthly.

Result

Reality Checks is not a pop-up "for the species," but an outline of awareness and protection: correct triggers, honest numbers, quick access to pause and limits, fair thresholds and provable operational discipline. This approach reduces the risk of harm, strengthens licenses and reputation and contributes to sustainable product growth.