Reference

Open cakrabola Privacy Policy Before Account Access

cakrabola Privacy Policy sets out what we collect when you create an account, verify your phone, browse Speed Blackjack or use a local wallet.

Account dataWallet recordsDevice cookiesPrivacy requests
cakrabola Open cakrabola Privacy Policy Before Account Access
REQUEST ROUTES

Ask About Privacy Policy Through Account Support

A privacy question should not disappear inside a general payment query. Use the support route attached to your cakrabola account and describe the request in plain English, such as a correction to…

Account privacy request Send a request from your account support path when you want to access, correct or remove eligible data. We may confirm your phone details before sharing account-linked records.
Wallet record question Mention DANA, OVO, GoPay or QRIS when asking about a payment record. Naming the rail helps us locate the relevant status without asking you to resend unnecessary personal details.
Locked access help If phone verification or a device change blocks access, contact support through the available account path. We check identity first, then explain which privacy request can proceed.
HANDLING DETAILS

Protect Your Data Across Devices And Wallets

We treat privacy as an operating step inside every account action, not as a footer link. Our process separates sign-in checks from wallet references, records consent where required and limits staff access…

Data collected

We may receive your account contact details, phone verification result, sign-in events, device signals and transaction references. We use each category for access, security, support or a stated account service.

Cookie choices

Cookies and similar device storage can remember session settings and help us detect unusual sign-ins. You can manage browser storage through your device settings, though some account functions may then need another check.

Account security

A new device or changed sign-in pattern may trigger an identity check before account details are shown. Keep your phone access private and never send a verification code through a support message.

Wallet separation

A DANA, OVO, GoPay or QRIS reference helps us match payment status, but support does not need unrelated wallet content. We use the smallest record needed to resolve your account request.

Retention choices

We retain personal data for the period needed to provide account access, investigate security events, settle disputes or meet legal duties. When a record is no longer needed, our handling process addresses removal.

Change requests

You can ask us to access, correct or remove eligible personal data through account support. Tell us the requested change and the account step involved so we can verify identity and respond clearly.

Find Privacy Policy Answers Before Joining

These Privacy Policy questions cover the account steps Indonesian customers usually ask about before opening access. If your situation involves a particular device, wallet or game record, include that detail in your support request so we can give a precise answer without broadening the data shared.

The cakrabola Privacy Policy covers account details, phone verification, sign-in events, device cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

We use the verification result to confirm account access and help detect unusual sign-ins. We do not need the contents of your phone; the relevant record is the verification status linked to your account.

Yes. Send an access request through account support, describe the data you want to see and complete the identity check. We then explain which eligible account records can be provided.

Contact account support with the incorrect detail and the requested correction. For phone or wallet-linked changes, we may verify your identity before updating the record or confirming the result.

Yes. The policy covers payment references and status records used to match DANA or QRIS activity with your account request. We do not ask for unrelated wallet content to answer a query.

Cookies can keep a session active and help identify unusual device activity. You can clear or restrict them in your browser settings, but a later sign-in may require another account check.

You may request deletion of eligible personal data through account support. Some records can remain when required for security, disputes, transaction matching or legal duties, and we will explain that reason.