Reference

rexus88 Privacy Policy For Your Account

rexus88 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet checks and lobby access.

Account dataWallet recordsCookie choicesAccess depends on local law
rexus88 rexus88 Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Help Beside The Account Path

A clear contact route helps you resolve a privacy question without repeating your account story.

Account privacy request Use the on-site support channel for a copy, correction or removal request. Include your registered contact detail so we can confirm which account record you mean before responding.
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the date and reference code through support. We use those details to locate the matching transaction record.
Access concern For an unexpected login or device change, contact us through the account support path and change your password from the account screen. Never send a password, PIN or verification code.
YOUR DATA CONTROLS

What We Do With Account Records

We separate everyday account operations from privacy requests so each question reaches the right handling step.

Collection at account opening

We collect the contact and verification details needed to create your account and confirm access. You can check the entered details before completing the account step.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us reconcile account activity. We do not need your wallet PIN or banking password for that check.

Cookies and device memory

Cookies can keep a session active or remember a device setting. Browser controls let you clear them, although clearing session cookies may require another account login.

Account security

We use login records, phone verification and device signals to identify unusual access. If a sign-in looks unfamiliar, contact support and update your password from your account path.

Retention period

We retain account, payment and support records while they serve account operation, dispute handling or legal needs. When no valid purpose remains, we remove or anonymise them.

Your requested changes

You may ask us to access, correct or delete eligible personal data. Send the request through support with enough account detail for identity checking, without sharing secret credentials.

Privacy Policy Answers For rexus88

These Privacy Policy answers address the account questions we expect before you open access. They cover payment records, device use, cookies, correction requests and the route to reach us. If your situation is not listed, send the request through support with your registered contact detail and we will assess it under the same policy.

The Privacy Policy covers account details, phone verification, device and login records, cookies, payment references, support messages, retention and requests to access, correct or delete eligible data.

We keep transaction references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use so we can match receipts, investigate status questions and protect the correct account.

Yes. Send a correction request through the account support channel with your registered contact detail and the specific field. We may verify your identity before changing the account record.

Cookies can retain a login session or device preference. You can clear or block them in your browser settings, but doing so may end the session and require account access again.

We retain data while it supports account operation, payment reconciliation, dispute handling, security or legal needs. After that purpose ends, we remove or anonymise the relevant record.

Use our support path and state that you want eligible personal data deleted. Include your registered contact detail, but do not send your password, wallet PIN or phone verification code.

Payment processing may require relevant transaction details to move through DANA, OVO, GoPay, QRIS, a bank transfer or virtual account. We share only what the payment step requires.