Reference

xr88 Privacy Policy for Your Account Data

Our Privacy Policy shows how we handle the account details, phone verification records and wallet activity connected with your xr88 access.

Account dataWallet recordsCookie choicesRequest path
xr88 xr88 Privacy Policy for Your Account Data
REQUEST SUPPORT

Get Privacy Policy Help Near Your Account

A clear contact path helps you ask about the Privacy Policy without sending sensitive details through an unrelated channel. Start from your signed-in account area, include the email or phone number attached to your profile, and describe whether you need access, correction or deletion. Our support route can also connect a payment receipt or wallet status question to the right account record.

Team online

Account contact

Use the support contact shown after account access and identify your profile with its registered phone number. We can then locate the relevant Privacy Policy request without asking you to resend a full wallet record.

Wallet record

For DANA, OVO, GoPay or QRIS questions, attach the payment reference rather than your wallet password. This gives us a precise record to check while keeping unnecessary account details out of the request.

Policy request

Tell us whether you want a data copy, a correction, a cookie preference change or removal of eligible records. We will use the account contact path to clarify identity before handling the request.

DATA HANDLING

What Our Privacy Controls Do For You

Privacy controls work alongside the account steps you already know: phone verification before access, a signed-in session on mobile, and a wallet record linked to the selected payment route.

Account data

We may use your registration details, phone verification result and sign-in events to maintain account access and investigate an account request. We do not need a full wallet password to check a payment reference.

Cookies

Cookies can keep your signed-in path active, remember selected settings and help us understand whether a page session worked. Your browser controls can limit cookies, although some account functions may then need another sign-in.

Mobile security

On a phone, session and device signals can help identify unusual account access. If your device changes or a session stalls, contact support from the account path and avoid sharing your password or verification code.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us trace a receipt and status. We use the details needed for that check, not unrelated wallet credentials.

Retention choices

We retain account and transaction records only for the period needed for account operation, dispute handling, security checks or legal duties. A request can ask which records remain and why they are held.

Change requests

You can ask us to access, correct or remove eligible personal data through the signed-in contact path. We may confirm your phone or account details first so another person cannot alter your record.

xr88 Privacy Policy Questions Answered

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data connected with your xr88 profile, local wallet references, cookies, device access and the steps for sending a request.

It covers account registration details, phone verification, sign-in activity, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Use the support contact shown in your signed-in account area and ask for a data copy. Include your registered phone number or email so we can confirm the correct profile.

Yes. Send a correction request through the account contact path and identify the field that needs changing. We may confirm phone verification before updating personal or payment-related records.

Yes. The Privacy Policy covers transaction references and status details connected with QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity, while wallet passwords remain yours.

Your browser may block session or preference cookies, so you might need to sign in again or repeat a page setting. The account contact route remains available for cookie questions.

We use account details, phone verification and session signals to identify the profile and spot unusual access. Never send your password or verification code when asking about the Privacy Policy.

Yes. Account access and eligibility depends on local law. Our Privacy Policy explains data handling for supported access, but it does not override Indonesian requirements or other applicable rules.