Reference

Explore casinoscores Privacy Policy

Blackjack, Power Hold, Football Strike, Crash X, Bingo and Fishing War sit behind one account, and this Privacy Policy explains how casinoscores handles the data that keeps that…

Account data scopeUPI privacy contextPaytm and PhonePe recordsCookie choices
casinoscores Explore casinoscores Privacy Policy
CONTACT ROUTES

Check privacy contact paths

Privacy support works quickly when your request arrives with enough context and from the email tied to your account.

Email privacy desk Send privacy questions from the email linked to your account so we can confirm the request belongs to you. Include your username, the data topic, and the action you want us to check.
In-account help Use the help area after you open your account when your question involves wallet entries, UPI references, Paytm receipts, cookie choices or profile data. That route keeps the case tied to your account record.
Security alert route If you think someone else has accessed your account, contact us before changing privacy settings. We may freeze risky sessions, ask for ID checks, and explain what personal data may have been viewed.
DATA HANDLING

Browse account data safeguards

Our policy is not only a page to read; it controls how our teams handle account data each day.

Data we collect

Account records may include your name, contact details, login activity, device data, wallet references and chat messages.

Cookie controls

Cookies help keep you signed in, remember language choices and measure page performance.

Account security checks

We use encryption in transit, limited staff access, session checks and audit logs around account data.

Payment record handling

UPI, Paytm, PhonePe and Google Pay references are stored with transaction status, timestamps and anti-fraud checks.

Retention approach

We keep data only as long as needed for account operation, payment checks, dispute handling, security logs and legal duties.

Service partners

We share data with service providers only where they help run hosting, analytics, support, verification or payment processing.

Ask about privacy choices

Privacy questions often come up when you open an account, add a payment method, clear a cookie setting, or ask us to change profile data. The answers below keep to the Privacy Policy itself: what we collect, what you can request, how we verify you, and how law in India may affect access or handling. If you need case-specific help, contact us from your account email so we can match the request safely.

It covers account details, login records, device signals, cookie choices, support chats, game history, and payment references from UPI, Paytm, PhonePe or Google Pay. We explain why each category is needed and how it is handled.

Yes. Send the correction request from your account email or through in-account help. We may ask for proof before changing details, especially when the change affects payments, security checks, identity matching or legal records.

We use payment references to process wallet entries, match UPI or Paytm receipts, investigate failed transfers, handle withdrawal checks and meet record duties. We do not sell payment data to unrelated advertising lists.

Some cookies remember your session, language and consent choices, while analytics cookies help us see whether policy pages work properly. You can manage cookies in your browser, though some account functions may change.

Access is limited to staff and service providers who need it for support, security, verification, payments or legal duties. We log access where practical and check permissions when roles or tools change.

Where local law permits, you can ask for a copy, correction or deletion of account data. Some records may remain for payment disputes, security needs, tax rules or other legal duties.

Yes. Access or eligibility depends on local law and is available where local law permits. Privacy requests remain available through support, but certain account features may differ by state or device.