Reference

Privacy Policy for Your dewa6d Account

The dewa6d Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, use DANA or QRIS, and contact support.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
dewa6d Privacy Policy for Your dewa6d Account
CONTACT OUR TEAM

Privacy Policy Help Through Your Account

A direct support route helps you ask about Privacy Policy records without sending sensitive wallet credentials. Sign in first when you can, then include the phone number linked to your account and the transaction reference you want us to locate. If login access is unavailable, tell us the device path you used, such as Android mobile browser or desktop browser, and we will explain the next verification step. Requests about DANA, OVO, GoPay or QRIS are handled alongside the relevant account record.

Team online

Account message

Send a Privacy Policy question from the account support path and include your registered phone number. We use that account step to match the request before discussing stored details, so you do not need to place wallet passwords or one-time codes in the message.

Payment reference

For a DANA, OVO, GoPay or QRIS question, provide the date, amount and payment reference shown in your account. We can then trace the status record without asking you to share your wallet PIN, passcode or full private login credentials.

Access assistance

If your phone verification or browser session stalls, contact us through the available account support channel and state whether you used Android, iPhone or desktop. We will guide the identity check needed to discuss your Privacy Policy request safely.

DATA HANDLING DETAILS

What We Keep, Protect and Change

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account security

We use your registered phone and verification step to help protect account access. Do not send a password, wallet PIN or one-time code to support. If a new device behaves differently from your usual Android or desktop path, we may ask for extra confirmation.

Payment records

A payment record normally contains a method, reference, amount, status and time. For QRIS, DANA, OVO, GoPay, bank transfer or virtual account activity, these fields help us match the cashier event without storing your external wallet password.

Cookies

Cookies can keep a signed-in session available and help us understand which Privacy Policy page brought you to support. You can manage or remove browser cookies through your device settings, although some account functions may then require another sign-in.

Retention

We retain records for the time needed to operate the account, resolve a payment question, prevent misuse and meet applicable legal duties. When a record no longer serves one of those purposes, we assess it for deletion or de-identification.

Your request

You can ask what personal data we hold, request a correction, ask about processing, or seek deletion where applicable. Include your registered phone number and a clear request so we can verify ownership before making a change.

Policy contact

For a Privacy Policy request, use our support path and write the subject clearly. We may ask for account verification before sharing details. If your request concerns a QRIS or bank transfer record, add its reference to shorten the search.

Privacy Policy Answers for dewa6d

These Privacy Policy answers address the questions we expect before an Indonesian account holder opens an account or asks us to change a record. We explain the account step, wallet references, cookies, device access and contact route in plain English. Where a request depends on a legal rule, we apply the rule for your region and tell you what information or verification we need to continue.

The Privacy Policy covers data connected with your account, phone verification, sign-in device, support messages and payment references. It explains why we use those records, how we protect access, how cookies work and how you can ask about correction, deletion or other applicable rights.

No. When you use DANA or QRIS, we keep the transaction reference and status needed to match the account activity, not your external wallet password or PIN. Never send those credentials to support. A payment question can usually be checked using its reference and date.

Your registered phone supports account verification, while device and browser details help us recognise a session and investigate unusual access. An Android mobile browser and a desktop browser may create different session records. We use this information for account operation and protection, not to request your private device passcode.

Use the account support path and state that you are making a Privacy Policy data request. Include your registered phone number and the records you want to ask about. We verify account ownership before sharing personal details, then explain what we can provide under the rules that apply to your region.

You can request a correction or deletion where applicable by contacting support with your registered phone number and a specific description of the record. We assess the request against account operation, payment reconciliation and legal retention duties. If removal cannot happen immediately, we explain the reason and the available next step.

We keep payment references for as long as needed to confirm account activity, resolve a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, and meet applicable legal duties. The stored record is used for reconciliation and support; when no longer needed, it is deleted or de-identified.

Yes. Account access and eligibility depend on local law. Our Privacy Policy is written for the Indonesia-facing service, but a request or processing activity can be affected by the rules for your location. Contact us with your region and question, and we will explain the applicable route where local law permits.

Related Pages

dewa6d Indonesia Access guide FAQ Toraja Gold Reels Live Baccarat Gold