Reference

dutaplay Privacy Policy for Your Account

dutaplay Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification, device access and wallet records.

Clear data purposesWallet record contextAccount request pathIndonesia access wording
dutaplay dutaplay Privacy Policy for Your Account
REQUEST HELP

Ask About Your Privacy Policy Rights

A clear request route matters when you want to understand an account record or correct a detail. Use the support path connected to your account and describe the request in plain English, with the phone number or account reference we can use to locate it. We may ask for account checks before discussing personal data, because sending details to the wrong person would create a privacy risk. If a wallet status or payment receipt is part of your question, include the rail used and the relevant reference rather than sharing your wallet password.

Team online

Account data request

Ask us which account details we hold, why they are used and which records relate to your phone verification. We will use the account path to confirm that the request comes from you before discussing personal details or preparing a copy.

Correction request

If your phone number, contact detail or account record is inaccurate, tell us what needs changing and why. For a DANA, OVO, GoPay or QRIS reference, include the transaction context without sending a password, PIN or full security code.

Privacy support path

When you cannot access the account area, start with the available account-support route and explain the device path you used, such as mobile browser or desktop browser. We can then separate a login issue from a request about personal data.

DATA HANDLING

How We Apply Privacy Controls

Privacy controls work alongside ordinary account checks rather than sitting apart from them. We limit account details to the purposes described in this policy, keep payment references available for status checks, and…

Data purposes

We use submitted account details to create and maintain your account, complete phone verification, respond to support requests and connect payment status to the correct record. We do not need your wallet password or PIN to investigate a receipt question.

Cookie choices

Cookies or related browser storage may support login continuity, security checks and session functions. Your browser can block or clear some storage, although doing so may require another account check when you return to the lobby or account area.

Account security

We use phone verification and access-event checks to reduce the chance that another person reaches your account. A new device or unusual login pattern may lead to an additional check before account details or wallet status are shown.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can contain a reference, amount context or status marker needed to reconcile an account action. We use that operational detail for checking, not as a request for your secret wallet credentials.

Retention questions

Some records remain available while an account, support matter, payment check or legal requirement needs them. If you want to ask how long a particular record is retained, identify the account event and we will assess the request against the applicable rule.

Change requests

You can ask us to access, correct or clarify personal data through the account-support path. Include your account reference and the specific field or event, then complete any identity check needed before we disclose or change the record.

Privacy Policy Answers for dutaplay

These Privacy Policy answers address the account questions you are most likely to have before or after using dutaplay in Indonesia. We keep each answer tied to a real account step, device path or payment reference, so you can choose the right request route instead of sending sensitive credentials. Access and eligibility depends on local law, and the policy applies to account activity where local law permits.

The dutaplay Privacy Policy covers account details, phone verification, device and browser records, cookies, support requests and payment references. It explains how we use those records for account access, security checks, receipt status and legal duties where local law permits.

Phone verification helps us connect an account request with the person attempting access. It can also support an additional check when a new device or unusual login appears. We use the verified phone detail for account security and related support handling.

We may receive or retain payment references and status details connected with DANA, OVO, GoPay or QRIS so we can match an account action and answer a receipt question. We do not ask you to send a wallet password, PIN or security code.

Yes. Use the account-support path and request access to your personal data, naming the account phone number or reference. We may complete an identity check first, then assess which records can be provided under the applicable privacy rule and local law.

Send a correction request through account support and identify the exact field, such as a phone detail or contact record. If the issue concerns a bank transfer or virtual account reference, include the event context without revealing passwords or private codes.

Yes. The policy covers personal data handled through mobile and desktop browser access. Device type, browser details and security events may be recorded for session and account protection. Clearing cookies can lead to another phone or account check when you return.

Use the account-support route and name the record or event you want us to assess, such as a payment receipt or phone verification request. We retain some records for account, support, payment or legal needs, and we will review the request under applicable rules.