Account desk

Signing in

Most failed sign-ins come down to a handful of causes, and you can clear nearly all of them yourself in a minute or two.

The five causes, in order of likelihood

1. The wrong email addressPeople register with one address and try to sign in with another, especially where a work address and a personal one both exist. A password reset settles it quickly, because a reset link only reaches a registered address.
2. An old password saved in the browserA saved credential that was changed elsewhere fails quietly and keeps failing. Type the password by hand once to rule this out.
3. The account is not verified yetSome accounts sign in but cannot move money until documents are approved. That is a verification state, and the screen does not always separate it from a login problem.
4. A session that expiredSessions time out fast here, which is a security feature. A page that looks logged in but rejects every action usually needs a reload and a fresh sign-in.
5. A regional blockIf the account was opened from a territory the operator restricts, access can be refused whatever the credentials say. New Brunswick and Ontario are on that list, so check the Canada page.

Resetting a password

The reset flow is standard. Request a link, open it from the same device where you can, set a new password, sign in. Two details cause most of the frustration. Reset links expire, often inside an hour, so an email opened the next morning will fail. And asking for several links in a row invalidates the earlier ones, which means the newest email in the inbox is the one that works.

If nothing arrives after you have checked spam and confirmed the address, the likeliest explanation is that no account exists at that address. Registering again is faster than a support ticket, though duplicate accounts breach the terms, so take that step only when you are confident the first registration never completed.

Staying signed in

Sessions drop for good reasons. Shared devices, unattended browsers and stolen cookies are real risks on any site holding a balance. Expect to sign in again after switching networks, after a long idle stretch, and always after clearing cookies. A private browsing window discards the session when it closes, which is the design working as intended.

On a phone, the common complaint is a session that dies when you switch apps. That is the browser reclaiming memory, and it is not the casino logging you out. The mobile page covers how to keep phone play stable.

Signing in on a shared or public device

A private or incognito window is the safer default on any device you do not fully control. It throws away cookies and saved credentials the moment it closes, so nothing lingers for the next person at that keyboard. You will sign in fresh every time, and on a machine you cannot lock down yourself that small chore is the whole point.

On your own device the calculation flips. A password manager and a remembered session save time without adding real risk, because the device itself is the security boundary. The account is the same either way, holding money and identity papers, and it is the surrounding machine that changes the answer.

Keeping the account secure

• Unique password

  Reused passwords are the main route into gambling accounts. A manager solves this for good.

• Two-step verification

  Switch it on where it is offered. It stops a leaked password from being enough on its own.

• Your own email

  Never a shared or work mailbox, since password resets and withdrawal confirmations both land there.

• Never share access

  Account sharing breaches the terms at essentially every casino and can void a balance.

Account lock versus self-exclusion

These look identical from the sign-in screen and are entirely different underneath. A temporary lock, whether it follows too many failed attempts or a fraud flag, is automatic and short, and it clears itself or resolves with a password reset. Self-exclusion is a deliberate choice a player makes to block their own access for a set period, and support cannot lift it early however the request is phrased. During that window the login form may accept correct credentials and still refuse entry, which is the feature doing exactly what it was set up to do.

If you cannot tell which one you are looking at, the practical test is simple. A temporary lock generally tells you roughly how long to wait or offers a reset. A self-exclusion screen typically does not, because the entire point is that a bad moment cannot talk its way back in. See responsible gambling for how the account-level tools work.

Neither a support agent nor any account setting can shorten a self-exclusion period once it is set. Repeated login attempts are a slow way to test whether it has worn off, and a calendar reminder answers the same question more reliably.

Login questions

The welcome package