Reference

What This Privacy Policy Covers

This page sets out what cxscore records when you open an account, send a bKash or Nagad deposit, and move between live tables and slots. Access depends on your local law and eligible regions, so read it alongside our terms.

Account data onlyWallet records kept maskedCookie choices you controlDeletion on request
cxscore What This Privacy Policy Covers
DATA CONTACT DESK

How to Reach Our Data Team

Every request about your data moves through one channel so nothing gets lost: the support desk inside your account. Open your profile, tap Help, then choose Privacy Request. Our team handles those tickets from Dhaka and Chattogram in the same queue, and the form attaches your account ID automatically, so you will not be asked for it twice. You can also raise the same request through the live chat widget. Keep your ticket number — it is what we quote back when a change is confirmed.

Privacy request ticket Tap Help inside your account and choose Privacy Request. Describe what you need changed, exported or deleted, and the form carries your account ID so we can locate the record without asking twice.
Live chat on this page The chat widget sits on the lobby and on this policy page. Use it for quick cookie or masked-number questions, and the agent opens a formal ticket whenever the answer needs a written record.
Email follow-up If your case needs documents, we send a secure upload link instead of asking for attachments by mail. A screenshot of a Nagad or Rocket receipt is enough for most wallet corrections.
SECURITY PRACTICE

Cookies, Login Safety and Retention

Cookies do two jobs here. Session cookies keep you logged in and remember your language and currency; analytics cookies show us which tables stall on a slow connection. You can refuse that second group from the banner without losing access to the lobby. At sign-in, we send a one-time code to your registered mobile number, and a payout needs a fresh code before money leaves your account wallet — a stolen password alone will not move funds.

Cookie choices you control

The banner on your first visit splits session cookies from analytics ones. Turning analytics off leaves deposits, withdrawals and live tables working exactly as before; only our internal page-speed reporting drops.

Fresh code on every payout

A one-time code goes to your registered mobile number at sign-in and again when you request a withdrawal. If your SIM changes, update the number in account settings before asking for a payout.

How long records stay

Transaction records are held for the period local financial rules require, then deleted. Support transcripts close after a set window and are removed unless they are tied to an open dispute.

Who can see your file

Only the team handling your ticket and the staff who reconcile wallet balances. Access is logged, and any change to your stored phone number or payout wallet is recorded with the date and agent ID.

Questions About Your Data

These are the questions our support desk gets most about this policy, answered the way we would answer them in chat. Nothing here replaces the policy text above — if the two ever seem to disagree, the policy wording wins and we will fix the shorter line. If your case is not covered below, open a privacy ticket from your account and we reply in writing.

Your name, mobile number, date of birth and verified email, plus the wallet records created by a bKash, Nagad or Rocket transfer and the basic device details your phone sends.

Yes for the essential ones — they keep you signed in. You can decline analytics cookies from the banner and still deposit, withdraw and open live tables; only our internal traffic reporting stops.

Open your account, tap Help and choose Privacy Request. We confirm receipt in the ticket, ask for identity proof if needed, and reply in writing once the export or deletion is complete.

Only what a transfer needs: the amount, the reference and the wallet number involved. bKash, Nagad, Rocket and Upay see their own transaction side, not your play history or table activity.

Sign-in access stops and profile details are cleared. Wallet transaction records stay for the period local rules require, then go. You can ask us to remove anything that rule does not cover.

Access depends on your local law and eligible regions. Where a service is not permitted in your area, we do not open an account, and this policy does not apply to that visit.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.