Beyond the Pop-Up: How UKGC and Spelinspektionen Are Redefining Session Control Obligations

The regulatory argument about session controls has moved on. Two of Europe’s most technically demanding regulators, the UK Gambling Commission and Sweden’s Spelinspektionen, have each built session-control frameworks that treat the periodic pop-up reality check as a minimum compliance threshold, not a completed obligation. Compliance teams that configured their systems to the 2019 standard and left them there are now running behind what both regimes actually require.

This article examines what each framework mandates in precise technical terms, where the two regimes diverge in approach and prescription, and what that means operationally for licensees holding authorisations in both markets.

What Does UKGC RTS 13 Actually Require?

RTS 13, published 2 February 2021 and last updated 21 January 2025, sets out the UKGC’s technical requirements for time management within remote gambling sessions. Its stated aim is to provide customers with facilities to assist them in keeping track of the time they spend gambling. The standard covers three requirements, each with a different scope of application.

RTS 13A applies to all remote gambling except telephone gambling. Where a gambling system uses full-screen client applications that obscure the clock on the customer’s device, the application itself must display either the time of day or the elapsed time since the application was started. The UKGC’s implementation guidance specifies that time of day may be drawn from the customer’s device or from server time, displayed in hours and minutes, and that elapsed time should be displayed in minutes and hours. This is not a player-optional feature, it is a mandatory display obligation on the system.

RTS 13B is the provision most compliance teams associate with reality checks, and it applies to remote gaming (including bingo but excluding peer-to-peer gaming), remote instant win lotteries, and high frequency lotteries. The gambling system must provide easily accessible facilities enabling customers to set a frequency at which they will receive and see on screen a reality check within a gaming session. The UKGC defines a reality check as a display of the time elapsed since the session began, and the customer must acknowledge the reality check for it to be removed from the screen.

The reality check must prevent a new game within an auto-play sequence from commencing until the player has acknowledged the reality check.

That obligation, drawn directly from UKGC RTS 13B implementation guidance, has material system design implications. It is not satisfied by a dismissible notification that a player can bypass while a game continues in the background. The auto-play break is mandatory.

The implementation guidance for RTS 13B also sets constraints on default settings. Where a default time period is offered, it must be set at the minimum, not at a longer interval that reduces the frequency of interruptions. A pre-set list of intervals is permitted, but the range must be reasonable and appropriate. Where possible, a player’s preferences should be applied to all future account logins or gaming sessions. If the system cannot carry preferences forward, the licensee must provide clear information explaining that the player will need to set a reality check for each session. The guidance also specifies that the reality check should offer the customer the facility to exit the gaming session or log out, and should provide a link to the customer’s account history.

RTS 13C applies specifically to casino products, excluding peer-to-peer poker. It requires that elapsed time be displayed for the duration of the gaming session. The implementation guidance clarifies that the timer should begin either when the gaming session starts or when the customer first plays a game, and that it should be persistent on screen throughout the session.

The Time-Out Obligation: LCCP SR Code 3.3.4

Separate from the RTS technical standards, LCCP Social Responsibility Code 3.3.4 imposes a distinct session-level obligation on remote licensees. Licensees must offer a time-out facility for customers for the following durations: 24 hours, one week, one month, or such other period as the customer may reasonably request up to a maximum of six weeks.

This provision applies to all remote licences with a defined list of exclusions (ancillary remote betting, remote betting platform, gaming machine technical, gambling software, host, ancillary remote bingo, ancillary remote casino, and remote betting intermediary trading-room-only licences are excluded from scope). The time-out facility differs from self-exclusion, it is a shorter-term cooling-off tool. But it interacts with session-level RG design in an important way: a licensee whose session controls fail to surface the time-out option within the reality check interaction is likely failing the spirit of LCCP 3.4.3 (remote customer interaction) even if it technically satisfies RTS 13B in isolation.

