Reference

Privacy Policy for DANA and QRIS Access

dwg228 Privacy Policy shows what we collect, why we use it and how you can ask about your account records.

Clear data purposesWallet record contextPhone verificationIndonesia access
dwg228 Privacy Policy for DANA and QRIS Access
CONTACT ROUTES

Ask About Privacy Near Your Wallet

A privacy question should not get lost beside a cashier issue, so we keep a direct route for account data requests.

Account data request Use the account support route to ask what personal records we hold.
Wallet record question For a cashier-related privacy question, identify DANA, OVO, GoPay, QRIS, bank transfer or virtual…
Access concern If a mobile browser or desktop session shows an unexpected account prompt, contact us…
SECURITY PRACTICE

Privacy Controls Across Mobile and Live Tables

We handle Privacy Policy requests as account matters, not as general lobby questions.

Data use

We use submitted account details to create and protect your profile, support phone verification and respond to Privacy Policy requests.

Cookies

Cookies and similar session tools help keep your signed-in path connected while you move from the lobby to account settings.

Account security

We compare login details, device signals and phone verification before handling sensitive account changes.

Record retention

We retain account, payment and security records for as long as needed for the stated service purpose, dispute handling and…

Changing your data

You can ask us to correct an inaccurate phone number, contact detail or account record through the support route.

Who receives requests

Privacy requests go to the account support team rather than a game or cashier queue.

Privacy Policy Questions for dwg228 Accounts

These Privacy Policy answers focus on the questions we expect you to have before opening an account or checking a wallet record. They cover the account step, mobile sessions, cookies, payment references and requests to access or change data. If your situation is not covered, use the account support path with the relevant device or transaction detail.

It covers account details, phone verification, device and session events, cookies, wallet references and support requests. It also explains why we use those records, how long operational records may remain and how you can ask for access or correction where applicable.

We use a DANA or QRIS reference to match a cashier action with its status and investigate a receipt question. The same principle applies to OVO, GoPay, bank transfer and virtual account records; we do not need unrelated wallet details.

Yes, you can send an account data request through the support route. State the phone number used for verification and the categories you want, such as login events or wallet records. We may verify ownership before releasing account-linked material.

Cookies help maintain your mobile browser session and remember the path between account settings and the lobby. If you clear cookies, the next session may ask for phone verification again. Our use of these tools remains subject to applicable local requirements.

You may ask us to correct an inaccurate account detail or record through support. Tell us which field is wrong and provide the relevant DANA, OVO, GoPay, QRIS or bank reference. We verify the request before making a change.

We keep payment and account records for the period needed to provide the service, resolve disputes, maintain security and meet legal duties. A virtual account or bank transfer reference can remain after the session closes because it may support a later account check.

Yes. Requests to access, correct or remove personal data depend on local law and the nature of the record. Where local law permits, we explain the available action after verifying your account and identifying the specific data involved.