Reference

What Our Privacy Policy Covers

This page sets out exactly what betbat records when you open an account, sign in from your phone and clear a deposit through bKash, Nagad or Rocket.

Account recordsCookie controlsAccess requestsDeletion path

Explore the Lobby Read FAQ

Which Details We Hold And Why

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

When you open a wallet with us, we collect the basics needed to run it: the mobile number you register with, your name as it appears on your bKash, Nagad or Rocket account, your date of birth, and the region you sign in from. Each deposit,

1
withdrawal and settled wager — including a cricket bet placed ahead of a BPL fixture — stays in one history so a disputed transfer can be traced back to the wallet reference. Your device sends the usual technical signals: browser type, IP address, handset model. We
2
log those to flag logins that do not match your normal pattern. We do not ask for more than the payment rails need. A bKash transfer has to come from a wallet in your own name so we can match the sender number to your account.
3
Nagad and Rocket follow the same rule, and Upay or Bank Transfer work the same way when they are available in your region. Cookie data does two jobs here: keeping you signed in between visits on the same handset, and measuring which lobby pages load slowly
4
so we can fix them. Advertising cookies are a separate set, and refusing them costs you nothing. Eligibility, verification steps and the records we have to retain depend on your local law and eligible regions, so what applies to your account here in Bangladesh can differ
5
from another country. Where those rules change, we update this page rather than send a buried email.

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

SECURITY AND STORAGE

How We Store And Protect Records

Records sit on servers we control, and access is limited to the staff who need them to verify a transfer or answer your request. Passwords are stored hashed, so nobody here can read yours. Session cookies keep your phone signed in until you log out or the session expires. Anything the payment rails no longer need gets removed on a rolling schedule rather than held forever. What local rules require us to keep stays, and we tell you exactly which records those are when you ask.

Account security

Your password is stored in hashed form, and a login from a new handset triggers a one-time code to your registered mobile number before the session opens.

Cookie choices

Sign-in and page-speed cookies run by default because the lobby needs them. The advertising set is optional and you can switch it off without losing access.

Retention window

Wallet and transfer references are kept only as long as the payment rails and local rules require, then cleared on a rolling schedule instead of sitting there indefinitely.

Your rights

Ask for a copy, a correction or deletion of your records by messaging support inside the account. We confirm what changed, and what has to stay on file.

ASK US DIRECTLY

Where To Send A Data Request

One desk handles everything privacy-related. Message support from the chat inside your account, or write to the address on our contact page. Both routes reach the same team. Tell us what you need — a copy of your records, a correction, or closure of the wallet — and include your registered mobile number so the request can be matched to the right account. We reply to the number or email you signed up with, never to a fresh inbox you have just created.

Privacy Questions We Get Asked

Most messages we get come down to the same handful of things: whether we sell data, how long a closed wallet stays on file, and what happens when you ask for a copy of your records. The answers below cover those. If yours is not here, message support from inside your account and we will take it from there.

No. We share a transfer reference with bKash, Nagad or Rocket only to settle or reverse a payment, and with providers hosting parts of the lobby under a contract that limits their use.

Message support from your signed-in account and ask for a copy. We send it to your registered mobile number or email once your identity is matched, with no charge for the first request.

Yes. Ask us to close the wallet. We erase what we are not required to retain; transfer records tied to bKash, Nagad or Rocket payments stay for the period local rules set.

Log out at the end of each session and skip the keep-me-signed-in option. Session cookies on a shared handset can reopen your wallet, so clear the browser too if you passed the phone on.

Only if you accept them. Sign-in and page-speed cookies run by default because the lobby needs them; the advertising set is optional and can be turned off without losing access.

That depends on your local law and eligible regions. Wherever you sign in from, we follow the retention rules that apply there and update this page when those rules change.

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.

InfoLegal InfoBetbat Banking InfoBaccarat Lantern

What Our Privacy Policy Covers

How We Store And Protect Records

Account security

Cookie choices

Retention window

Your rights

Where To Send A Data Request

Privacy Questions We Get Asked

01 Do you sell my details to other companies?

02 How do I get a copy of the data you hold on me?

03 Can I close my account and have my details removed?

04 What happens if I sign in from a shared phone?

05 Do you use cookies for advertising?

06 Which laws decide what you must keep?

Privacy Policy

Related pages

Related pages