LCCP SR Code 3.4.3, which came fully into force on 31 October 2023, requires licensees to implement effective customer interaction systems and processes that embed three elements: identify, act, and evaluate. Session-control data, specifically patterns of session length, frequency, and player responses to reality checks, constitutes evidence that feeds the identify element of that cycle. A licensee that deploys a technically compliant reality check but never uses the session data generated by it to trigger customer interaction has satisfied the letter of RTS 13 while arguably undermining LCCP 3.4.3.

How Spelinspektionen’s LIFS 2018:2 Prescribes More

Sweden’s responsible gambling framework rests on Spellagen (2018:1138), specifically Chapter 14, which establishes the duty of care. Chapter 14, Section 1 requires that the player must be protected from excessive gambling, and places an ongoing obligation on licence holders to monitor players’ gambling behaviours continuously. The operational detail of session controls is carried in the Spelinspektionen regulations issued under the original regulatory mandate, principally LIFS 2018:2.

Section 9 of LIFS 2018:2 governs session-time limits. The player must be able to limit how much time they spend logged in each day, week, and month. This is not an optional feature that operators may offer, it is a mandatory player-facing tool. The accredited testing body is required to verify that the possibility of setting login-time limits is offered to the player. The distinction from the UKGC model is architectural: under LIFS 2018:2, session-duration limiting is a required player tool from the moment of account access, not a technical design standard applied at the game level.

Section 13 of LIFS 2018:2 addresses the notification obligation for online gambling under Chapters 7 and 8 of Spellagen. Licence holders must give players regular, clear, and varied notifications of their wins and losses, as well as information about how long the player has been logged in. Those notifications must be displayed as often and for as long as is needed to counteract excessive gambling. The notification must then be acknowledged by the player, and when the player confirms it, they must be given the opportunity to choose to either end their gambling session or continue.

Under Spelinspektionen’s LIFS 2018:2 Section 13, session notifications must be regular, clear, and varied, and each must be acknowledged before play can resume, with the player explicitly offered the option to stop.

The word “varied” is operationally significant. A system that repeatedly surfaces an identical message at a fixed interval arguably fails this requirement because the notification lacks variety. Spelinspektionen’s intent, reflected in the supporting accreditation guidelines, is that players receive information they are likely to engage with rather than habituate to and dismiss.

Section 15 of LIFS 2018:2 adds a further obligation: on every login to online gambling, the player must receive clear information about the licence holder’s responsible gambling measures, the player’s own deposit limitations under Chapter 14, Section 7 of Spellagen, and the player’s accumulated losses for the past twelve months. This is not a periodic notification, it is a per-login mandatory disclosure. Compliance teams building multi-jurisdictional RG frameworks should note that this twelve-month cumulative loss display at login has no direct UKGC equivalent in the RTS.

The accreditation guidelines published in SIFS 2022:3 (as updated May 2025) further confirm that licence holders must continuously visualise the player’s session time and account balance on screen throughout the session. The guidelines state explicitly that the requirement to continuously show the player’s time consumption is not a hindrance to, or alternative to, the regular notifications required under LIFS 2018:2 Section 13. Both obligations run simultaneously, the persistent display and the acknowledged notifications are cumulative, not substitutable.

Side-by-Side: What Each Regime Demands

Requirement	UKGC (RTS 13 / LCCP 3.3.4)	Spelinspektionen (LIFS 2018:2 / Spellagen Ch. 14)
Session timer display	Mandatory (RTS 13A: time of day or elapsed time where full-screen app obscures device clock, RTS 13C: persistent elapsed time for casino)	Mandatory continuous display of login duration (SIFS 2022:3 guideline on Section 9)
Player-set session duration limit	No direct RTS mandate, time-out up to 6 weeks (LCCP 3.3.4)	Mandatory: daily, weekly, monthly login-time limits (LIFS 2018:2 Section 9)
Reality check / session notification	Player-set frequency, must acknowledge, auto-play interrupted (RTS 13B)	Regular, clear and varied, frequency sufficient to counteract excess, must acknowledge and choose to stop or continue (LIFS 2018:2 Section 13)
Notification content	Time elapsed since session began (RTS 13B definition)	Wins, losses, and time logged in (LIFS 2018:2 Section 13)
Per-login disclosures	No specific per-login mandatory content equivalent	RG measures, player’s own deposit limits, 12-month cumulative losses (LIFS 2018:2 Section 15)
Time-out / cooling-off tool	24h, 1w, 1m, up to 6w (LCCP SR Code 3.3.4)	Session limitation through player-set login limits, Spelpaus for exclusion
Scope (gaming products)	RTS 13B: remote gaming incl. bingo, instant win, high-frequency lotteries (excl. P2P)	Chapters 7 and 8 of Spellagen, online gambling including casino and betting

