Reference

How CX BD Protects Your Account Data

This page explains what account, wallet and device data CX BD collects the moment you log in, top up through bKash, Nagad or Rocket, or switch between the sportsbook and slot rooms.

Account & Wallet DataPayment RecordsDevice & Login LogsRegion-Based Access
CX BD How CX BD Protects Your Account Data
REACH OUR TEAM

Contact Paths For Privacy Questions

If anything in this policy needs clearing up — how we store your bKash transaction history, why we ask for ID during wallet verification, or how long login logs sit on file — you can raise it directly instead of guessing. We keep support channels open for account and privacy questions the same way we do for payment issues, so a message about your data gets the same attention as a stuck deposit. Have your registered phone number ready; it speeds up how quickly our team can locate your account record.

Live Chat Message our support desk from inside your account for anything related to how your data is stored, used or shared, including bKash or Nagad transaction records tied to your profile.
Email Support Send a written request if you want a copy of the personal or payment data CX BD holds against your account, and we'll route it to the right team.
In-App Help Open the help section from the app or mobile browser menu to ask about login logs, device data or wallet verification records without leaving your session.
HOW WE HANDLE DATA

Cookies, Retention And Account Security

Session cookies and app tokens keep your login active between visits so you don't retype your phone number every time you switch from the browser to the app shortcut. We hold payment records — your bKash, Nagad and Rocket references — for as long as reconciliation and local record-keeping rules require, then they age out of active systems. Account security checks, including the OTP step at login, exist to stop someone else from opening your wallet. Want a data correction or deletion request logged? Contact support with your registered number and we'll confirm the next step.

Cookies & Sessions Cookies and app session tokens keep you signed in across visits so switching between the mobile browser and the app doesn't force a fresh login every time.
Payment Record Retention Deposit and withdrawal references from bKash, Nagad or Rocket stay on file long enough to reconcile disputed transfers and meet local record-keeping requirements before they're archived.
Account Security Checks Every login runs through an OTP step tied to your registered phone number, which keeps your account wallet and payment history away from anyone but you.
Requesting Changes If you want your data corrected, exported or removed, reach out through support with your account phone number and we'll confirm what happens next and when.

Common Questions About This Policy

Here are the questions we hear most often about how CX BD handles account, payment and device data, from what gets stored during a bKash or Nagad transfer to how you can ask for a change. If your question isn't covered here, our support team can walk through the specifics of your own account record.

We collect your phone number, wallet identifiers linked to bKash, Nagad or Rocket, and any ID you submit for wallet verification, along with basic device and login details for account security.

Your payment records stay within CX BD and the processors needed to complete a bKash, Nagad or Rocket transfer; we don't sell wallet or personal data to outside marketers.

Login and device logs sit on file long enough to review account security issues and meet local record-keeping rules, then they're cleared from active systems on a routine schedule.

Yes — contact support with your registered phone number, tell us what needs correcting or removing, and our team will confirm the next step for your account.

Yes — whether you log in through the app shortcut or a mobile browser tab, the same account, cookie and session rules in this policy apply to both.

Availability and how we process your data can depend on your local law and eligible region, so some account or payment features may differ depending on where you're accessing from.
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.