Reference

casino score Privacy Policy: Your Data Path

Our casino score Privacy Policy explains what we collect when you open an account, check DANA or QRIS status, and move between the mobile lobby and account area.

Clear data categoriesWallet activity explainedRequest path includedPolicy access on mobile
casino score casino score Privacy Policy: Your Data Path
HELP WHEN NEEDED

Get Help With a Privacy Request

A privacy question should not get lost beside a wallet query. We keep a support route inside your account area so you can ask about a stored detail, a phone verification record or a payment receipt reference. From a mobile browser, open the account menu, select support, and describe the request in plain English. We may ask for account confirmation before discussing personal records, while access remains subject to local law.

Team online

Account support path

Use the support link after signing in to ask which account details are held or why a verification record is connected to your profile. We will use the account contact route already attached to your request before discussing personal data.

Wallet record check

Include the relevant DANA, OVO, GoPay or QRIS receipt reference when your question concerns a wallet event. A reference helps us locate the matching account entry without requiring you to send a full statement or unrelated transaction history.

Change request

Ask us to correct an outdated phone number, contact detail or account field through support. We may request a fresh account check first, because changing identity-linked data without verification could expose your profile or affect wallet records.

DATA PRACTICES

How We Handle Your Account Data

We separate account, device, payment and support records so each request can be handled with the right context.

Account details

When you create an account, we collect the fields needed to open and maintain access, including your contact details and phone verification status. If you later ask about your record, we compare the request with those account fields before sharing account-specific details.

Payment references

We use transaction references and status details to trace wallet activity through DANA, OVO, GoPay, QRIS, bank transfer or virtual account routes. We do not need a complete bank statement for a normal status question, and we ask you to remove unrelated details before sending a receipt.

Cookies and devices

Cookies can keep a session connected and help us understand whether a sign-in is continuing on the same browser. Your phone or desktop may provide browser type, language and basic connection signals, but our web path does not request access to unrelated device files.

Account security

Phone verification and sign-in checks help us reduce mistaken access to your profile. If a sign-in looks unusual, we may pause a request and ask you to confirm account details. Never send a password, one-time code or full wallet credential through a support message.

Retention approach

We keep records only for the period needed to maintain an account, resolve a support matter, trace a transaction or meet a legal requirement that applies to the service. When a record is no longer needed for those purposes, our process is to remove or de-identify it.

Your privacy contact

For a copy request, correction request or question about deletion, contact us through the signed-in support path and name the record involved. We may confirm your identity, explain any local-law restriction and tell you what action was taken on the request.

Privacy Policy Questions for casino score

These answers address the questions we hear before an account is opened or while a wallet record is being checked. They focus on the casino score Privacy Policy rather than general account features, so you can understand the data path before entering your phone number or payment reference. If your situation is unusual, use the signed-in support route and include only the details needed to locate your request.

It covers account and phone verification details, browser and device signals, support messages, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how to request correction or deletion where local law permits.

Phone verification helps us connect account access with the correct profile and reduce mistaken disclosure during support. It may also be used when you ask about a wallet receipt or request a change to account data. We will not ask you to send your password or one-time code.

Yes. The Privacy Policy covers transaction references and status details that help us match DANA or QRIS activity with your account. It also applies to OVO, GoPay, bank transfer and virtual account references. Send only the receipt details needed for the question, not unrelated account statements.

We may receive basic browser and device signals, such as device type, browser type, language and connection details. These signals help keep a session working and identify unusual access. Our mobile web path does not require access to unrelated photos, files or other apps on your phone.

Sign in, open the account menu, choose support and describe the specific record you want copied or corrected. We may confirm your identity before responding. If a request is restricted because of local law or a transaction need, we will explain the reason and available next step.

We retain account, support and transaction records for as long as needed to operate access, resolve a request, trace an account event or meet an applicable legal requirement. After that period, our process is to remove or de-identify the record, subject to any continuing legal need.

Yes. Contact us through the signed-in support path and ask which cookie or session detail concerns you. Cookies may keep your browser session connected and support security checks. You can also adjust browser cookie settings, although changing them may affect sign-in or policy-page access.