Reference

Privacy Policy for Your Account

The dewa 212 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
dewa 212 Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Your Data

A clear contact route helps when a Privacy Policy question concerns your phone verification, wallet status or a stored payment receipt. Start from the support contact shown in your account area and include the phone number linked to your account, the relevant date and the type of request. We use those details to locate the correct record without asking you to send a full wallet password or account login code. If access is unavailable, use the contact route published on the Privacy Policy page and describe whether you need access, correction or deletion support.

Team online

Account access

If you cannot reach your account after phone verification, contact us through the account support route and state that your request concerns the Privacy Policy. We can use your linked phone number and recent access details to identify the account without requesting your login code.

Wallet records

For a DANA, OVO, GoPay or QRIS record, send the payment date, displayed status and reference shown in your cashier history. Please hide passwords and one-time codes. We use the receipt reference to check which account record your Privacy Policy request concerns.

Data requests

To ask for a copy, correction or removal of personal data, use the published contact path and name the request clearly. We may ask for an account check before responding, so a private request is linked to the right account holder.

ACCOUNT DATA PRACTICE

How We Handle Account Records

The Privacy Policy is applied through ordinary account steps rather than broad promises.

Data collection

We collect the account details you enter, phone verification results, device and browser signals, and transaction references created through DANA…

Cookie choices

Cookies can remember a sign-in state, language setting or security preference on the device you use.

Account security

We use phone verification before account access and may compare device or sign-in signals when activity looks unusual.

Payment matching

A wallet name alone does not explain a transaction, so we match the payment reference, account identifier and displayed status.

Retention choices

We keep records for the period needed to provide account access, resolve a payment question, protect the service or meet…

Changes and contact

You may ask which personal data we hold, request a correction, or ask about deletion through the published Privacy Policy…

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account steps most likely to raise questions in Indonesia: phone verification, wallet records, browser cookies, device access and requests for a copy or change. We keep the wording practical so you know what to send us and what we may need to confirm. If your question involves eligibility or service access, that decision depends on local law and the circumstances of your account.

It covers account details, phone verification, device and browser signals, cookies, payment references and contact requests. It also explains how we use those records for account access, security, payment matching and support, including transactions connected with DANA, OVO, GoPay, QRIS or bank transfer.

We do not need your wallet password or one-time code to match a payment. Our records may include a payment reference, displayed status, amount and linked account identifier. When contacting us about DANA or QRIS, hide passwords and codes from any receipt image.

Use the support contact route published on the Privacy Policy page or shown in your account area. State that you want a copy of your personal data and include your linked phone number. We may complete an account check before sending a response.

Yes. Send a correction request through the published contact path and identify the field that needs changing, such as a phone number or account detail. We may ask for verification so the change is applied to the correct account and not to another record.

Cookies can remember browser settings, sign-in state and certain security preferences. If you block or clear them, we may ask you to repeat an account step or phone verification. Your browser controls manage these files, while our Privacy Policy explains their account-related purpose.

We retain payment references and related account records only for the period needed for access, reconciliation, security, dispute handling or a legal requirement. A request about a DANA, OVO, GoPay, QRIS or bank transfer record can be sent through our published contact route.

Yes. Account access and eligibility depends on local law. Where local law permits, we handle the account and payment records needed for the stated service purpose. If you need clarification about a location-based restriction or your data, contact us with your account details.