What Does Enforcement Tell Us?

The UKGC’s settlement with Stakelogic BV in June 2026 is the clearest recent signal that session and game-pacing obligations carry enforcement weight for software suppliers, not just operators. Stakelogic’s slot titles were found to be running with cycle times below the 2.5-second minimum required under RTS 14D, in one case, a gap of 1.97 seconds between game cycle starts. The investigation expanded when Stakelogic retested its entire UK-market portfolio and found 15 further titles also failed the standard by margins ranging from 0.001 to 0.675 seconds. The UKGC settlement reached £122,835.

The case is instructive for session-control compliance for two reasons. The root cause was Stakelogic’s reliance on manual stopwatch testing, which consistently misread the cycle interval. The lesson for RTS 13B compliance is the same: manual configuration review of reality-check intervals and acknowledgement gates is insufficient. Operators and their software providers need automated regression testing against the specific RTS parameters on each product version. The UKGC’s explicit statement that RTS 14D targets risks linked to the intensity of gameplay, citing research showing faster game speeds increase consumer vulnerability, applies equally to session-control design, the pacing of interruption is the protective mechanism, and deviations from it are not technical trivialities.

Spelinspektionen has not published a comparable single enforcement action against an operator specifically for LIFS 2018:2 session notification failures in the most recent reporting period. However, Spelinspektionen’s supervisory framework requires accredited testing bodies to verify, at the point of technical certification, that session-time limitation tools under Section 9 are present and functional. A failure at certification would prevent go-live, which means the enforcement pressure is structural rather than post-market in the Swedish model.

The Operator Compliance Gap: Player-Set vs. Operator-Constrained Controls

The sharpest structural difference between the two frameworks is the degree to which they trust player choice versus mandate operator configuration. Under UKGC RTS 13B, the player sets the frequency of reality checks, and the operator must provide a reasonable range from which to select. The system must surface a default at the minimum of that range, but the player can select a longer interval. The UKGC’s model is player-led within operator-defined parameters.

Spelinspektionen’s LIFS 2018:2 Section 13 does not specify a fixed interval. Instead, it mandates that notifications appear as often as needed to counteract excessive gambling. That standard is outcomes-oriented rather than configuration-oriented. An operator that sets a once-per-hour notification and finds that segment of its player population continues to exhibit markers of excessive gambling has not satisfied Section 13 simply by having a notification system active. The duty of care under Chapter 14, Section 1 of Spellagen is ongoing and requires the licence holder to monitor player behaviour continuously, and the notification frequency must reflect that monitoring.

In practice, this means Swedish licensees should be documenting the basis on which they set notification frequencies, and reviewing those settings against player behavioural data. A standard implementation that mirrors the UKGC’s player-configured model without any assessment of whether the resulting frequency is sufficient for the Swedish player population is vulnerable to supervisory challenge.

Implementation Considerations for Multi-Licence Operators

Operators holding both a UKGC remote gambling licence and a Swedish gambling licence must manage two technically distinct session-control frameworks within what may be a shared platform. The following points identify where the frameworks create specific design constraints.

On notification content, RTS 13B’s definition of a reality check covers elapsed session time. LIFS 2018:2 Section 13 requires that notifications cover wins, losses, and login duration. A single notification template that displays only elapsed time satisfies the UKGC standard but does not satisfy LIFS 2018:2 for the Swedish market. Operators serving both markets must either maintain separate notification templates per market or build a notification that exceeds the UKGC minimum by including win and loss data, which the UKGC standard does not prohibit.

