Home › Security and Responsible Gaming
Keeping your account secure
Account security in gambling is not mainly about sophisticated attacks. It is about a small number of simple habits that stop the ordinary cases: a reused password, a shared session, a login page that was not what it appeared to be. Most compromised accounts are lost through one of those doors.
An account holding a balance deserves at least the care given to an email address, and a little more, because the money inside can move instantly.

The password is still the first line
A long, unique password removes the most common route into an account. Reuse is the specific danger: when a password is exposed in one service's breach, automated tools try it against hundreds of others within hours, including gambling platforms.
Length matters more than complexity. A passphrase of several unrelated words is both stronger and easier to remember than a short string of substituted characters, and it survives the common advice to change passwords on a schedule, which tends to produce weaker variants.
Two-step verification
Where it is offered, two-step verification is the single most effective protection available. It requires a second piece of evidence at login, usually a code delivered to a device you hold, so a stolen password alone is not enough.
The main pitfall is the recovery channel. If the second factor is delivered to the same address that can reset the password, an attacker with mailbox access defeats both steps at once. Keeping the two channels separate is the whole point.
Session hygiene
A session that stays open on a shared computer is a signed blank cheque. Log out deliberately at the end of a session, especially on devices you do not exclusively own, and review the list of active devices in the profile settings periodically.
Removing an unfamiliar device and changing the password immediately is the correct response to a session you do not recognise. Doing it in that order is important: the password change ends the session; removing the device alone may not.
The habits and what they prevent
| Habit | What it prevents | Effort |
|---|---|---|
| Unique long password | Credential stuffing from other breaches | One-time |
| Two-step verification | Login with a stolen password | Seconds per login |
| Deliberate logout | Access from a shared device | One click |
| Reviewing active devices | Long-running unnoticed access | Occasional check |
| Separate email for finance | Cross-service breaches | One-time |
None of these requires technical skill. Their value comes from being applied consistently rather than impressively.
What support will never ask for
- Your password or a one-time code.
- Your card PIN or the full card number.
- Remote access to your computer or phone.
- A payment to release a withdrawal.
- Documents sent through a messenger or a link in a message.
Any request on this list is fraudulent regardless of who appears to make it, and legitimate support will confirm a genuine need through the account rather than through an unsolicited channel.
Payment-method safety
Deposits and withdrawals should use instruments in your own name, and no one should ever have access to your payment credentials on your behalf. Sharing a card or a wallet with another person creates both a security exposure and a verification problem that may prevent withdrawal entirely.
It also helps to keep the payment notification channel active. A message about a transaction you did not make is the earliest warning available, and it is only useful if the alerts are switched on.
Recognising social engineering
Most account theft begins with a conversation rather than with software. A message claiming to be from support, an operator encouraging a bet, or a “friend” asking for a code are the standard openings, and each depends on the target responding.
The defence is procedural rather than clever: never share a code, never install software at someone else’s request, and verify any claim by opening the site yourself instead of following the link provided.
Urgency is the reliable signal. A legitimate security notice does not need you to act within sixty seconds, and any message that insists on speed is designed to prevent exactly the check that would expose it.
In short
Account security is a handful of unglamorous habits: one long unique password, a second factor kept separate, a deliberate logout, occasional review of devices, and a firm refusal to share credentials with anyone. Every breach story usually starts with one of these steps being skipped.
Read next
Recognising clone and scam sites
Look-alike domains, fake login pages and messages that promise guaranteed wins — and how to check before you type.
Deposit limits and pauses
How to set a limit before a session, why time limits matter as much as money limits, and how to make them stick.
Self-exclusion explained
What self-exclusion does, how long it normally lasts, and why it is not a punishment but a tool.