Reference

Open the Policy That Covers Your Account

Opening an account with 2999bat means we hold a small, defined set of details — your mobile number, your wallet reference and your login record — and this page sets out exactly what we keep, why a bKash or Nagad transaction reference matters, and…

Wallet PIN never requestedNew-device sign-in checkCopy of your data on requestAccount closure honoured
2999bat Open the Policy That Covers Your Account
DATA HANDLING STEPS

See How 2999bat Holds Your Details

Four habits carry most of this. We hold the least we can, tie every record to a wallet you control, keep device sessions visible to you, and delete on a schedule instead of forever. That is why we never ask for your bKash or Nagad PIN, why a new handset triggers a check on your registered number, and why a closed account no longer receives messages. Cookies stay narrow: session state, your language choice, and the last screen you opened — a slot room, a live table, or the cricket markets on our sportsbook.

Least-data approach

We collect the mobile number, the wallet name, the transfer reference and the login record. Nothing further is needed to run your account, and we do not sell the set to anyone.

Cookie scope

Session cookies keep you signed in on your phone. Preference cookies remember your language and your last screen. Clear them in browser settings and you simply sign in again, with no account data lost.

Device and session checks

A sign-in from an unfamiliar handset raises a check on your registered number. If our record of a bKash, Nagad or Rocket transfer does not line up, we hold the account until you confirm.

Retention window

Records stay while your account is open, plus the stretch afterwards that local rules and payment providers require. Ask us to close the account and the deletion clock starts from that confirmation.

ONE HELP CHANNEL

Ask Us for Your Data Copy

Questions about this policy go to the same team that handles account access, so you only need one thread. Message us from inside your signed-in account and the request carries your account ID with it — no copy-pasting of wallet references. If you cannot sign in, use the chat on the login screen and give the mobile number registered with us. We reply in English and in the order requests arrive. Ask for a data copy, a correction, a device unbind or a full closure; each request gets a written outcome you can keep.

In-account message Signed in? Open the help panel in your account and send the request there. Your account ID, wallet number and last sign-in travel with it, so we skip the back-and-forth.
Login-screen chat Locked out but still need the policy explained or a handset unbound? The chat on the sign-in screen takes your registered mobile number and passes it to the same account team.
Written request Prefer writing it out in full? Send your request from the mobile number on the account and attach a screenshot of the bKash or Nagad message if it makes the case clearer.

Browse the Questions We Get Most

These come up every time someone opens this policy page, so we answered them the short way. If yours is about one transfer in particular, mention the wallet and the reference number when you write in — bKash, Nagad and Rocket messages each carry a different format, and that detail saves a round trip. Anything not settled here goes to the same account-help channel described above.

Your mobile number, the name registered on your wallet, the reference numbers from your bKash, Nagad or Rocket transfers, and your login record — device, time, and the last screen you opened.

No. A PIN stays inside your bKash, Nagad or Rocket app. We match transfers using the reference number and the notification you receive. Anyone asking for your PIN in our name is not us — report it to account help.

Write from the mobile number registered on the account, either inside the signed-in help panel or through the sign-in chat. We confirm the request, then send a written copy back to that same number.

Yes. Ask inside the account and we close it once any open transfer is settled. Payment records stay for the stretch local rules and wallet providers require, then they are deleted.

Only what a payment rail or a game studio needs to settle a transfer or load a title, plus anything a lawful request requires. We do not hand your mobile number to advertisers.

It describes how we handle data across our own site and app. The law where you are may add rights or limits, and access to 2999bat depends on your local law and eligible regions.
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.