Reference

How We Handle Your Account Data

This policy sets out the data we hold when you open an account with bbbangla and pay through bKash, Nagad or Rocket, plus the control you keep over it.

What we collectHow long we keep itCorrection rightsCookie choicesClosing your account
bbbangla How We Handle Your Account Data
REACHING OUR TEAM

Ask Us About Your Data

Privacy requests go into their own queue, apart from game or payment complaints, so a busy cricket night does not push them to the back. Send one from the help form while signed in and it carries your account ID with it, so you never retype a wallet number. You can also open live chat first and simply ask what we hold before filing anything formal. Keep the ticket reference we give you. That is how a correction gets tracked through to the end.

Help form in your account Sign in, open the help section and choose the privacy reason from the list. The form attaches your account ID automatically, so you describe the request once and we route it to the right team.
Live chat from the lobby Prefer to ask first? Chat works well for a quick question about what we hold or how long we keep it. Anything that changes a record still needs the written form.
Email for written requests Write from the address saved on your profile so we can confirm it is you. Include your account ID and any ticket reference, and the reply comes back to that same inbox.
DATA HANDLING PRACTICE

Cookies, Logins and Record Keeping

Your login needs a one-time code sent to the registered mobile number, and we never ask for your bKash, Nagad or Rocket PIN. Anyone who does is not us. Session cookies keep the lobby and the cricket sportsbook working while you move between pages; clear them and you simply sign in again. Records sit on access-controlled systems, with staff seeing only what their role needs. If a change to this policy affects what we hold, we post it in your account and email the address on file before it takes effect.

Sign-in and one-time codes

Every session starts with a code to your registered mobile. A new device or browser triggers another code, which stops a stolen password from turning into a stolen wallet.

Cookies we set

Cookies hold your session, remember your language choice and flag unusual traffic patterns. Clearing them in your browser signs you out, and no wallet PIN is ever written into a cookie.

Retention and deletion

Transaction and verification entries stay for the period local rules require. Once that window closes they are deleted or anonymised, and everything else goes when your account closes.

Changes to this policy

When the text is updated, the new version appears in your account area and we email the address on file before it starts. The date shown on this page always marks the current version.

Questions About Your Privacy

These six questions cover most of what people ask us about this policy: what we hold, who sees it, and how to get it changed. If yours is not here, the help form reaches the same team that answers these. We keep the wording in plain English rather than legal shorthand, because a policy you cannot read is not much use. Anything about access or eligibility still depends on your local law and eligible regions.

Your name, mobile number, date of birth and the wallet number you pay from. We also log device type, IP address and each deposit or withdrawal reference against your account.

No. Your wallet PIN stays inside the bKash, Nagad or Rocket app. We never ask for it in chat, by email or on a call, and no member of our team will request it.

Yes. File the request from the help form while signed in, and we confirm it is you before releasing anything. You get the entries tied to your own account, not the wider database.

Tell us through the help form and attach a document showing the correct spelling. A changed mobile number means a fresh one-time code check before we switch the account over.

Only the wallet operator or bank matching a payment, plus hosting and messaging providers working on our instructions. We also answer lawful requests from authorities where local law requires it.

Yes, ask us to close it. Transaction and verification entries stay for the period local rules set, then go. Anything else is deleted once no open query remains.
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.