Reference

bbca4d Privacy Policy for Your Account

The bbca4d Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, contact support, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesContact routes
bbca4d bbca4d Privacy Policy for Your Account
CONTACT OPTIONS

Three Ways To Ask About Privacy

A direct request helps us locate the right record without asking you to repeat your whole account history.

Account contact Send a Privacy Policy request through the support route displayed after account access.
Wallet query For DANA, OVO, GoPay or QRIS records, include the payment reference and date shown…
Correction request Ask us to correct a name, phone detail or contact address through the account…
DATA PRACTICE

What We Do With Your Personal Data

Privacy Policy choices work best when each data action has a clear reason. We use account and device records to keep sign-in consistent, payment references to trace wallet status, and contact details…

Account details

We collect details you enter when opening an account and the phone verification result connected to access. These details help us identify your profile, answer a Privacy Policy request, and prevent another person from receiving information about you.

Cookies

Cookies and similar browser records can remember sign-in state, language choices and page activity needed for the service. On a mobile browser, you can clear them through browser settings; clearing cookies may require you to sign in again.

Device signals

We may record browser type, device signals and sign-in time to spot unusual account access. These signals are used for account protection and support checks, not as a substitute for your phone verification or as a public profile.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can remain with the transaction record. We use it to match receipts, investigate a status question and separate your account history from another person’s payment.

Retention

We keep personal data only while its operating purpose, an unresolved request, or an account and transaction check requires it. When a record no longer needs to be retained, we remove it or make it unavailable for ordinary account support.

Your request

You may ask for access, correction, clarification or a change to an available permission through our account support contact. Tell us the request type and registered contact detail; we verify ownership before releasing, changing or explaining personal data.

Privacy Policy Answers For bbca4d

These Privacy Policy answers address the questions we expect before account access in Indonesia. They explain the records connected to sign-in, mobile browsing, local wallet activity and support requests without turning a policy question into a general lobby description. If your situation is not covered, use the contact route inside your account and include the relevant reference. We will first confirm that the request belongs to you, then explain the applicable record or next step where local law permits.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and transaction references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains why we use each category, how retention works, and how you can request access or correction.

Yes. When you use a mobile browser, we may record browser and device signals, sign-in time, cookie state and pages opened. These records help maintain access and answer support questions. You can clear browser cookies in your device settings, although this may sign you out.

We keep the reference needed to match a DANA or QRIS receipt with the correct account and transaction status. The reference is not your wallet password. If you contact support about a missing status, send the date and receipt reference so we can check the relevant record.

You can request access through the support contact shown inside your account. Include your registered email or phone detail and state that the request concerns the Privacy Policy. We verify account ownership before explaining or sharing records, and the response depends on local law.

Send a correction request through the account support route and identify the field that is wrong, such as your phone detail or contact address. Tell us the replacement value. We check ownership and the account record before applying a correction where local law permits.

Retention depends on why the record exists, whether a support request remains open, and whether an account or transaction check is still required. Payment references may stay with transaction history for that purpose. We remove or restrict ordinary access when the reason ends.

Use the support contact displayed after you access your account. Describe the Privacy Policy issue, add your registered contact detail, and attach a receipt reference only when relevant. We may ask for an ownership check before discussing personal data or changing an account record.