Reference

crs999 Privacy Policy For Your Account

crs999 Privacy Policy sets out what we collect, why we use it and how you can ask about your account data before opening the lobby.

Clear data purposesWallet record contextAccount access choicesIndonesia policy scope
crs999 crs999 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Privacy Through Account Support

A clear contact path helps when you want to ask about the Privacy Policy, check a data record or request an account change. Start from the support route connected to your account and include the phone number or account detail needed to locate your request. For a wallet question, include the relevant DANA, OVO, GoPay or QRIS receipt reference without sending your full wallet password or sign-in code.

Team online

Policy question

Use the account support route to ask which data we hold, why a field is needed or which part of the Privacy Policy applies to your request. We may ask for an account detail so we do not disclose data to the wrong person.

Wallet record check

If your request concerns a DANA, OVO, GoPay or QRIS record, share the transaction reference and date through account support. We use those details to locate the relevant entry while avoiding requests for your wallet password or one-time sign-in code.

Change request

Ask us through the same account support path to correct an account field, explain a retention period or request removal where applicable. We assess the request against account safety, legal duties and the access rules stated in this Privacy Policy.

DATA PRACTICE

Six Privacy Checks Behind Your Login

We keep the Privacy Policy practical by linking each data practice to an account action you can recognise.

Account details

When you open an account, we use the details you submit to create and maintain that account. A phone number can be used for verification before access. We do not need unrelated profile details to explain the Privacy Policy or answer a data request.

Device signals

A sign-in from your phone, tablet or desktop can create a record of device type, browser setting and access time. These signals help us compare account activity and protect your login; they are not a view into unrelated files or applications.

Cookie choices

Cookies can keep a session active, remember a language or preserve a selected page setting. Your browser controls can remove or restrict them, although a stricter setting may require another login when you return to the account.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a reference, amount and status record. We use that record to match the account action and receipt, not to collect your wallet password.

Account protection

Phone verification and sign-in checks help us respond when account access looks unusual. Keep your password and verification code private. If you notice a device or account action you do not recognise, contact account support promptly.

Retention requests

We keep personal data for the period needed for the purpose described in this policy, account safety or a legal requirement. You can ask why a record remains, request a correction or ask whether removal is available for your specific account.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we hear before an account is opened or a wallet is connected. You can use them to understand phone verification, cookies, payment records, device activity and requests for changes. If your question concerns a particular account entry, the support route can help us locate it using the relevant account or receipt reference.

The crs999 Privacy Policy covers data created when you open an account, verify a phone, sign in, use cookies, contact support or request a payment through DANA, OVO, GoPay, QRIS, bank transfer or virtual account. It also explains retention, protection and requests for changes.

Phone verification connects the account to a contact detail before access and helps us respond to unusual sign-in activity. We use the verification result for account protection and access checks. Availability depends on local law and applies where local law permits.

Yes. The Privacy Policy covers account-linked records for DANA, QRIS, OVO, GoPay, bank transfer and virtual account requests. These may include a reference, amount, status and time needed to match a receipt. We do not ask for your wallet password.

We may record device type, browser setting, approximate access details and sign-in time when you use a phone, tablet or desktop. This supports account protection and session handling. It does not give us access to unrelated files, contacts or applications on your device.

You can contact account support and ask us to correct an account field or explain a record. Include the account detail needed to locate your request, but never send a password or one-time code. We assess the request under this Privacy Policy and applicable local law.

We retain account, access and payment records for the period needed for the stated service purpose, account protection or a legal requirement. The exact period can depend on the record. Ask through account support if you need the retention reason for a particular entry.

Use the account support path linked to your account and describe whether your request concerns access, correction, removal, cookies or a wallet record. For a DANA, OVO, GoPay or QRIS question, add the receipt reference and date so we can identify the correct record.