On per-login disclosures, LIFS 2018:2 Section 15 requires that every login to online gambling in Sweden triggers a display of the player’s responsible gambling measures, their deposit limits, and their twelve-month accumulated losses. This has no UKGC analogue in the RTS. Operators must implement this as a Swedish-specific gate at the login flow, independent of whatever session-level notifications they deploy during gameplay.

On session-duration limiting tools, LIFS 2018:2 Section 9 requires that players be able to set limits on daily, weekly, and monthly login time. The UKGC’s equivalent is the LCCP 3.3.4 time-out facility, which is structured differently, it is a cooling-off mechanism rather than a recurring usage cap. The two do not satisfy each other. An operator that offers only the LCCP 3.3.4 time-out structure to Swedish players has not met Section 9 of LIFS 2018:2.

On auto-play interruption, UKGC RTS 13B requires that no new game within an auto-play sequence can commence until the player has acknowledged the reality check. Spelinspektionen’s framework addresses auto-play directly in its game design standards, specifically, SIFS 2022:3 Section 3 requires that repeated choices must not be placed in a queue, and choices must be the player’s. The prohibition on queued auto-play actions in Sweden means that the acknowledgement gate is structurally embedded in Swedish product design standards as a categorical constraint rather than a reality-check-specific rule.

Where Both Regimes Are Headed

The UKGC’s Autumn 2023 consultation and subsequent “We Asked, You Said, We Did” response introduced additional constraints on game design that interact with session-control obligations. The prohibition on autoplay for all online gaming products (RTS 8, now extended beyond slots), the ban on operator-led multi-game functionality for casino products (RTS 14C), and the 5-second minimum game cycle for non-slots casino titles (RTS 14G) all reduce the mechanical speed at which a player can progress through a session. These changes do not amend RTS 13 directly, but they alter the environment within which reality checks operate, a slower session means the same notification frequency carries a different proportional impact on play rhythm. Compliance teams should model this interaction when calibrating default notification intervals.

Sweden’s ongoing channelisation debate, the concern that prescriptive RG requirements contribute to player migration to unlicensed offshore operators, has not translated into any relaxation of LIFS 2018:2 session requirements. Spelinspektionen has maintained the regulatory intensity of the Swedish responsible gambling framework while pursuing offshore operators through separate enforcement channels, including the reporting on unlicensed affiliate and social media promotion published by Spelinspektionen in July 2026. The direction of travel in both jurisdictions is toward more prescriptive session-level controls, not fewer.

Compliance officers responsible for the responsible gambling compliance function across multi-jurisdictional operations should treat the UKGC and Spelinspektionen frameworks as an instructive comparison for modelling what second-tier jurisdictions may introduce. Several markets currently operating player-optional reality check models, with no acknowledgement requirement and no content mandate beyond elapsed time, are architecturally behind where both the UKGC and Spelinspektionen positioned themselves at their 2021 and 2018 implementation dates respectively. The trajectory is toward mandatory acknowledgement, structured content, and operator-owned frequency obligations tied to behavioural monitoring, not toward player-configured voluntary tools.

For operators holding or assessing a UKGC licence, the RTS 13 requirements should be read in full alongside LCCP 3.4.3 and the Commission’s formal guidance on customer interaction for remote gambling licensees. Session data is both a technical compliance output and an operational input to the customer interaction duty. The two functions are not administratively separable, even if different teams within a licensee own them.

Key Resources

UKGC Remote Gambling and Software Technical Standards, RTS 13: gamblingcommission.gov.uk (last updated 21 January 2025)

UKGC Licence Conditions and Codes of Practice, SR Code 3.3.4 and 3.4.3: gamblingcommission.gov.uk

Spelinspektionen LIFS 2018:2, Regulations and General Advice on Responsible Gambling: Available via spelinspektionen.se regulatory document archive

Spellagen (Swedish Gambling Act) SFS 2018:1138 consolidated to SFS 2024:255: riksdagen.se

UKGC Public Statement, Stakelogic BV (RTS 14D settlement, June 2026): gamblingcommission.gov.uk