Reference

Open rajacabe88 Privacy Policy Before Account Access

The rajacabe88 Privacy Policy shows what we collect when you create an account, verify your phone, enter the lobby or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record detailsDevice choice controlsAccount request path
rajacabe88 Open rajacabe88 Privacy Policy Before Account Access
REQUEST ASSISTANCE

Check Policy Help Through Account Support

A clear support route matters when a privacy request meets a login or wallet status issue.

Account privacy request Send your request through account support and describe the exact record involved, such as…
Wallet record question If DANA, OVO or GoPay appears in a privacy question, provide the transaction reference…
Cashier path issue When a privacy request relates to bank transfer or virtual account activity, contact us…
DATA CONTROLS

Switch Devices With Policy Controls

We keep privacy controls close to the account steps where they matter: phone verification, login, wallet matching and support requests.

Account data

We use details such as your phone number, verification result and account activity to provide account access, investigate requests and protect the account from suspicious sign-in behaviour.

Cookies and sessions

Cookies and session records help keep you signed in, remember selected settings and connect a request to the correct account. Your browser controls can limit cookies, though some account steps may then need repeating.

Device security

A mobile or desktop device can create security signals such as browser type, session time and approximate access pattern. We use these signals to check unusual activity, not to read unrelated device content.

Payment matching

For QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity, we keep references that connect a payment status with your account. Wallet passwords and PINs remain outside our requested support details.

Retention choices

We keep personal records for the purposes stated in the Privacy Policy, including account support, security checks and resolving payment disputes. When a retention need ends, records are deleted or changed so they no longer identify you.

Change request

You can ask us to correct inaccurate details, explain a processing purpose or review an eligible removal request. Contact account support with the phone-linked account details needed for an ownership check.

Browse Privacy Policy Answers for rajacabe88

These Privacy Policy answers focus on the searches you may make before opening an account or when checking an existing record. We keep the explanations tied to actual account steps, device behaviour and Indonesian payment references. If your question involves eligibility or account access, the answer depends on local law and applies where local law permits.

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

Phone verification helps connect a request to the correct account and supports account security. We may use its result when you ask to change details, inspect a record or resolve a login issue.

Yes. The Privacy Policy explains that we may retain transaction references and status for QRIS, DANA, OVO and GoPay when those details are needed to match an account action or resolve a payment question.

You can contact account support with the phone-linked account details required for ownership checking. Tell us which records you want, such as sign-ins, device details, support messages or payment references.

Send a correction request through account support and identify the inaccurate field. We may ask for account verification before changing phone, profile or payment-related details so another person cannot alter them.

Retention depends on the purpose described in the Privacy Policy, including security, account support and payment disputes. When that purpose ends, we delete or de-identify the relevant record under our procedures.

The policy still applies when you move between mobile and desktop. We may record browser and session signals to protect access, while cookies and settings can behave differently according to your device controls.