Reference

Legal access for your dpr189 account

dpr189 Legal sets out how we handle account access, identity checks, wallet records, cookies, and requests about your personal data.

Policy accessAccount checksData choicesWallet records
dpr189 Legal access for your dpr189 account
POLICY CONTACT

Get help with Legal questions

A clear contact path matters when a policy question affects your account, so we keep requests close to the account and cashier areas.

Account support route Use the support link inside your signed-in account when you need a Legal answer about phone verification, account access, or a restriction. Mention the page or decision involved, and we will check the account record connected to your request.
Wallet record check For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, open the support path beside the cashier area. Attach the payment receipt reference and date, but do not send a wallet PIN or full security credential.
Policy change request Ask us to review an eligible data correction or policy request through your account support route. State what should change, why the record is inaccurate, and which phone detail identifies your account so we can verify the request.
DATA PRACTICE

How we handle your Legal rights

Legal rights are useful only when the operating steps are clear. We describe what we collect for account access, why transaction records may be needed, how cookies support a signed-in session, and…

Data handling

We use the account details you submit to create access, complete phone verification, and connect your wallet or payment record to the right account. A DANA or QRIS receipt may also contain provider-side data that remains subject to that provider's own terms.

Cookies

Cookies can keep your signed-in session working and remember security-related choices on the device you use. You can manage browser cookie settings, but turning them off may interrupt Legal consent records or the mobile path from login to the lobby.

Account security

Phone verification is required before account access, and we do not need your wallet PIN to check a payment case. Use your own device where possible, keep sign-in details private, and contact support through the account when access behaviour looks unfamiliar.

Record retention

We retain account, security, and payment records for the period needed to operate the account, resolve disputes, and meet applicable legal duties. The relevant Legal notice explains the record type and the conditions that affect its retention.

Access decisions

Eligibility and access depends on local law. If your account cannot reach a table such as Omaha Online Room, check the policy message first and contact us through support rather than attempting repeated verification from different devices.

Request changes

To correct an inaccurate name, phone detail, or account record, send a signed-in request with the exact change and supporting context. We may ask for an account step to confirm that the request comes from the account holder.

Answers about dpr189 Legal

These Legal answers address the questions we expect before an Indonesian account is opened or accessed. They cover local eligibility, account records, cookies, wallet evidence, data requests, and support contact. If your situation is not covered, use the signed-in support route and refer to the specific policy section or account step that prompted your question.

dpr189 Legal covers account access, phone verification, personal data, cookies, security, payment records, retention, and eligible correction requests. It also explains how to contact us about a policy decision. Access depends on local law, so check the applicable rule before opening or using an account.

Yes. Access depends on local law, and availability may differ according to the location and circumstances connected with your account. We ask you to provide accurate account details and complete phone verification. Do not try to bypass an access decision by switching devices or altering account information.

Phone verification connects the account to a confirmed contact detail before access and helps us investigate an account request safely. It may be relevant when you ask about a Legal record, a wallet status, or an unfamiliar login. Never send a wallet PIN through support.

We use payment references to match a DANA or QRIS transaction with the correct account and to resolve a status question. The provider may retain its own transaction data under separate terms. Send only the receipt reference and date through the signed-in support route.

You can request an eligible correction through the account support path. State the inaccurate field, the proposed correction, and the account detail that helps us locate it. We may ask for an account step to confirm your identity before changing a phone detail or other record.

Cookies can preserve a signed-in session and record security or policy choices on your browser. If you block them, the mobile or desktop account path may ask you to repeat a step. Browser settings control cookies, while the Legal notice explains their role in access.

After login, use the support link near the account and cashier areas. Describe the Legal issue, include the relevant date or policy message, and avoid sending passwords, wallet PINs, or unnecessary personal details. This route lets us connect the request to the correct account record.