Reference

Privacy Policy For Your Account

dewan4dlogin Privacy Policy shows how we handle your account details, wallet records and device access while you use the lobby.

Clear data purposesWallet record detailsCookie choicesAccount contact path
dewan4dlogin Privacy Policy For Your Account
CONTACT YOUR DATA TEAM

Where To Ask About Privacy Policy

A clear contact route matters when a Privacy Policy question affects your account. We ask you to use the account support path linked near the cashier area, then include your registered phone number and the specific record you want checked. That helps us separate a login issue from a wallet-status question without asking you to resend unnecessary documents. If you are in Yogyakarta, the same digital route applies, and we handle requests through the account details attached to your message.

Team online

Privacy request

Tell us whether you want access, correction or deletion of a personal record. Include your account phone number and the relevant date so we can locate the request without collecting extra details.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, attach the transaction reference rather than your wallet password. We use the reference to compare cashier status and explain what record we hold.

Account access help

If phone verification or a saved device blocks access, contact us through the account support path. We may ask account-specific questions before changing details, helping protect your profile.

DATA HANDLING PRACTICE

Six Practical Privacy Controls We Apply

Privacy work is part of the account steps you already see: phone verification, login checks, wallet matching and support follow-up.

Collection purpose

We collect account and verification details to create access, protect sign-in and respond to a case. Game activity such as Live Blackjack Prestige may be linked to your account record so we can resolve a specific access question.

Cookie controls

Cookies can keep a session active, remember a language or device choice and help us spot repeated login failures. You can adjust browser cookie settings, although some account steps may not work when required cookies are blocked.

Wallet matching

A cashier reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account helps us match status. We do not need your wallet password for that check, and support should never ask you to disclose it.

Account security

Phone verification comes before account access, and unusual device behaviour may trigger an extra check. Keep your phone and login details private; we use these signals to reduce the chance of an unauthorised profile change.

Retention period

We keep records only for the period needed to provide access, settle a support case, detect misuse or meet a legal duty. When a record is no longer needed for those purposes, our handling process removes or restricts it.

Change requests

You can ask us to correct an outdated phone detail, explain a stored record or consider deletion. Send the request through account support; we verify ownership first and explain any reason a legal or transaction record must remain.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the searches we hear before an account is opened or a wallet record is queried. We explain the practical path for your data, including phone verification, browser cookies, payment references and requests sent through account support. If a question depends on your location or eligibility, the answer remains subject to local law.

It covers the personal data connected with your account, phone verification, login activity, cookies, support messages and payment references. It also explains why we use those records, how we protect access, how long records may remain and how you can request a correction or deletion.

No. Our Privacy Policy treats a DANA or QRIS transaction reference as a status-matching detail, not as a wallet password. The same approach applies to OVO and GoPay. Never send a wallet password through support; a reference and account phone number are normally more useful.

Phone verification connects the account to a contact route before access and helps us distinguish you from someone attempting a profile change. The result may be recorded with the account. If verification fails, use account support and provide only the requested ownership details.

Send a Privacy Policy request through the account support path near the cashier area. State whether you want access or correction, identify the account phone number and describe the record. We verify ownership before responding, and the available process depends on local law.

Cookies can retain a sign-in session, remember device settings and help identify repeated access failures. Blocking every cookie may interrupt phone verification or return you to login. You can change browser settings, while required cookies remain subject to the account function they support.

We retain transaction references, support records and access logs for the period needed to match status, settle a case, protect the account or meet a legal duty. The period can differ by record type. When no purpose remains, the record is removed or restricted.

You can submit a deletion request through account support, and we will assess it against the purpose for holding each record. Some account, security or payment records may need to remain for a legal or transaction reason. Any access depends on local law.