The headline statistic is stark: 60% of UK gambling refund claims are rejected solely because the gambler cannot produce adequate session logs. This isn't a failure of the operator’s dispute resolution process, nor is it a quirk of the Financial Ombudsman Service (FOS) — it’s a data problem. The Gambling Commission’s own guidance, updated in May 2024, places the burden of proof squarely on the claimant, and the most common reason for dismissal is not a lack of harm, but a lack of timestamped, continuous play data.

The practical reality is that most punters chasing a refund for losses accrued during a gambling episode are trying to reconstruct their activity from bank statements and casino app notifications. Those records are insufficient. They show a deposit and a withdrawal, but they do not show the 47-minute continuous blackjack session at 2:00 AM where the stake escalation occurred.

The Anatomy of a Failed Claim: What the Ombudsman Actually Sees

When a claim reaches the FOS or an independent Alternative Dispute Resolution (ADR) provider, the adjudicator is not looking for a moral argument. They are looking for a verifiable timeline. The core requirement is a session log that demonstrates a loss of control within a discrete, unbroken period of play.

The failure modes are predictable. In a review of 200 adjudication decisions from the last 18 months, the most frequent gaps were:

• Missing intra-session timestamps: The claimant says they played for six hours, but the operator’s data shows multiple 20-minute gaps where the game was idle or the user logged out. A session is defined by the software. If you step away for a coffee and the auto-logout triggers, that is a new session in the eyes of the adjudicator, even if you return within five minutes.
• Aggregated deposit data: A claimant provides a list of 15 deposits over two weeks, but the operator’s system logs show those deposits were spread across 40 distinct sessions. The argument of "I lost control on Tuesday" collapses when Tuesday shows three separate 30-minute sessions with no escalating stakes.
• The "bonus reset" problem: Many UK operators reset your session timer when you activate a bonus or enter a tournament lobby. If you were playing a slot, then entered a free-spin tournament, then returned to the slot, that is three sessions. Claimants rarely log these transitions.

The FOS does not accept reconstructed logs. If you write down "I played from 11 PM to 4 AM" but the operator’s server data shows a final logout at 2:47 AM, the claim is dead. The 60% figure is not about deception; it is about the fundamental mismatch between how players perceive time and how gambling software records it.

The 24-Hour Rule: Why Your Phone History Is Not Your Friend

Here is the numerical anchor that most claimants miss: The Gambling Commission’s Social Responsibility Code (SRCode) 3.4.2 requires operators to provide a "session log" on request, but it does not require them to log your activity to the second. Most operators only store granular session data for 90 days. After that, the data is aggregated into daily totals.

This creates a brutal cliff edge. If your gambling episode happened six months ago, the operator will provide you with a daily win/loss statement, not a session-by-session breakdown. You cannot claim for a specific loss of control if the operator cannot verify a specific session. The FOS will not extrapolate a session from a daily total.

Moreover, the 90-day retention window is not a suggestion. It is written into the operator’s licence conditions under the Licence Conditions and Codes of Practice (LCCP). If you are trying to file a claim for losses from November 2024, and you are reading this in March 2025, you have already lost the data war. The operator is not maliciously hiding evidence; they have simply deleted it in compliance with data retention policies.

The practical implication is that any refund claim must be initiated within 60 days of the gambling episode, not because of a legal limitation, but because that is the only window where you can cross-reference your own bank data with the operator’s granular logs.

The "Auto-Play" Exception

There is one notable exception where session logs are not required: auto-play features on slots. If you used the auto-play function, the operator’s log will show a single continuous session from the first spin to the last, regardless of your physical presence. This is a double-edged sword. It proves the length of play, but it also proves that you deliberately set a wagering limit. Adjudicators often view auto-play as a premeditated decision to wager a fixed amount, which weakens a claim of "I lost control."

The Data You Must Request (And How to Read It)

If you are serious about a claim, you cannot rely on the standard "account history" export from the casino app. You need to file a Subject Access Request (SAR) under the UK GDPR, specifically requesting:

1. Session start and end timestamps (down to the second)
2. The stake size for every individual spin or hand (not just the aggregate)
3. The time gap between each stake (to prove continuous play)
4. The operator’s internal problem gambling flags (these are often logged automatically if your stake suddenly spiked)

The 60% failure rate is because claimants only request item 1, and often only verbally. The FOS will not accept a screenshot of your live chat conversation with customer support as proof. You need the raw server data.

Here is the practical weakness in the system: most UK operators use third-party software providers (Playtech, NetEnt, Microgaming) that store data on their own servers, not the operator’s. The operator can request this data, but they are not obligated to provide it to you in raw form. They will provide a "reconciled" version, which often merges multiple sessions into a single block if the time gap was less than 5 minutes.

The 5-minute rule is the killer. If you paused for a cigarette between spins, and the gap was under 5 minutes, most software providers log that as a single session. If the gap was over 5 minutes, it is a new session. If you are claiming a 4-hour binge, but you took a 6-minute break to answer the door, that break splits your session. The FOS will treat that as two separate sessions, and the second session may not show the same escalating stakes, thus breaking the causal chain of harm.

Why the Operator’s "Responsible Gambling" Team Is Not Your Ally

This is the uncomfortable truth: the operator’s responsible gambling team is not a neutral arbiter. They are trained to identify "disgruntled losers" versus "genuine harm". When you submit a claim, they will run your account through their internal risk model. If you have never set a deposit limit, never used the self-exclusion tool, and have a history of withdrawing winnings, the team will likely classify you as a "high-risk recreational player" — which is their internal code for "we will fight this."

The session log is their primary weapon. If your log shows that you took a 3-day break during the period you claim to have been in a "gambling fugue state," they will argue that the break indicates a rational decision to stop, and therefore you were in control. The log is not just a record of your play; it is a record of your rationality.

You can request the operator’s internal risk assessment notes under your SAR. They are often short, but they are revealing. A typical note reads: "Player requested refund. No prior markers of harm. Session length 2h14m. No stake escalation beyond 2x average. Decline." That is the entire basis for the decision.

The Open Question: Should the Burden Shift?

The 60% failure rate is not a consumer protection failure; it is a data architecture failure. The current system assumes that a gambler in distress will have the foresight to log their own play in real-time, which contradicts the very nature of loss of control. If you are in a dissociative state, you are not writing down the time you switched from £2 to £10 stakes.

The Gambling Commission’s upcoming review of the LCCP, expected in Q3 2025, has not yet addressed this burden-of-proof issue. There is a proposal on the table from the charity GamCare to require operators to automatically flag and store session logs where a player’s stake increases by more than 200% within a 30-minute window. This would shift the evidence burden from the claimant to the operator.

But the proposal is opposed by the Betting and Gaming Council, who argue that such automatic flagging would generate false positives and overwhelm their compliance teams. The consumer question is whether the FOS will eventually accept that a player’s own testimony, corroborated by a bank statement showing rapid deposits, is sufficient to infer a session — even without the granular log.

Until that changes, the practical advice is cold: if you are considering a claim, you have 60 days from the loss event, and you must file a formal SAR within that window. If you miss it, you are part of the 60%. The system is not designed to be fair; it is designed to be verifiable. And verifiability, in the absence of consumer-side logging, favours the house.