Most UK-licensed slot apps switch off promotional push notifications between 21:00 and 07:00, but that's a voluntary restraint, not a rule. When the alerts resume just after 07:00, they arrive into a very specific window: the tail end of the night session, when a player who has been awake since 2am is most receptive to a "your balance is waiting" nudge. The 3am question isn't really about what happens at 3am — it's about what's queued up to fire at 7:01.

The overnight silence isn't regulation

It's worth being precise about why your phone goes quiet. The Gambling Commission's remote technical standards and the CAP advertising code don't impose a blanket overnight curfew on push notifications. What they do impose is consent, clear opt-out, and — since the 2020 CAP guidance on gambling ads — a requirement that marketing isn't targeted at or likely to appeal to under-18s. The overnight quiet is a product of individual operators' own "responsible marketing" policies, most of which were tightened after the 2021 review of the CAP code and again around the 2023 white paper fallout.

That matters because voluntary codes are the first thing to bend. An operator can change its notification policy in a terms update with 30 days' notice, and most players never read that email. If you want to know what your app does at 3am, you need to look at what it's allowed to do, not what its marketing page says it does.

The practical result is a patchwork. Some apps genuinely stop all marketing pushes overnight. Others stop only "promotional" pushes but keep "service" messages — deposit confirmations, bonus expiry warnings, "your free spins expire in 4 hours" — running 24/7. That second category is where the interesting behaviour lives, because a free-spin expiry warning at 03:40 is functionally a prompt to open the app and play.

What actually fires when the switch flips

The 07:00 queue

If you've ever woken to four notifications stacked on your lock screen, you've seen the backlog. Operators that suppress overnight sends typically queue them and release at the start of the permitted window. The result is a burst in the first 30 minutes of the marketing day. Industry send-time data (Braze's annual benchmarks put gambling among the highest-volume push categories, with open rates that routinely clear 8–12% versus a cross-sector average nearer 3–4%) explains why: push is cheap and it works, so the temptation is to catch the commuter before they've opened anything else.

For a player who's been awake since 2am, that 07:01 alert lands differently than it does for someone who slept. It reads as continuity rather than interruption.

Session-aware messaging

The more sophisticated apps don't just queue — they segment. If your account shows a session that ended at 03:15, a 07:00 "come back and finish your spins" message is a different animal from a generic promo. Nothing in the licence conditions prohibits it. The Commission's customer interaction guidance (under LG-D2 and the customer interaction requirements introduced in 2022) asks operators to identify harm indicators, and a 3am session on a weekday is one of the more obvious ones. Whether that indicator gets used to protect the player or to time a message is entirely down to the operator's internal controls.

This is the honest answer to the title question: at 3am, most apps are doing nothing visible. What they're doing is deciding what to send you when they're allowed to speak again.

The numbers that shape the overnight window

A few concrete anchors worth holding onto:

• 05:00 is the most common end of the voluntary overnight suppression window across major UK-facing operators, though 07:00 is also widespread.
• The Commission's customer interaction guidance expects operators to act on indicators including "gambling at unusual times" — which explicitly covers the small hours.
• Under the 2023 white paper proposals and subsequent consultations, the direction of travel is toward mandated friction: stake limits on online slots (consulted at £5 per spin for adults under 25 and £15 otherwise, with the £15 figure landing in 2025), financial risk checks, and tighter marketing rules. None of these directly govern push timing, but they set the tone.

The gap between "we voluntarily go quiet overnight" and "the regulator requires us to" is where most of the practical risk sits for players. Voluntary restraint is a marketing decision and can be reversed. A licence condition cannot.

What to check on your own phone

If you want to know what your apps are actually doing, the settings are more revealing than the marketing copy.

On iOS: Settings → Notifications → [app] → check whether "Deliver Quietly" is on and whether "Time Sensitive" is enabled. Time Sensitive notifications bypass Focus modes, and some gambling apps request that permission for what they frame as service messages.

On Android: Settings → Apps → [app] → Notifications → check the channel breakdown. Many apps split "promotions" from "account" channels, and you can kill the first without losing deposit confirmations. Few players realise the channels exist.

In-app: look for a "communication preferences" page, usually buried under account settings rather than responsible gambling. If you can only toggle "all marketing" rather than set quiet hours, that tells you something about the operator's priorities.

The blunt option — turning off all notifications and checking the app when you choose to — remains the most effective. The friction of opening an app deliberately is exactly the friction that overnight pushes are designed to remove.

The open question

The interesting development isn't what apps do at 3am. It's whether the regulator will ever treat notification timing as a customer interaction issue rather than a marketing one. The Commission has been willing to act on design features — the 2021 ban on autoplay and loss-chasing features on slots, the 2024 rules on reverse withdrawals — and push timing sits in the same category of "nudge architecture" that those rules targeted.

If a 07:01 message aimed at someone who was spinning at 03:15 is a harm indicator being monetised rather than mitigated, it's hard to see how it survives the next round of consultation. The question is whether operators will self-police the queue before they're made to — or whether the first enforcement case will be the thing that finally sets the quiet hours in code rather than in policy.