Session replay logs 40 events — the audit trail keeps 6

A single blackjack session on a mid-tier Australian-facing casino generated 40 distinct events worth logging. The operator's own retention policy kept six of them. The other 34 — including three balance adjustments and a disputed bet void — existed for somewhere between 24 and 72 hours before being overwritten by a rotation job that nobody on the support desk could explain when asked.

That gap between what gets recorded and what survives is the single most useful thing to understand about online gambling disputes, because it determines almost everything about whether you win one.

What actually gets logged, and what gets kept

Every session throws off a stream of events: login, device fingerprint, geolocation check, deposit, bonus activation, each round's stake and outcome, each balance mutation, any manual adjustment by a risk analyst, withdrawal request, KYC document upload, and so on. A 40-event session over two hours is unremarkable — a slots player doing 400 spins will generate far more.

The retention question is separate. Operators typically tier their logs:

• Financial and AML-relevant records — deposits, withdrawals, source-of-funds checks — are held for years, because AUSTRAC obligations under the Anti-Money Laundering and Counter-Terrorism Financing Act require it. Seven years is the common figure.
• Game round data — the RNG output, bet ID, payout — usually sits in the game provider's own system, not the operator's, and is retained per the provider's contract.
• Session and behavioural telemetry — the stuff that tells you how someone was playing, not just what they wagered — is frequently on a 30 to 90 day rolling window, sometimes much shorter.
• Debug and application logs — the layer that would show you a botched bonus calculation or a failed bet acceptance — are often the shortest-lived of all. Thirty days is generous. Some setups run seven.

The 40-to-6 ratio in the title isn't a rule. It's the kind of shape you see when a player asks for "everything you have on my session" and gets back a PDF with a login timestamp, four bet records, and a withdrawal.

Why the six that survive are usually the six that don't help you

Here's the frustrating part. The records that get kept longest are the ones that protect the operator's regulatory position — proof that a deposit happened, proof that KYC was done, proof that a withdrawal was paid. Those are the least likely to be in dispute.

The records that would settle most arguments are the short-lived ones:

Bonus wagering calculations. If you believe you'd cleared $340 of a $500 wagering requirement and the system says $290, the answer lives in the contribution log for each individual bet. If that log has rotated out, you're arguing from your own screenshots against a system of record that no longer exists.

Voided or adjusted bets. A bet void mid-event, a "palpable error" correction, a cashout reversed — these generate an adjustment event with a reason code. If the reason code is gone, the operator can only tell you that the balance changed, not why.

Session state around a disconnect. Did the connection drop before the spin registered, or after? The answer is in the network and application logs, which are exactly the logs on the shortest rotation.

Under the current registered codes for online wagering — and this has been the pattern across the states that have moved on interactive gambling reform — the obligation is broadly to keep records that demonstrate compliance, not records that reconstruct a customer's experience. Those aren't the same thing, and the gap between them is where complaints go to die.

The 72-hour window and the practical deadline nobody tells you about

If you have a dispute, the clock is not the 12 months you might assume from consumer law instincts. The clock is the log rotation schedule, and you don't know what it is.

A workable rule: treat 72 hours as the hard deadline for lodging a written complaint with the operator. Not because the law says so, but because that's roughly when the useful telemetry starts disappearing at the operators with the tightest retention. Email, don't use live chat — chat transcripts are themselves logs with their own retention, and you want a timestamped copy in your own inbox.

In that email, ask for four specific things:

1. The full bet history for the session, with bet IDs.
2. Any balance adjustment events, with reason codes.
3. The bonus wagering contribution record.
4. Confirmation of the operator's log retention periods by category.

That fourth one is the tell. An operator that can answer it clearly has thought about this. An operator that can't is one where your 40 events are already down to six.

The screenshot habit

Take a screenshot of your balance and bet history at the end of every session you might conceivably argue about — a big win, a bonus you're close to clearing, anything with a disputed round. It's a weak form of evidence, but it's your evidence, and it survives rotation. The Australian Gambling Research Centre and various state-based gambling help services have noted for years that players who keep their own records fare better in disputes, which is a slightly bleak thing to have to say out loud.

What the regulator can and can't do with six events

If a complaint escalates — to the operator's ADR provider, or to the state regulator — the investigator works from the same record set you do. They can compel production of records the operator holds. They cannot compel production of records that were deleted in the ordinary course before the complaint arrived, provided the deletion followed a documented policy.

That's the whole ballgame. A retention policy that says "application logs: 14 days, rotated" is boring, lawful, and completely fatal to a complaint lodged on day 20. There is no general obligation in Australia to preserve logs indefinitely for the benefit of future disputes, and no regulator has shown much appetite for imposing one.

Where operators do get caught is inconsistency — a policy that says 14 days, and a system that actually keeps 90, or vice versa. That's a compliance failure in its own right, and it's the sort of thing that surfaces during a broader audit rather than from a single player complaint.

The question worth asking your operator

So: if you asked your casino today for the complete event log of your last session — not the bet history, the event log — how many entries would come back, and what would the retention schedule say about the rest?

Most players never ask. The ones who do tend to find out that the answer depends entirely on when they asked, which is a strange basis for a system that's supposed to be auditable. The more interesting question is whether any Australian regulator will eventually decide that reconstructability — not just compliance evidence — belongs in the record-keeping rules. Until then, the audit trail is whatever survived the night, and the burden of proving otherwise sits with the person who has the least access to it.

If a dispute is already affecting you, Gambling Help Online runs 24/7 on 1800 858 858, and it's a free call.