Reference

Open crazyrich88 With Privacy Clarity

Our Privacy Policy explains what we collect when you open a crazyrich88 account, why we use it, and how you can ask about your records.

Clear data purposesPhone verification contextIndonesia access wordingPolicy request path
crazyrich88 Open crazyrich88 With Privacy Clarity
REQUEST SUPPORT

Switch To The Right Privacy Contact

A clear contact route helps you ask about the Privacy Policy without sending account data to the wrong place. Start with the support path linked to your account so we can match your request to the correct profile and payment record. We may ask you to confirm your registered phone before discussing private details. Keep your request specific, such as access, correction, deletion, cookies or a DANA receipt. Our team can explain the next step for supported Indonesia accounts.

Team online

Account privacy request

Use the account support path to ask what personal details we hold, why they are used, or how to request a copy. We will verify the registered phone before discussing account-specific records.

Wallet record question

If a DANA, OVO, GoPay or QRIS receipt appears incorrect, include the transaction reference and date through support. We use those details to locate the relevant payment record without requesting your wallet password.

Access and correction

For a name, phone or account detail correction, tell us which field needs attention and why. We may request an account step to confirm ownership before changing or disclosing private data.

DATA PRACTICES

Explore How We Handle Your Data

Privacy work follows the same account path you use to reach the lobby: we identify the account, check the requested record and limit the response to the stated purpose.

Account details

We use your registered details to create and maintain account access, respond to account requests and connect support conversations to the right profile. Phone verification helps us avoid disclosing private records to another person.

Device sessions

When you switch from a phone to desktop, session data helps us recognise an active login and protect the account flow. Sign out on a shared device and contact support if a session looks unfamiliar.

Cookies

Cookies can remember a session, preserve selected settings and help us understand whether a policy page loads correctly. You can manage cookies through your browser, although some account functions may then need another login.

Account security

We use phone verification and account checks before handling sensitive requests. Never send a password or wallet PIN to support. If your phone number changes, complete the account check before asking us to update it.

Record retention

We retain account, payment and support records only for the operational, dispute or legal purpose that requires them. A QRIS or bank transfer reference may remain while a status question or reconciliation request is still open.

Policy changes

If we change this Privacy Policy, we will place the revised wording on the policy page and show the effective date. You can ask support to clarify a change before continuing with your account.

Browse Privacy Policy Answers

These Privacy Policy answers cover the account questions we expect before access begins. They explain how we connect personal details with payment records, what happens on different devices and how to contact us about a change. If your request concerns a specific account, use the support path rather than placing private details in a public message. Access depends on local law.

The Privacy Policy covers account details, phone verification, device sessions, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can ask for access, correction or deletion where local law permits.

We use your phone number to create account access, complete phone verification and connect a privacy request to the correct profile. If you ask about a DANA, OVO, GoPay or QRIS record, confirmation helps us avoid sharing private details with another person.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to check receipt status, reconcile an account question and handle disputes, not to request your wallet password or PIN.

Use the account support path and state that you are making a privacy access request. Tell us the registered phone and the record category you need, such as profile, device or payment history. We may complete an ownership check before releasing account-specific data.

Yes. Send the field that needs correction, the accurate replacement and a short reason through support. We may verify your registered phone before making the change. A correction request does not automatically remove payment or legal records that we still need to retain.

Ask support for a deletion request and identify the account by its registered phone. We will assess the request under applicable law and explain what can be removed. Some account, payment or dispute records may remain when retention is required for a stated purpose.

Yes. The Privacy Policy applies when you access the account from a mobile browser or desktop session. Cookies and session records may differ by device, so sign out from shared equipment and tell support if an unfamiliar device appears in your account path.