Reference

Privacy Policy for Your DANA Account

Our Privacy Policy explains how we handle the account details, device signals and wallet records connected with your raja cabe88 access.

Clear data choicesWallet record detailsPhone verification contextIndonesia access wording
raja cabe88 Privacy Policy for Your DANA Account
PRIVACY HELP PATH

Get Policy Help Beside Your Account

A clear support route matters when a privacy question appears during login or while you check a wallet status. We ask you to use the support path connected to your account so we can confirm the request belongs to you before discussing personal details. Include the account contact, the relevant payment reference and the change you want, while keeping passwords and one-time codes private. This keeps a DANA receipt question separate from a request to access or correct account data.

Team online

Account privacy request

Use the account support path to ask what personal details we hold, why they are used and which account step is needed before we respond.

Wallet record question

For DANA, OVO, GoPay or QRIS status records, include the reference shown in your cashier history so we can locate the correct transaction data.

Security concern

If your account opens on an unfamiliar device, tell us through support and change your password before sharing any further details about the session.

DATA HANDLING

What We Keep And Why

We keep this policy practical by linking each data category to an account task you can recognise. Account details support login and contact; payment references support reconciliation; device signals support session security…

Account details

We use contact and verification details to create, maintain and secure your account. The phone verification step helps us avoid sending private account responses to the wrong person.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can include a reference, amount status and timestamp used to match your payment question.

Device signals

Browser, device and session signals help us identify unusual sign-ins and keep the account path consistent when you move between mobile and desktop.

Cookies

Cookies can retain session preferences and your policy choice. You can clear browser cookies, although doing so may require you to verify the account again.

Retention

We retain records only for the account, security, reconciliation or support purpose that needs them, subject to the local requirements connected with your access.

Policy changes

When this Privacy Policy changes, we update the page and identify the affected topic. You can ask support to explain a change or request a correction to your data.

Privacy Policy Answers For raja cabe88

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We focus on what is collected, how wallet records are matched, how requests are checked and where local law affects access. If your question is not covered, use the account support path and include only the details needed to identify your request.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment records connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention, security and ways to request access or correction.

Phone verification helps us connect an account request to the right person before discussing private details. It may be used during account access or a data request. Keep verification codes private, and contact support if an unfamiliar device opens your account.

Yes. The policy includes payment references and status records created when you use DANA or QRIS, along with OVO, GoPay, bank transfer and virtual account records. We use those details to reconcile a payment question and support the related account.

Use the support path connected to your account and ask for a copy of the personal details held about you. Include your account contact and a clear request. We may ask for phone verification before disclosing data or discussing account-specific records.

You can ask us to correct inaccurate account details through the account support path. State which field is wrong and provide the current value. We may check the request against your phone verification before making a change to protect the account.

Retention depends on why the record exists, such as payment reconciliation, account security or a support request, and on local requirements. A DANA, QRIS or bank reference may remain while that purpose needs it. Ask support about a particular record.

Yes. Account access and the handling of certain requests depend on local law. We apply this Privacy Policy where local law permits, and support can explain the account path available to you without asking for your password or one-time code.