Reference

Terms & Conditions for v2026 Accounts

Our Terms & Conditions explain how your v2026 account, wallet activity and lobby access work before you open an account.

Account rulesWallet checksAccess conditionsData requests
v2026 Terms & Conditions for v2026 Accounts
HELP WITH TERMS

Get Clear Answers About Your Account

A clear contact path helps when a clause affects your account, payment record or access request. We ask you to contact our support team from the account route connected with your question, so we can match the request to the correct phone verification and transaction history. Include the relevant date, payment rail and account email or phone detail, while leaving out passwords and one-time codes. We can then explain which Terms & Conditions section applies and what step is needed next.

Team online

Account questions

If a Terms & Conditions rule affects sign-in, phone verification or account details, contact us through the account support path. Tell us which step stopped you, and we can point to the relevant clause without asking you to share a password or one-time code.

Wallet status

For DANA, OVO, GoPay, QRIS or bank transfer questions, include the payment rail and transaction reference in your support request. We use those details to separate a pending wallet record from a rule-based account check before explaining the applicable Terms & Conditions.

Policy changes

When you want to question a policy change or ask how a new clause affects your account, send the page section and date you saw. We can clarify the effective wording and record a request for a correction or account-data change where the terms allow it.

CONTROL YOUR RECORD

Six Practical Protections In Our Terms

The policy is designed to show what happens to account records, payment references and access requests rather than leave those decisions unclear.

Account data

We use the details attached to your account to manage sign-in, phone verification, payment matching and policy requests. If a detail is wrong, contact us from the account route with the correction you need; we may ask for a matching verification step before changing it.

Cookies

Cookies can support the session needed to move from login to the lobby and remember basic access settings. Our Terms & Conditions treatment of cookies does not make them a substitute for your password. You can ask support which cookie-related setting applies to your account session.

Account security

Keep your password and phone verification codes private, because our support team does not need those secrets to explain a clause. If access looks unusual, stop sharing account details and contact us through the account path so we can check the sign-in record.

Payment records

A DANA, OVO, GoPay, QRIS or bank transfer reference helps us match a transaction to the correct account. We retain the operational record needed to check status and withdrawals, while a payment receipt alone does not change the Terms & Conditions.

Retention requests

Our policy explains why certain account and transaction records may remain available after a request to close access. If you ask what we retain, name the account route and record type; we will explain the applicable retention reason and any local-law limitation.

Change requests

You can ask us to correct account details, explain a policy clause or clarify an access decision. Send the request through support with the relevant section, account identifier and date. We may verify ownership before discussing or changing information tied to the account.

Terms & Conditions Questions For v2026

These questions focus on the Terms & Conditions decisions you are most likely to check before opening an account or using a wallet rail. Each answer connects the policy wording with a practical account step, from phone verification to payment matching and data requests. If your situation is not covered here, contact support with the exact clause and account detail involved, without sending a password or one-time code.

You can read the current Terms & Conditions on this page before opening an account. The text covers account access, phone verification, wallet records, withdrawals, cookies, security and policy changes. Save the date you read it if you need to ask support about a particular clause.

Yes. The Terms & Conditions apply when you use DANA, OVO, GoPay, QRIS, bank transfer or another listed wallet route connected with your account. Payment matching may require a transaction reference, and a wallet status does not replace the account verification steps described in the policy.

You must provide account details that belong to you and complete phone verification before account access is enabled. If a sign-in or verification step fails, contact support through the account route. Do not send your password or one-time code in a policy request.

Access depends on local law. You are responsible for checking whether access is permitted where you are located, while we may apply account or location checks described in the Terms & Conditions. If a restriction appears, support can explain the relevant policy route and required account details.

A withdrawal request can be checked against the account details, phone verification and original payment trail. DANA, OVO, GoPay, QRIS or bank transfer references may help match the request. We may pause processing while an account or transaction check described in the terms is completed.

Yes, you can ask us to correct account details through the support path linked to your account. Include the field that needs changing and the date of your request. We may verify account ownership first, then explain any retention or local-law limit affecting the correction.

Send support the exact Terms & Conditions section, the date of the decision and the account or payment reference involved. Use the account contact route and omit passwords, codes and unrelated wallet credentials. We will explain the decision path and tell you whether another request step is available.