Disconnections and game errors: your rights and the procedure

Every outcome is determined and recorded on the operator's server, not in your browser or app. Your screen is a display of that record. What follows from this: • If your connection drops mid-spin, the result still happened. The outcome was determined when you pressed the button. Reconnect and the balance reflects it • An interrupted slot round is normally completed automatically or restored when you return, including any unfinished bonus round. Most games resume exactly where they stopped • Your device crashing does not void a bet. The wager was accepted server-side • The game history is the authoritative record, not your memory of what the screen showed The first thing to do after any disconnection: open the game history or account statement and check what the server recorded. Every licensed operator provides this, usually under account history or game history, and it shows each round with its stake, its outcome and a round identifier. If the history and your balance agree, there is no incident, however alarming the disconnection felt. If they do not, you have a specific, documented discrepancy — which is exactly what a claim needs.

Live dealer games are different in one crucial respect: the table does not wait. What happens if you disconnect at a live table: • The round continues. A real dealer is dealing to many players, and your absence changes nothing • Your placed bets stand and are settled according to the result • Decisions you do not make are taken by default rules. In live blackjack, failing to act within the time limit typically results in an automatic stand on your current hand • You cannot claim the round back on the basis that you would have played differently Why this is not unreasonable: the game is physical, shared and real time. It cannot be rewound for one participant without affecting everyone. The practical protections: • Do not play live tables on an unstable connection. RNG games tolerate a drop; live tables do not • Know the default action for the game you are playing before you sit down. It is in the rules • Avoid live games on mobile data in areas with poor coverage, and be aware that a phone call can interrupt a session • Do not open several live tables at once if your connection is marginal

Real malfunctions do occur — a round that does not settle, a balance that does not update, a bonus round lost without being played out. The procedure, in order: 1. Screenshot immediately. The screen as it appears, the balance, and any error message. Timestamps matter. 2. Note the round identifier. Every game round has an ID in the game history. This is the single most useful piece of information for support, because it lets them retrieve the exact record. 3. Check the game history before contacting anyone. Establish precisely what the server recorded and how it differs from what you expected. A claim that states the discrepancy is treated very differently from one that states a feeling. 4. Contact support in writing, with a ticket number. Live chat is fine to open it, but ask for a ticket reference and follow up by email so there is a written trail. 5. State the facts and the specific ask. Round ID, time, stake, what happened, what you believe should have happened. Avoid accusations — the fastest resolutions come from clear, calm reports. 6. Escalate if needed. If support cannot resolve it, ask for escalation, then complain to the licence regulator with your full documentation. Regulators require you to exhaust the operator's process first. One term to know: essentially every operator's rules state that malfunction voids all pays and plays. That clause is standard and legitimate — it exists so that a genuine software fault does not create a windfall — but it also means a claim needs to establish that the round was validly completed, not merely that the screen showed a win.

1. Play on a stable connection. Wired or strong wifi for live tables. If your connection is unreliable, RNG games are the safer choice because they resume. 2. Use the operator's app or a current browser. Most reported faults are client-side — an outdated browser, a blocking extension, a device short of memory. Clearing the cache resolves a surprising share of them. 3. Check the game history after anything unusual. Make it a reflex. It takes ten seconds and it either resolves your concern or gives you a documented case. 4. Do not replay a round you are unsure about. If you disconnected mid-round, reconnect and check the history before staking again. Playing on can make an incident far harder to reconstruct. 5. Keep records of anything significant. Screenshots of large wins, round identifiers, and support conversations. Storage costs nothing and a documented case is the difference between a resolution and a disagreement. A final note on expectations. The overwhelming majority of reported malfunctions turn out to be connection problems where the server record is correct and complete. That is a good outcome — it means the money was never at risk. Checking the history first saves you the anxiety and saves support the ticket, and on the rare occasion something genuinely went wrong, you will have exactly the evidence needed to prove it.