Reference

Open the abcd188 Privacy Policy for Your Account

The abcd188 Privacy Policy explains how we handle the details connected with your account, including phone verification, DANA and QRIS activity, device access and support requests.

Account dataWallet recordsCookie choicesAccess requests
abcd188 Open the abcd188 Privacy Policy for Your Account
CONTACT OUR TEAM

Contact Support About Privacy Requests

A clear support path helps you raise a privacy question without sending sensitive details to the wrong place. Use the account support route connected to your abcd188 access, describe the request in plain English, and include only the reference needed to locate it. We can then check account access, wallet status or a data request while keeping the conversation tied to your verified account.

Team online

Account access

If you cannot reach the Privacy Policy or your account page, use the support route linked from the login area. We may ask you to complete phone verification before discussing account-specific data.

Wallet records

For a DANA, OVO, GoPay or QRIS record question, send the transaction reference shown in your account rather than a wallet password or full security code. We use that reference to check the correct entry.

Change request

To request a correction, deletion or copy of personal data, state which account detail is involved and how we can confirm it is yours. We assess each request under local law before making a change.

SEE OUR PROCESS

See How We Handle Your Data

Privacy work is part of the account path, not a separate promise hidden from you. We limit account details to the people and systems that need them for access checks, transaction matching…

Account details

We use details such as your phone verification status, login record and account identifier to connect requests with the correct account. We do not need your wallet password when checking a DANA, OVO, GoPay or QRIS reference.

Cookies and devices

Cookies and device signals can help keep a session connected and identify unusual access. You can review cookie controls in your browser, although changing them may affect login continuity or the way the Privacy Policy loads.

Account protection

Before we discuss account-specific data, we may ask for the phone verification step used during access. Never send a password, wallet PIN or full payment credential through a support message.

Transaction matching

A payment reference helps us match a wallet or bank record to your account without requesting unnecessary details. This applies to QRIS, virtual account and bank transfer questions as well as local wallet status checks.

Retention period

We retain account, support and transaction records only for the period needed for the purposes described in this Privacy Policy, unless local law requires a longer period or permits another handling period.

Your request route

To ask for access, correction or removal, use the support path connected to your account and identify the specific record. We confirm the request before acting and explain any limit that depends on local law.

Ask About the abcd188 Privacy Policy

These answers address the searches we hear most often about account privacy, wallet records and access requests. They are written for your account journey, from the first phone verification step to a later request about cookies, retention or a DANA transaction. If your situation is not listed, use the support route connected to your account.

It covers account details, phone verification, login and device records, cookies, support messages and transaction references. It also explains why we use these records, how retention works and how you can request access or correction under the rules that apply to your account.

Yes. The Privacy Policy explains how we use references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use a reference to match the correct account or investigate a status question, without asking for your wallet password or PIN.

Use the support route connected to your account and ask for a copy of the specific data you want to access. Include your account identifier or relevant transaction reference, then complete phone verification if requested so we can confirm the request is yours.

Yes, you can request a correction by naming the account field that is inaccurate and explaining the change needed. We confirm your identity before updating it, and the result depends on local law where a record must be retained or cannot be changed.

We keep account, support and transaction records for as long as needed for the purposes described in the Privacy Policy, subject to applicable retention duties. The period can differ by record type, and local law may require a longer period.

Cookies can keep a browser session connected and help us recognise unusual access across a mobile browser or desktop session. You can change cookie settings in your browser, but blocking some cookies may interrupt login continuity or policy-page functions.

Use the support path linked to your account and describe the privacy issue without sending passwords, wallet PINs or full payment credentials. For a DANA, OVO, GoPay or QRIS question, add only the reference needed for us to locate the record.