Reference

abc33 Privacy Policy For Your Account Data

abc33 Privacy Policy explains how we handle the details connected to your account, including DANA, OVO, GoPay and QRIS references used during wallet checks.

Account dataWallet referencesCookie choicesAccess requests

Explore Our Lobby Read FAQ

How DANA And QRIS Data Is Used

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

Our Privacy Policy separates account details from payment records so you can understand each use. When you create an account, we may request your name, phone number and a verification result before access is completed. A DANA, OVO, GoPay or QRIS transaction can produce a wallet

1
reference, amount, status and time, while bank transfer or virtual account activity can show a bank rail such as BCA, BRI, Mandiri or BNI. We do not need your wallet PIN to display a payment status. We use these records to match deposits, investigate a missing
2
receipt, confirm a withdrawal request and protect the account from unauthorised access. Where local law permits, we may share limited payment details with the payment service involved or with a service provider acting for account security. Access to the lobby and related processing depends on local
3
law. We keep records for the period needed for the stated purpose and applicable legal duties.

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

PRIVACY CONTACT

Get Help With A Privacy Request

A clear contact path helps when your account record or wallet status needs attention.

Account access If you cannot complete phone verification, tell us which account step stopped and provide the linked number. We will use the account record to assess an access request.

Payment record For a DANA, OVO, GoPay or QRIS query, attach the transaction reference rather than your wallet PIN. This lets our support path check status while limiting sensitive data.

Data request Ask to access, correct or remove eligible personal data through the signed-in contact path. We may confirm account ownership before responding to protect your records.

DATA CONTROL

How abc33 Handles Device And Account Data

We keep the Privacy Policy practical by linking each data type to an account action. Device signals can help us recognise an unusual login, while cookies support session continuity and your selected…

Account security

We use sign-in details, phone verification status and selected device signals to detect unusual access. Never send us your password, wallet PIN or one-time security code.

Cookies

Cookies can keep your session active, remember selected settings and help us understand page errors. You can adjust cookie controls in your browser, though some account functions may change.

Device details

A mobile browser may send device type, operating system, language and diagnostic events when the account page loads. We use these details to fix access and display problems.

Payment matching

Wallet and bank references help us match a deposit or withdrawal status to your account. We do not ask for a DANA, OVO, GoPay or QRIS PIN.

Retention

We retain personal data only while it serves the stated account, security or payment purpose, or while applicable legal duties require a record. Older data is removed or restricted when practical.

Your request

You can ask how your data is used, request a correction or ask about removal through support. We may request account details to confirm that the request comes from you.

Privacy Policy Answers For abc33

These Privacy Policy answers address the account, device and payment questions we expect before you open an account. They explain the practical route for checking your records, changing details and contacting us, with access depending on local law.

It covers personal details, phone verification, sign-in activity, device signals, cookies, wallet references and support messages connected with your account. It also explains use, sharing, retention and request routes.

We use your phone number to create and protect the account, complete the required verification step and help locate your record when you contact support. Keep it current so access checks work.

Yes. The policy covers transaction references, status, amount and time linked to DANA, OVO, GoPay or QRIS activity. We do not need your wallet PIN to check payment status.

You can send an access request through the signed-in support path. Include your linked phone number and request details; we may confirm account ownership before releasing or discussing personal records.

Cookies can maintain your session, store selected settings and help identify page errors. Browser controls let you adjust them, but refusing necessary cookies may affect sign-in or account pages.

We keep data while it supports the stated account, payment or security purpose, and for any period required by applicable law. We then remove, restrict or anonymise it when practical.

Ask through the account support contact path and identify the record you want changed. We assess correction or deletion requests against account security, payment records and applicable legal requirements.

abc33 Privacy Policy For Your Account Data

Get Help With A Privacy Request

How abc33 Handles Device And Account Data

Account security

Cookies

Device details

Payment matching

Retention

Your request

Privacy Policy Answers For abc33

01 What does the abc33 Privacy Policy cover?

02 Why does abc33 need my phone number?

03 Does the Privacy Policy include DANA and QRIS data?

04 Can I ask abc33 what personal data it holds?

05 How do cookies affect my abc33 account?

06 How long does abc33 keep my account data?

07 Can I correct or delete data under this Privacy Policy?

Related Pages