A 20-minute idle timeout is standard across most regulated platforms. On a progressive jackpot screen, though, it's a trap: 63% of players who get timed out mid-session never make it back to the screen they were on. That figure comes from a 2024 audit of 4.2 million sessions across 11 operators, and it's the kind of number that should make anyone who designs these interfaces wince.

Timeouts exist for good reasons, and that's not the problem

Auto-logout rules are a responsible gambling tool. The UK, Malta, and a growing list of other jurisdictions expect operators to detect prolonged play and nudge players out. A 20-minute idle timer is a blunt version of that, but a defensible one: if someone has walked away from the screen, the session should close.

The problem is what the timer does to a player who hasn't walked away at all. Jackpot screens — the ones showing a rising prize pool, a countdown, or a "you're in the draw" confirmation — often sit outside the main game loop. They don't register taps the same way a spinning reel does. A player watching a pool tick upward can be logged out while actively staring at the screen.

Why the jackpot screen is the worst place to lose a session

Progressive and networked jackpots depend on continuity. Your entry, your stake, your position in a tournament lobby — some of that lives in the session, not the account. When the session drops, three things can happen:

• The screen resets to the lobby. Your place in a queue or a draw is gone, and the operator's logs may or may not show you were eligible.
• The jackpot state refreshes. If the pool has grown since you left, the new figure is what you see — which is fine — but any "locked in" display is now wrong.
• Re-entry costs time. Logging back in, navigating to the same game, and confirming you're still in it takes 40 to 90 seconds on average. For a timed draw, that's often too long.

None of this is fraud. It's just friction, and friction lands hardest on the players who care most about the outcome.

The 63% figure deserves a closer look

The audit's headline number is that 63% of timed-out jackpot sessions ended without the player returning to the same screen. That doesn't mean 63% lost money or lost a prize. Many had no live entry at the time. But the subset that did — players with an active stake in a draw or a progressive pool — is where the real cost sits, and the audit put that at roughly one in nine timed-out sessions.

That's still a lot. Across 4.2 million sessions, one in nine is hundreds of thousands of players who were doing exactly what the product asked of them and got logged out for it.

What operators could do tomorrow

Extend the idle timer on draw and jackpot screens specifically. Treat a visible jackpot page with an active entry as "activity" even without a tap. Push a two-minute warning before logout, not a silent redirect. None of these weaken the responsible gambling case — a player watching a pool isn't the same as a player chasing losses at 3 a.m.

The question nobody's answering

If the timeout is there to protect players, why does it fire hardest on the screen where the stakes are clearest? The honest answer is that most timeout logic was built for slot reels and sportsbooks, then bolted onto jackpot products without rethinking the edge cases. The 63% is a symptom of that shortcut.

The open question is whether regulators will treat a dropped jackpot session as a player-protection failure or just an engineering quirk. If it's the former, expect idle-timer rules to get more granular — and expect operators to start arguing about what counts as "activity" on a screen where the only thing moving is a number going up.