What the topic covers
Live dealer play typically combines a streamed table, a dealer’s actions and software that accepts and records a player’s decisions. The practical review questions are therefore more specific than whether a game appears on a page: What rules govern each round? What happens if the stream or connection fails? How is a player’s interaction recorded? What information supports the final settlement?
“Non-Gamstop” is a description used for services outside Gamstop’s UK self-exclusion scheme; it does not, by itself, establish a service’s licensing, oversight, quality or legal status. This checklist does not suggest using another service to get around self-exclusion. If self-exclusion applies, treat that as a protective boundary and seek appropriate support rather than looking for access elsewhere.
A review should also separate a live broadcast issue from a game or account issue. A frozen picture may not mean the underlying round stopped, and a displayed result may not explain how a disputed transaction was handled. These are questions to verify from published rules and available records, not assumptions about how any particular operator behaves.
What to verify independently
Start with the rules for the specific table and the terms that apply to interruptions. Check whether the rules explain when a round is considered started, what happens to accepted decisions if a connection drops, and how an unfinished or interrupted round is treated. Look for distinctions between a player-side disconnection, a stream problem and a broader technical failure. If the documents do not make those distinctions clear, record that uncertainty rather than filling it with an assumption.
Next, examine the information available before a round and during play. The review can note whether rules are accessible from the table, whether key decisions and limits are explained, and whether the interface indicates that a choice has been received. Do not infer that an action was registered just because it appeared to be clicked. Where a record is available, compare the displayed action with the round history or account record.
For dealer interaction, distinguish ordinary table conversation from communication that can affect a decision or resolve a technical concern. Check what the interface actually permits, whether messages are visible to the player, and whether a dealer’s statement is consistent with the written rules and recorded outcome. Avoid treating friendliness, speed or confidence as evidence that a settlement is correct. Do not assume that a dealer can change a result or resolve an account dispute.
For settlement evidence, look for a round identifier, recorded decisions, the result shown, and the corresponding account entry. The precise records available can vary. Preserve relevant rule text and records in their original context where possible, including any visible time information. Redact personal or payment details before sharing material publicly. The table below separates useful checks from what they can establish.
| Area | Evidence to inspect | What it can show |
|---|---|---|
| Table rules | Rules for the selected table and interruption wording | What the published procedure says; not whether it was followed |
| Connection event | Visible error, round record and any account entry | Which details are documented; not the cause if it is unstated |
| Dealer interaction | Displayed conversation and related written rule | What was communicated; not proof of a binding decision |
| Settlement | Round history, displayed result and transaction record | Whether records appear consistent; not independent verification |
How to read the evidence
Keep observations separate from interpretation. A useful note says what screen or document was reviewed, what it displayed, and what remains unknown. For example, “the account record shows an entry associated with this round” is narrower and more defensible than claiming that the entire settlement process was fair. If the records conflict, describe the conflict and avoid deciding which is authoritative unless the relevant rules explain that point.
Check that evidence relates to the same table, round and account event. A general help page may describe a standard process but may not address the particular interruption under review. A screenshot can show what was visible at a moment, but it may omit earlier steps, later changes or underlying system records. Likewise, a customer account can provide context but is not independently verified merely because it is detailed. This article has no such accounts to assess.
When summarising a check, separate the evidence into three groups:
- Published rules, with the version or date if shown.
- Observed displays and records from the same round.
- Unresolved questions and gaps in the evidence.
Risks and limits
Publicly available rules may not expose the full technical record behind a stream, decision or settlement. A player may also lack access to internal logs, so an apparent mismatch can remain unresolved. Do not claim a system error, misconduct or correct payment without evidence sufficient to support that conclusion. An absence of public complaints is not proof that no problems occurred, and an individual account is not proof of a general pattern.
Finally, logging out is not the same as deleting or closing an account, and neither action should be assumed to cancel an existing restriction or record. The checklist does not explain how to bypass self-exclusion and is not a substitute for legal, financial or support advice. Its purpose is limited: identify what can be checked, distinguish documented facts from claims, and state clearly when available evidence cannot answer the question.
