Reference

dwg11 Terms & Conditions In Plain English

dwg11 Terms & Conditions explain how your account, wallet status, lobby access and policy requests work in Indonesia.

Account accessWallet checksPolicy requestsLocal-law wording
dwg11 dwg11 Terms & Conditions In Plain English
CONTACT THE POLICY TEAM

Help With A Terms Question

A clear contact route helps when a clause affects your account, wallet status or access request. We can direct you to the relevant Terms & Conditions wording and explain which account step is still pending. Include your dwg11 account identifier and the payment reference when your question concerns DANA, OVO, GoPay, QRIS, a bank transfer or a virtual account. Do not send a password or one-time security code in a support request.

Team online

Account policy help

Use the account support route when you need clarification about phone verification, duplicate account concerns, login access or a clause affecting your account. We check the account details you provide and point you to the relevant Terms & Conditions section without asking for your password.

Wallet status query

For a payment-related policy question, send the payment rail, reference and visible status from your account. Our team can help trace whether the matter concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account instructions and explain the applicable Terms & Conditions.

Access clarification

If a page or game does not open, contact us with your device path, such as mobile browser or desktop browser, and the wording shown on screen. We can clarify whether the restriction is account-related or depends on local law before you continue.

ACCOUNT RECORDS

How We Handle Policy Details

Our Terms & Conditions work alongside practical account controls rather than replacing them. We use the details needed to maintain your account record, assess access requests and match payment references to the…

Account data

We handle registration details, phone verification data and account activity so we can apply these Terms & Conditions to the correct account. Keep your phone number current, because an outdated contact detail can delay an access question or a request to change your record.

Cookie function

Cookies may keep a browser session connected and help us identify security events during account access. Your mobile browser and desktop browser can display the same policy pages, but clearing cookies may require you to complete the login path again.

Login security

Your password and verification code belong only to you. We do not need either item in a policy message. If you suspect that someone else used your account, contact support promptly and include the time, device path and visible account activity.

Payment records

A payment reference helps us connect a policy question with the correct wallet event. For DANA, OVO, GoPay and QRIS, retain the receipt shown by your wallet; for bank transfer or virtual account activity, retain the bank reference.

Retention questions

If you want to ask how long a particular account record is kept, identify the record and the reason for your request. We will route the question through support and explain what can be changed under the applicable Terms & Conditions.

Requesting changes

To request a correction, access copy or account-detail change, contact us with your account identifier and a precise description of the requested action. We may need to confirm account ownership before acting, so do not create a second account to bypass that step.

Terms & Conditions Questions Answered

These Terms & Conditions answers address the account questions we expect you to ask before opening access. They cover eligibility, policy changes, payment references, browser behaviour, account records and contact steps. If your situation is different, use the support path with the exact account or payment detail involved. Access depends on local law, including the law that applies to your location.

You can read the Terms & Conditions on this policy page before opening an account or continuing through the login path. We publish the clauses covering account access, phone verification, wallet activity, security, policy changes and contact requests in one place for your reference.

Yes. The same Terms & Conditions apply when you use a mobile browser or a desktop browser. Your device may display the account path differently, but phone verification, login protection, wallet references and local-law wording remain part of the same policy.

Access depends on local law and the eligibility requirements shown for your location. If an access message appears, do not try to bypass it with another account or device. Contact support with the wording displayed so we can explain the relevant policy route.

DANA and QRIS are named payment rails in the account payment flow. Keep the receipt and reference visible in your wallet or bank record. If a status does not match your account, contact us with that reference so we can apply the relevant Terms & Conditions.

You can contact support to request a correction or another account-record change. Provide your account identifier and describe the field or record clearly. We may confirm ownership before acting, and the request remains subject to the access and record clauses in these Terms & Conditions.

Stop using the account and contact us through the policy support path if you need clarification about an updated clause. We can identify the change and explain its effect. If you do not accept the wording, do not continue account activity after the effective date.

Send support your account identifier, device path, visible message and relevant payment reference. For OVO, GoPay, bank transfer or virtual account questions, include the receipt status without sharing passwords or security codes. We will direct the matter to the applicable policy and account route.