Reference

dianbet Privacy Policy for Your Account

Your account path keeps profile, phone verification and wallet records connected to the right activity, while our Privacy Policy explains how we use each data category.

Account data clarityWallet activity contextDevice access choicesPrivacy request path
dianbet dianbet Privacy Policy for Your Account
REQUEST ASSISTANCE

Account Help for Privacy Requests

A clear support path helps when you want to ask about a privacy record rather than a game or wallet result. Open account help while signed in and include your registered phone details, the request type and any relevant receipt reference. We use those details to locate the correct account without asking you to send a full password or security code.

Team online

Account help request

Use the support link beside your signed-in account area to ask about stored profile details, phone verification records or a correction. We may confirm account ownership before discussing private data.

Cashier receipt query

For a DANA, QRIS, OVO or GoPay privacy question, include the receipt reference and approximate date. This lets us separate your payment record from another account without requesting wallet credentials.

Access issue path

If privacy settings or account access stalls on mobile, state your device type and browser path in the support request. We can then identify whether the issue concerns cookies, session data or verification.

DATA CARE PRACTICES

Cookies, Devices and Account Security

We separate account details from ordinary browsing signals so our Privacy Policy can describe what each record does.

Account data

We may store your account name, registered phone details, verification status and support correspondence to maintain access and answer requests. We use these fields for the stated account purpose, not as an open request for unrelated personal details.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match an account action with its status. We record the transaction context needed for checks without asking for your wallet password.

Cookies and sessions

Cookies and session markers can remember a signed-in device path, preserve account steps and detect unusual access. You can manage browser cookies, although removing them may require phone verification again before account access continues.

Security checks

When you request private account details, we may compare your signed-in state with registered phone information. Never place a password or one-time security code in a support message or receipt reference.

Retention period

We retain account, payment and support records only for the period needed for account administration, security checks, disputes and applicable legal duties. A deletion request is assessed against those operating and legal needs.

Change request

You can ask us to correct eligible profile details or clarify how a record is used through account help. Include the registered phone detail and requested change so we can verify ownership first.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the records you are most likely to ask about before opening or using an account. We cover phone verification, wallet references, cookies, device sessions, retention and the practical route for requesting a correction or deletion review.

The dianbet Privacy Policy covers account details, phone verification, device and session records, cookies, wallet references, support messages and the ways we use, retain and protect those records.

We use phone verification to connect account access with the correct registered details and to check ownership before discussing private records. It also helps us distinguish your account from another account using the same device.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use the relevant receipt or status context without requesting your wallet password.

You can request a correction through signed-in account help. Include your registered phone detail, the field you believe is wrong and the requested change. We may verify ownership before making any update.

Cookies and session markers can preserve your login path and account steps on a mobile browser. If you clear them, the next visit may require a fresh sign-in or phone verification before access continues.

We keep account, payment and support records for the period needed for administration, security checks, disputes and applicable legal duties. A deletion request is considered against those needs and the relevant account status.

Open account help while signed in and describe your access, correction or deletion question. Add the registered phone detail and any receipt reference, but do not send your password or one-time security code.