Reference

Privacy Policy for Your cristal89 Account

Our Privacy Policy explains how cristal89 handles the details connected with your account, including phone verification, wallet choices and device access.

Account dataWallet recordsCookie choicesAccess requests
cristal89 Privacy Policy for Your cristal89 Account
CONTACT PATHS READY

Where To Ask About Privacy Policy

A clear contact path helps you ask what we hold, why we use it or how to correct an account detail. Start from the support route linked to your cristal89 account and include the phone number or transaction reference connected with your request. We will use the available account record to locate the matter, while avoiding unnecessary details in your message. This route also works when a cookie choice, device sign-in or wallet status needs a privacy explanation.

Team online

Account access

Ask about phone verification, sign-in records or a device that no longer appears familiar. Include your account phone number and the approximate sign-in time so we can check the relevant access event without asking you to send a password.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the transaction reference rather than a wallet password or full secret. We can explain which payment record is stored and why a matching check may be needed.

Policy questions

Use our account help path for a copy request, correction request or question about cookies and retention. Mention the exact Privacy Policy topic you are asking about, and we will keep the response tied to your account and the applicable local rules.

SIX HANDLING PROMISES

What Our Privacy Process Covers

We keep the Privacy Policy practical by connecting each rule to an account action you can recognise.

Collected account data

We may handle your name or account identifier, phone number, verification result, sign-in events and selected settings. These records help us provide account access, connect a support request to the right account and identify changes that need your confirmation.

Wallet and payment data

DANA, OVO, GoPay and QRIS activity can create references, status results and timing records. Bank transfer and virtual account checks may also create matching data. We use these records to trace a requested transaction, not to request your private wallet password.

Cookies and device signals

Cookies can remember a selected setting or help maintain a sign-in session. Device and browser signals can show whether an access attempt differs from your usual path. You can ask support how a cookie or device record relates to your account.

Account security

Phone verification is an account step before access, and sign-in events can be checked when a device looks unfamiliar. Keep your password and wallet credentials private. Our support route will not require those secrets to assess a Privacy Policy request.

Retention decisions

We retain account, security and transaction records only for the period needed for the stated service, account protection, dispute handling or a legal requirement that applies to the request. Ask us which category a record belongs to before requesting a change.

Changes and corrections

You can ask us to correct an inaccurate account detail, explain a data use or describe the record linked to your request. We may verify account ownership through the phone path before making a change, so another person cannot alter your account data.

Privacy Policy Questions About cristal89

These Privacy Policy answers focus on the account actions you are most likely to check before opening access. We explain what may be collected, how wallet and device records fit into the process, and how to ask for a correction or copy. The same rules apply across mobile and desktop access, subject to local law and the account path available to you.

It covers data connected with your account, phone verification, sign-in activity, device signals, cookies, support messages and payment references. That can include DANA, OVO, GoPay, QRIS, bank transfer and virtual account status records when you use those routes.

Phone verification helps connect account access with the right account and lets us examine an unusual sign-in. We store the verification result and related access event as needed for account security. Access depends on local law and applies where local law permits.

Yes. The policy includes payment references and status data created when you use DANA or QRIS, along with OVO, GoPay, bank transfer or virtual account routes. We use these records to match and explain a transaction, not to collect your wallet password.

Cookies may keep a session active or remember a selected setting on your phone browser. Device signals may help us compare a new sign-in with earlier access. The Privacy Policy applies when you move from mobile login to the lobby, and you can ask about a specific cookie record.

You can contact our account help path and request the data categories connected with your account. Include your account phone number and the subject of your request. We may verify ownership first, then explain what can be supplied under the local rules that apply.

Send a correction request through the support route linked to your account and identify the field that is wrong. Do not include your password or private wallet credentials. We may use phone verification to confirm ownership before changing the relevant account record.

Retention depends on the type of record and whether it is needed for account security, transaction matching, dispute handling or a legal requirement. Ask us about the category you are concerned about, and we will explain the applicable period or reason where local law permits.