Reference

raja cabe88 Privacy Policy Explained

Our raja cabe88 Privacy Policy shows how we collect, use and protect details connected with your account, phone verification and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
raja cabe88 raja cabe88 Privacy Policy Explained
CONTACT PATHS

Get Privacy Help Through Your Account

A clear contact path helps you ask about stored details without sending sensitive records through an uncertain route. We keep privacy requests tied to the account step that created them, including phone verification, wallet status or a receipt check. Use the support contact shown in your signed-in account and include the email or phone detail attached to your profile; access depends on local law.

Team online

Account access

Ask us to explain account details or phone verification records through the signed-in support path. We may request an account step before discussing private details, so your request stays connected to you.

Wallet records

For a DANA, OVO, GoPay or QRIS receipt question, provide the transaction reference shown in your account. We use it to locate the relevant record without asking you to share a wallet password.

Status checks

If a privacy request concerns a bank transfer or virtual account status, tell us which account record you mean. We can check the stored status and explain the next request step.

HANDLING YOUR DATA

How We Keep Privacy Requests Clear

We separate the practical handling of account data from promotional language: each record has a purpose linked to access, security, support or transaction matching.

Account details

We may hold your name or contact detail, phone verification result and account identifiers so we can connect sign-in activity with the correct profile. We use these details for access, support and security checks.

Cookies and devices

Cookies can remember session settings and your privacy choices. Browser and device signals may help identify unusual sign-ins, whether you open the lobby on Android, iPhone or desktop.

Wallet matching

DANA, OVO, GoPay and QRIS references may be stored with transaction status and receipt details. Bank transfer and virtual account records help us answer a specific account query.

Account security

Phone verification and sign-in events help us check that a privacy request belongs to you. Never send a password or wallet PIN in a support message; we do not need either to assess a request.

Retention periods

We keep records only for the period needed for the purpose described here, account security, dispute handling or a legal requirement. When a record is no longer needed, our process addresses its removal or restriction.

Change requests

You can ask us to correct account details, explain a stored record, restrict a use where applicable or remove data where permitted. Include the relevant account step so we can assess the request accurately.

Answers About Your Privacy Policy

These Privacy Policy answers focus on the questions you are most likely to have before opening an account or checking a wallet record. We keep the route practical: identify the account, describe the record, and use the support contact shown after sign-in. Access and any request outcome depend on local law.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and transaction references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect access and privacy requests to the correct account. It also supports account security when you ask about stored details, wallet status or a receipt record.

Yes. It covers the browser session, device signals, cookie choices and sign-in events created when you use an Android phone, iPhone or desktop browser to reach the account.

Use the support contact shown in your signed-in account and identify the detail that needs correction. We may ask for a verification step before changing private account information.

You can request an explanation of account, security, cookie or transaction records connected with your profile. Include the relevant date or reference, and we will assess the request under applicable rules.

We may retain a wallet reference, receipt detail and status so we can match the transaction to your account and answer a support question. We do not need your wallet PIN.

Retention depends on the record’s purpose, account security needs, dispute handling and legal requirements. We address removal or restriction when the data is no longer needed for those purposes.