Reference

Your Privacy Policy For Every Account Step

dewa200 asli Privacy Policy explains how we handle the details you provide while opening an account, checking wallet status and reaching the lobby.

Account dataWallet statusDevice choicesPolicy access
dewa200 asli Your Privacy Policy For Every Account Step
PRIVACY HELP

Where To Ask About Your Policy Rights

A direct privacy question should not be mixed with a general lobby request, so we keep the account and payment trail visible when you contact us.

Account request Ask us to access, correct or clarify personal data through the account support path. State the exact Privacy Policy request and include your account phone number so we can identify the right record without asking for a wallet password.
Payment trail If a DANA, OVO, GoPay or QRIS reference appears in your account history, share the reference and date when asking about its handling. We use those details to trace the record while keeping the request focused on Privacy Policy.
Access concern When a sign-in or phone verification issue affects a privacy request, tell us which device path you used and what stopped. We can separate account access checks from the policy question and avoid collecting unrelated details.
DATA HANDLING

Inside dewa200 asli Privacy Controls

The Privacy Policy is designed around the moments that create a real account record: phone verification, wallet selection, device sign-in and a request for help.

Data purpose

We use your account details to create and maintain access, connect phone verification to the correct account and answer policy requests. Payment references from DANA, OVO, GoPay or QRIS help us trace status without exposing your wallet password.

Cookie choices

Cookies and similar device signals help keep a signed-in session connected to the right account and remember policy access preferences. We do not treat a cookie as proof of identity; phone verification remains the account step used for sensitive access checks.

Account protection

Sign-in records, phone verification and device signals help us identify unusual access around your account. If a device changes or a session stalls, we may ask for account details already connected to you rather than requesting DANA, OVO or GoPay credentials.

Record retention

We keep account, support and payment references only while they serve access, dispute, safety or legal needs. A request to remove or correct data is assessed against those needs, and we reduce the record when a full copy is no longer required.

Your request

You may ask what personal data we hold, why it is used, whether a detail is wrong and how long it is kept. Include your account phone number and a clear request so we can verify identity before discussing private records.

Policy contact

For a Privacy Policy question, use the account support path and describe the data issue in plain English. We keep the request tied to your account, separate it from a game or wallet query and explain any identity check needed.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the records you create while using an Indonesian account, including phone verification, wallet references, device sessions and support requests. We keep the wording practical so you know what to ask before opening an account or contacting us. Access and eligibility depend on local law, and our policy route remains available for account-specific questions where local law permits.

It covers account details, phone verification, device session signals, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account requests. It also explains purposes, retention, access checks and how you can ask for correction or clarification.

Phone verification links account access to the contact detail you provide and helps us distinguish your request from an unauthorised sign-in. We use the result for account protection and privacy checks, not as permission to view your wallet password or unrelated device content.

No. Our Privacy Policy concerns payment references and status details needed to match a request with your account. We do not need your DANA, OVO, GoPay or QRIS password to trace a receipt, check a status or answer a policy question.

Use the account support path and state that you want a personal data access request under the Privacy Policy. Include your account phone number and the records you want assessed. We may confirm identity before discussing private account, device or payment details.

Yes. Tell us which account detail is inaccurate, what the correct detail should be and why the change is needed. We may check phone verification or another account step before changing it, and we will assess the request where local law permits.

We keep payment references while they support account access, receipt tracing, dispute handling, safety checks or legal needs. When a record no longer serves one of those purposes, we remove it or reduce its connection to your account where local law permits.

Yes. The policy applies whether you open the account on a phone or desktop. Device signals may connect a session to account protection, while cookies may remember access preferences. We do not treat device data alone as proof that a privacy request is yours.