Reference

yuan99 Privacy Policy For Your Account

Your yuan99 Privacy Policy access starts with clear answers about account details, wallet records and device activity.

Account dataWallet recordsCookie choicesSecurity steps
yuan99 yuan99 Privacy Policy For Your Account
CONTACT PATHS

Three Ways To Ask About Your Data

A clear contact path helps when you want to understand a Privacy Policy entry or correct an account detail. Start with the support link shown inside your account, especially if a wallet status beside the cashier does not match your receipt. Include your account identifier and the subject of your request, but leave out passwords, wallet PINs and full payment credentials. We use the available account route to check ownership before discussing private records.

Team online

Account support link

Open the support route from your signed-in account when you need a copy, correction or explanation under the yuan99 Privacy Policy. We may ask for account details to confirm that the request comes from you.

Payment status path

For a DANA, OVO, GoPay or QRIS record, use the payment-status path beside the cashier and provide the receipt reference. We compare that reference with the account record without requesting your wallet PIN.

Security concern

If you notice an unfamiliar login or device session, contact us through the account support channel and change your password from account settings. We use the reported time and device details to investigate the session.

SIX DATA CONTROLS

How Six Data Controls Work Here

The policy is designed to connect everyday account actions with a clear data purpose.

Collection purpose

We collect account and phone details to create access, complete the clear phone verification step and respond to account requests. Lobby activity, such as opening Aviator Fast Round, is used only for stated service and security purposes.

Cookie choices

Cookies and similar device signals can keep your session connected, remember selected settings and help identify unusual access. You can manage browser controls, although changing them may affect sign-in or the way policy choices are saved.

Payment matching

A QRIS receipt, DANA reference or bank-transfer code helps us match a transaction with your account. We use the reference and status details for reconciliation, support and security rather than asking for a wallet password.

Account security

We use phone verification, sign-in records and device signals to help protect your account. If your device changes, check account settings and contact support through the signed-in route before sharing any further personal detail.

Retention approach

We retain personal and payment records for the period needed for account operation, security checks, dispute handling and legal duties. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Change requests

You can ask us to correct account data, explain a collection purpose or assess a deletion request through account support. We verify your identity first and explain if a record must remain for security or legal reasons.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the practical questions that arise before you open an account or connect a local wallet. They explain the phone step, device records, cookies, payment references and requests for changes in plain language. If your situation is not covered, use the support route inside your account and describe the specific record or policy point you want us to check.

It covers account details, phone verification, device and browser signals, cookies, lobby activity, payment references and support requests. It also explains why we use each category, how security checks work and how you can ask about correction or removal where local law permits.

We use your phone number for the clear verification step before account access and for account-security checks. It helps us confirm the account owner when a device changes or a support request concerns private records. We do not ask for your wallet PIN.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those details to match receipts, investigate payment status and protect the correct account.

Yes. Use the support link inside your account and state which detail needs correction. We verify that you control the account before changing private data, and we may retain an earlier record when it is needed for security, dispute handling or legal duties.

Cookies can keep a signed-in session active, remember settings and help identify unusual device activity. You can adjust cookie controls in your browser, but some changes may affect access, saved choices or the way account settings appear during a later visit.

We keep payment references for as long as they are needed for transaction matching, account support, security checks, dispute handling and legal duties. The applicable retention period can differ by record type and follows the requirements that apply where local law permits access.

Start with the support channel inside your signed-in account and describe whether you need access, correction, deletion assessment or an explanation. For a wallet question, include the DANA, OVO, GoPay or QRIS receipt reference, never your password or wallet PIN.