Reference

dp96 Privacy Policy For Your Account

dp96 Privacy Policy explains what we collect when you open an account, connect DANA, OVO, GoPay or QRIS, and move between the lobby and cashier.

Account dataWallet recordsDevice choicesContact route

Explore Our Lobby Read FAQ

Open The Policy Before Wallet Setup

dp96 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies from the moment you begin the account path and continues while you use account, lobby and cashier pages. We may handle details needed to verify your account, protect sessions, record payment status and respond when a DANA, OVO, GoPay, QRIS, bank transfer

1
or virtual account request needs checking. We use these records for the stated service purpose, not for unrelated activity. Cookie choices can affect how pages remember your session. Access and eligibility depends on local law, and some account or payment actions may require a matching account
2
name or additional checks. The policy also explains retention, contact steps and how to ask about a correction or deletion.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT THE TEAM

Reach Support About Privacy Questions

A clear contact route matters when your account record or wallet status needs attention. Use the support link beside the account and cashier path, describe the request in plain English, and include only the details needed to locate your account. We can help you understand a data request, payment receipt record or access issue, while you should never send a full password or wallet PIN.

Team online

Account request

Ask us to explain, correct or update account details through the support path connected to your account. We may ask you to complete the clear phone verification step before discussing private records or applying a requested change.

Wallet record

If a DANA, OVO, GoPay or QRIS receipt appears incorrectly, share the date, amount reference and wallet name without sending a PIN. We use those details to locate the payment record and explain its status.

Access concern

When login or device access stalls, contact support from the account path and describe the device behaviour. We can check session details and guide the next identity step without asking you to disclose your password.

HOW WE HANDLE DATA

Browse The Data Choices We Keep Clear

We keep Privacy Policy decisions tied to the way your account actually works. A phone check helps us separate your account from an unfamiliar session, while payment records help us trace a…

Account details

We collect details you provide during account opening and phone verification so we can maintain the correct account record. The same record may connect your casino and wallet activity, allowing us to investigate an access or payment question.

Payment traces

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can show a reference, status and account link. We use those details to reconcile a receipt or investigate a mismatch, rather than requesting your wallet PIN.

Cookies

Cookies may remember a session or selected page setting when you move from login to the lobby on mobile or desktop. Browser controls let you remove or block them, although some account functions may then require another login.

Security steps

Phone verification and session checks help us respond when an unfamiliar device reaches your account. Keep your password private, sign out on shared hardware and contact us if the account path shows activity you do not recognise.

Retention

We retain account and payment records for the period needed for the stated service, security checks and dispute handling. When you ask how long a particular record remains, support can explain the applicable retention basis and next step.

Change requests

You can ask us to access, correct or clarify personal data through the support route. Include the account phone detail and the precise request; we may verify ownership before making a change so another person cannot alter your record.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain account data, cookies, wallet records, phone verification and contact steps in practical terms. If your question is specific to a receipt, device or correction request, use the support path beside the cashier and refer to the relevant account detail.

The dp96 Privacy Policy covers data collected during account opening, phone verification, login, wallet activity and support contact. It also explains cookies, device signals, payment records, retention, security handling and the route for asking about access, correction or deletion.

Phone verification helps us confirm that the person requesting account access or a data change controls the registered account. It can also help us investigate an unfamiliar session. We will not ask you to share your password, wallet PIN or secret code.

Yes. The Privacy Policy covers records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. A receipt reference or payment status may be used to match an account and resolve a cashier question without requesting private wallet credentials.

Use the support route linked beside your account and state which detail needs correction. Include the registered phone detail and a short explanation, but do not send your password or wallet PIN. We may verify account ownership before changing the record.

Cookies can help retain a login session or page setting when you move through the mobile lobby. Your browser controls can block or remove them. If you disable cookies, you may need to log in again or repeat an account step.

We keep records for the period needed for the stated account service, security checks and payment dispute handling. The applicable period can differ by record type and local requirements. Ask support about a particular account or receipt record for a clearer response.

Yes. Send an access or deletion request through the support path connected to your account and describe the record involved. We may complete an ownership check before responding. Any action or eligibility depends on local law and the applicable record requirements.

dp96 Privacy Policy For Your Account

Reach Support About Privacy Questions

Account request

Wallet record

Access concern

Browse The Data Choices We Keep Clear

Account details

Payment traces

Cookies

Security steps

Retention

Change requests

Browse Privacy Policy Answers Before Opening

01 What does the dp96 Privacy Policy cover?

02 Why does dp96 need my phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a correction to my dp96 data?

05 How does the Privacy Policy handle cookies on mobile?

06 How long does dp96 keep account and payment data?

07 Can I contact dp96 about data access or deletion?

Related Pages