The record
A question about a game — the wrong paytable, a missing win, a title that behaved oddly — can only be answered about a specific build. Everything needed to identify it is available before you stake, and almost nothing of it survives if nobody notes it.
What is kept, and by whom
| Part of the record | Held by | What it is good for |
|---|---|---|
| Bets, returns, deposits and withdrawals | The operator | Your balance and the money trail, statement by statement. |
| The session: time, device, game opened | The operator | Placing a specific round in a specific session. |
| The build\u2019s specification and its certification | The supplier and the laboratory | What the game was supposed to do, for that build and market. |
| The build identity as shown in play | The game, to anyone who looks | Tying the three rows above to the artefact you actually played. |
The first two rows are the operator\u2019s responsibility and it will produce them on request. The third row belongs to companies you have no account with. The fourth row is the bridge between them, and it is the only one a player can lose by doing nothing.
What to note, in thirty seconds
- The exact title as displayed
Including any suffix or version word, copied rather than remembered.
- The build reference from the help panel
Where the game publishes one: a version number, a build identifier, or a catalogue string.
- The date and rough time you played
Enough to locate the session in the operator\u2019s own logs.
- The paytable as displayed
A screenshot of the panel showing what each combination pays is worth more than any description of a win you expected.
- What happened, stated plainly
The stake, the result shown, what you expected and why — one sentence, without conclusions attached.
How a paytable question is actually answered
It is answered by comparing what the build\u2019s specification says with what the session log shows happened, for the rounds in question. That comparison needs the build, which is why the identification step above is not pedantry: without it, the operator is being asked to guess which version of which title you mean, and the supplier has no reason to be involved at all.
title as displayed · build reference from the help panel · date and time
stake · the result shown · the paytable line you are relying on · transaction reference if you have one
a message that is hard to answer: “the game glitched and I lost” · no title · no time · no build
The same principle runs through the whole desk: a name is a brand, a build is an artefact, and only the artefact can be checked. That is also why the desk stops where it does — it explains what to record and how a question is answered, and offers no view on whether any particular complaint should succeed.
Disclosed sponsored link, and the only commercial element on this page. It recommends no operator, no game and no course of action, and it is not a complaints route.
Open the partner accountWhere to go next
- The figure in the help panel — where the build reference is published.
- The shelf check — the same notes as a pre-play routine.
- Certification — the specification your session is compared against.
- Why a title vanishes — why the record has to be made early.