Reference

duar77 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a duar77 account, move between the casino and sports areas, or use DANA and QRIS.

Clear data purposesWallet record contextPhone verificationRequest paths
duar77 duar77 Privacy Policy for Your Account
REQUEST ROUTES

Get Help With Privacy Requests

A clear request route helps us locate the right account record without exposing it to the wrong person. Start from the account support path when you need a copy, correction or explanation of data linked to your phone verification. If a wallet receipt is involved, include the payment reference and selected rail, such as QRIS or DANA. We may ask you to confirm account details before discussing records, and we keep the request attached to the relevant case so our response stays focused.

Team online

Account data request

Use account support to ask what personal records are linked to your duar77 login. We may confirm your phone verification step first, then explain the available access path and the records that can be shared with you.

Wallet record query

For a DANA, OVO, GoPay or QRIS query, send the payment reference and account identifier through support. This lets us separate a wallet status question from unrelated game activity and check the matching transaction record.

Correction request

If your account details are outdated, ask support to correct them and state which field needs attention. We may request account confirmation before changing a phone, identity detail or contact record connected with access.

HANDLING PRACTICE

What We Do With Your Records

We keep this policy practical by tying each data action to a recognisable account event. Opening Live Roulette Gold, checking Fishing War Arcade, or entering Serie A Mix Parlay can create activity…

Purpose-led collection

We collect account, phone verification, device and payment-reference details for stated purposes such as access, security, receipt matching and support. Activity around Live Roulette Gold or Serie A Mix Parlay is handled as account activity, not as a separate identity profile.

Cookie choices

Cookies and similar device signals can help keep your session connected and remember practical settings. You can ask support which cookie category relates to your account path, and we will explain the available control or removal option for that record.

Account protection

Phone verification helps connect account access to the details you supplied. We use checks around login, device signals and wallet references to spot mismatches before discussing account records, including a request involving QRIS or a virtual account.

Retention decisions

We retain records for as long as they support the stated purpose, account security, an open support case or a legal duty. When a record no longer needs to remain, we remove it or handle it in a way that limits further use.

Who handles requests

Our account support route receives privacy questions and passes them to the team handling data requests. Keep your request specific: name the record, account step or payment reference involved, without sending a password or full wallet credentials.

Changes you can ask for

You can ask us to access, correct or delete eligible personal records, or object to a stated use where local law permits. We assess the request against account security and retention duties, then explain any part we cannot change.

Privacy Policy Answers for duar77

These Privacy Policy answers address the account questions we expect from Indonesian customers before they open an account. They cover phone verification, device access, cookies, wallet references and requests for copies or corrections. If your situation is not covered, use the account support route with the smallest useful set of details, and do not send a password or complete wallet credential.

It covers details supplied during account opening, phone verification records, device and cookie signals, activity records, payment references and support requests. It also explains why we use those records for access, security, receipt matching, support and legal duties.

Yes. When you select DANA or QRIS, we may record the account identifier, payment reference and status needed to match the request. The same approach can apply to OVO, GoPay, bank transfer and virtual account records.

Where local law permits, you can request access to eligible records connected with your account. Send the request through account support, complete any account confirmation we require, and specify whether you mean login, device, cookie or wallet data.

Phone verification helps us confirm that a request comes from the account holder. We may use that step, together with account details, before discussing records or changing them. We do not ask you to send a password or full wallet credential.

You can ask us to correct an inaccurate record or delete eligible data where local law permits. We assess the request against security needs, open support cases and legal retention duties, and explain clearly if a record must remain.

We may use browser, device and cookie signals to keep your session connected, remember practical settings and identify unusual account access. Ask support which category applies to your case and what control or removal option is available.

Open the account support route and label your request as a Privacy Policy question. Include your account identifier and a short description of the record involved. If it concerns a wallet receipt, add the reference and selected payment rail.