Reference

Read 567live Terms & Conditions

567live Terms & Conditions set out how your account, wallet instructions and lobby access work before you open an account.

Account accessWallet recordsPolicy requestsLocal-law wording
567live Read 567live Terms & Conditions
WHEN RULES NEED CLARITY

Check Terms Support Before Sending Funds

A clear support route matters when a Terms & Conditions question affects your account or wallet status.

Account policy request Use the account support path when you need a clause explained or want to ask how a condition applies to your login. Include your account identifier and the section title so we can route the request accurately.
Wallet record question For DANA, OVO, GoPay or QRIS questions, send the payment reference shown in your account rather than sharing a wallet password. We can compare the record with the applicable Terms & Conditions.
Access clarification If a game or account action is unavailable, contact us through the listed support route and name the action. We will explain whether the condition relates to verification, device access or local law.
HOW WE HANDLE POLICY

Protect Your Account Under These Terms

The Terms & Conditions work alongside practical account controls rather than replacing them. We use the details attached to your account to process access questions, compare payment references and respond to policy…

Account details

Enter accurate details when opening an account and update them through the available account path if something changes. We may ask for clarification before applying a request that affects access or payment records.

Phone verification

Phone verification is an account step before access. Keep the verified number available and do not give its code to another person. A mismatch may delay an account request while we check the details.

Payment records

We use payment references to match activity involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account. Do not send wallet passwords; provide only the reference needed for the policy question.

Cookies and devices

Cookies and device data can help keep an account session working between login and the lobby. Clear them only when needed, because a new device or cleared session may require login and phone verification again.

Record retention

We retain account and policy records for the period needed to manage the account, answer requests and meet applicable requirements. A request to change or clarify a record should identify the relevant account detail.

Policy changes

When we revise these Terms & Conditions, we publish the new wording through the policy access point connected to the service. Check the date and read the changed section before continuing with account activity.

Find Answers About 567live Terms

These Terms & Conditions answers focus on the searches we hear most often before account access. We cover account creation, payments, device sessions, data requests and local eligibility so you can decide what to do before using the lobby. If your situation is different, send the policy section and account reference through the listed support path.

They explain account creation, phone verification, login security, wallet records, policy changes, data handling and access conditions. They also describe how we handle questions about DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Account and game access depends on local law. Before opening an account, check whether the service is available for your location and circumstances. If you are unsure, contact us through the listed policy support path before sending payment.

Phone verification helps connect an account request with the correct account holder before access. Keep your verified number available and never share its code. If the number is unavailable, ask support how the account condition applies.

For a wallet or transfer question, we may need the payment reference linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet password, login password or private verification code.

Yes, send a clear request through the account support path and identify the data you believe is inaccurate. We may ask for account verification before changing a record, and the request remains subject to applicable Terms & Conditions.

Cookies can keep your session and device settings working between login and the lobby. Clearing them, changing browsers or moving to another device may sign you out and require phone verification before access returns.

We publish revised wording through the policy access point connected to the service and identify the changed text or date where applicable. Read the new section before continuing, especially when it concerns account access or payment records.