Mobile / App
This is where bbt99 sets out the rules that sit over your account, your bKash or Upay movements and the way we handle your details. Whether you can open an account or use a given wallet route depends on your local law and the regions we are able to serve.
bbt99 operates under the terms published on this page, and those terms apply from the moment you open an account. Nothing here is a promise we cannot keep: we describe the rules we follow, the records we keep and the choices you have. Availability is not uniform, so whether you can use a given payment route or reach the lobby from where you sit depends on your local law and on the regions we are able to serve. We keep account rules separate from payment rules because different parts of the system handle them. Your sign-in details protect the account door. Your transaction records show what moved and when. Site content, including games, tables and cricket markets, sits behind both. When something goes wrong on a wallet transfer, the first place to look is the record attached to that transfer, not the game page. Because the legal picture differs by country, we do not claim here that access is permitted everywhere. We publish what we can stand behind: the terms you agree to at sign-up, the records those terms generate, and the routes you can use to raise a question. If a route is not open to you, the account area shows what is available rather than leaving you to guess. Read this page alongside the terms shown at sign-up. If the two ever disagree on a point, the version attached to your account at the time you agreed to it takes priority.
The policy on this page reaches the parts of bbt99 you actually touch: the account you open, the wallet transfers attached to it and the content we publish. It does not reach outward into systems we do not run. A wallet app on your phone answers to whoever operates it, and those rules apply to you separately from ours. The same holds for your bank, your mobile operator and the browser or app store on your device. Inside our own walls the line is simple. Games in our lobby, the table rooms and our cricket-led sportsbook fall under these terms, because we publish them. Titles supplied to us by the studios listed on the lobby sit under the same policy while they are live here. Anything you reach through an outside link does not. When a query touches two sides at once, such as a transfer that left your wallet but has not landed on your account, expect us to read our own record and point you to the other operator for the rest.
Opening the account, signing in and keeping your details current all sit under this policy. So does the way we handle a locked or inactive sign-in. If you cannot get in, the recovery path shown on the sign-in screen is part of the terms you agreed to.
Every wallet movement you make, whether a bKash deposit, an Upay transfer or a cash-out request, creates an entry attached to your account. That entry is governed by this policy and by the terms shown when you sent it. Amount questions are handled from it.
Games in our lobby, the table rooms and our cricket-led sportsbook are ours to publish, so they fall inside this policy. Titles we carry from the studios named on the lobby are made available to us for that lobby and sit under the same terms while they run.
Your wallet app, your bank and your mobile operator each run their own rules, and those services sit outside this policy. We can show you what our side recorded about a transfer. We cannot decide anything inside another operator's system, and we will say so plainly.
You are not stuck with whatever state your account happens to be in. This policy gives you practical moves, and the account area is where you make most of them. Start with your profile. If a name, mobile number or address detail does not match the document behind it, correct it before a transfer needs to clear against it. Then read your records. Every bKash or Upay movement leaves an entry with a date and a state, and checking those entries is usually faster than asking us what happened. If something still does not add up, raise it through the support route published on this site and quote the reference printed on the entry. You can also ask what details we hold about you, ask for a copy, or ask us to fix something inaccurate. Those requests need no reason beyond the request itself, and we answer them through the same published route so the exchange stays on your account.
Open your account area and read the transaction list. Each entry shows what moved, when it was sent and the state it holds now. Comparing your wallet app history against that list is the quickest way to spot an entry that needs a question.
Keep the name, mobile number and email on your account matching what you actually use. When something changes, update it from the profile screen instead of opening a second account, because two accounts for one person create avoidable problems at payout time.
If an entry looks wrong or a game round does not settle as expected, send the reference and a short description through the support route published here. Guessing at the cause wastes a turn, while the reference lets us open the actual record and answer it.
You can ask what personal details we hold, request a copy of them, or ask us to correct anything inaccurate. Send that request through the same published route so it is logged against your account and answered in writing rather than in passing.
Questions about this policy reach us through the routes already published on the site, and we would rather you use those than a channel you picked up somewhere else. Sign in before you send anything. A message carrying your account reference is far easier to act on than one arriving without it. If your query concerns a wallet movement, open that entry first and quote the reference printed on it. If it concerns the wording of this policy, copy the line you are asking about so we read the same sentence you did. Nobody from us will ask for your password or for any code sent to your phone, and no route we publish needs either one. Treat any message that asks for them as fraudulent and report it to us. When you follow up, stay in the same thread. A written trail shows what you asked and what we answered, which matters if the same entry comes up again later.
Sign in and use the contact route shown inside your account. It carries your account reference automatically, which means a question about a bKash deposit arrives attached to the transfer it concerns rather than as a loose message we have to trace back to you.
The public route on this site covers questions you can ask before signing in, including how this policy treats your details. Use it for terms wording, data requests and anything that does not need your transaction list open in front of you.
Keep your query in writing and reply in the same thread. A written trail shows what you raised and what we answered, which helps if the entry is examined again. Attach the transaction reference rather than retyping an amount from memory.
Your details sit on our side for a small number of reasons: to run the account, to attach wallet movements to the right person and to answer you when you ask. We use them for those jobs and not for anything else. Cookies do a narrower task than people assume. They keep you signed in between pages and remember basic display choices on your device. Clearing browser data signs you out and resets those choices, which is expected behaviour rather than a fault. Account security is shared work. The sign-in sits with us, the password sits with you, and it should never travel to anyone who contacts you first. Records stay while the account is open and for as long as a transaction or a rule requires them, after which they are cleared. If you want to know what we hold, want a copy or want a correction, write through the published route and we answer in writing.
Account details you enter, the transaction entries your wallet movements create, and the messages you send us. We use them to run the account and answer your questions, and we do not hand your personal details to outside parties for their own purposes.
Cookies keep your session alive between pages and remember display settings on the device you are using. They are not a profile of you. Clearing browser data on a phone signs you out and resets those settings, and you simply sign in again.
Your password protects the account door, so keep it to yourself. We never request it in a message, and no route we publish asks for it. Treat any message that does as a fraud attempt and report it to us through the site.
Records stay while the account is open and for as long as a transaction or a rule needs them, then they are cleared. You can ask what we hold, request a copy or ask for a correction by writing through the published route.
Most legal questions about an account come down to three things: what we owe you, what you can do, and where to ask. The answers below cover that ground first, then a few points that come up when a wallet transfer or a region restriction is involved. If your situation is unusual, say a number registered in someone else's name or a mobile operator you have changed, the general answer may not fit and the published support route is the place to take it. We would rather answer a specific question properly than have you rely on a line written for the common case. Nothing on this page replaces the terms you accepted when you opened the account, and access always depends on your local law and the regions we are able to serve.
The wallet routes shown at deposit depend on your region and on your local law, so the list can differ from one person to the next. Open the deposit screen in your account and it will show which routes are live for you, including whether bKash appears there today.
Your account area keeps a transaction list. Each entry shows what moved, when it was sent and the state it holds now. Compare that against your wallet app history. The two should line up, and any gap is worth a question with the reference attached.
No. The account has to be yours, with your own details and your own sign-in. Two accounts for one person, or an account fronted by somebody else, breaks these terms and creates trouble at the point where a transfer has to match a name.
Write through the support route published on this site and say what you want: a copy, a correction, or a short note of what we hold. We answer in writing and tie the reply to the account the request came from, so the exchange stays traceable.
Yes. The same terms cover the site whether you reach it from a phone browser or a desktop. What changes is the layout, not the rules. The account area behaves the same way once you have signed in on either device.
Then it belongs with the wallet operator, whose rules sit outside this policy. We can show you what our side recorded about the transfer, but we cannot decide anything inside another provider's system. Raise it with them using the same reference.