Sports / Mobile
Every login, deposit and lobby session on 299bf runs under one set of Terms & Conditions, and this page sets out the parts that touch your account day to day. Where you can use the site depends on your local law and eligible regions, so check what your area allows.
These Terms & Conditions are the agreement between you and 299bf, and they apply from the moment you open an account and sign in, whether that is from a phone or a desktop browser. What you can reach depends on your local law and eligible regions, so availability of any part of the lobby, wallet or sportsbook follows the rules where you are, not one global setting. We keep the wording plain on purpose. Where a term names a payment route, we mean the local rails already shown in your wallet, such as bKash and Nagad, and we describe what happens rather than promising outcomes we do not control. Bank and wallet operations sit with those providers, so their own terms run alongside ours. If you travel while signed in, local rules may restrict what you can do, and checking that is on you. We may update these pages when our processes change, and the version live here is the one that applies to your account. Continuing to use the account after an update means you accept the revised text; if you disagree, stop using the site and ask us to close the account. Nothing here removes rights your local consumer law gives you, and nothing here is legal advice for your situation. Read the sections below with your account open, so you can match each rule to what you actually see.
These terms cover what happens on our side of the account. That means the sign-in you complete, the wallet records we keep for your deposits and withdrawals, the lobby content we publish, and how you are expected to behave while you use any of it. What sits outside? Anything a provider runs on its own terms. bKash and Nagad handle the transfer itself and keep their own rules about verification and what their apps allow. Studios such as Microgaming, PG Soft, Pragmatic Play and CQ9 supply the game content on our shelves, so game-level behaviour follows the software they build, and nothing in our terms speaks for them. If your local law restricts online play where you are, those restrictions come first and these pages do not override them. We also do not cover third-party sites you reach through a link outside our lobby, or messages sent from an address that is not one of our published contact routes. The four boxes below split that boundary, so you can tell quickly which set of rules applies to the thing in front of you.
Anything tied to signing in sits inside these terms: your login details, the device you use, session handling, and the profile data you keep up to date. If someone uses your account without your permission, the rules on keeping credentials private apply to you, and we ask you to report it through the published contact route.
Deposits, withdrawals and wallet balances follow these terms as far as our side is concerned. A bKash or Nagad transfer appears as a record in your account wallet, and you can match each entry against the confirmation your provider sends. A dispute about the transfer itself belongs with that provider.
The titles and markets we publish, from Cricket Betflash through to Teen Patti PowerWin, are covered here: how you may use them, what you may copy, and what happens if someone interferes with the software. Any single title can leave the lobby as the catalogue changes.
Studios including Microgaming, PG Soft, Pragmatic Play and CQ9 supply the game content you open, and wallet operators run the money movement. Their own terms apply alongside ours, and we do not control how they run their service or what they decide about it.
You are not stuck with a setting you cannot change. Sign in and open your profile, and you can correct the details we hold — name spelling, contact number, language preference — with the change carrying into your next session. Anything you cannot edit yourself is raised through the published support route. Want the record of a bKash deposit? Your wallet shows every entry with the reference you can match against the confirmation from the provider, which is also how you check a session you do not recognise. If you think a rule has been applied to your account wrongly, write to us with the account detail and the timing, and we will look at what our records show. Asking us to close the account, or to stop using your details for anything beyond running it, is a request you can make at any time. Where your local law gives you a stronger right than these terms, that right stays yours, and we will explain how to use it.
Sign in, open your profile and edit the fields you own: display name, contact number, language. Save the change and it carries into your next session. Anything you cannot edit there, such as a verified wallet number, goes through the published support route so it is handled with you.
Your account wallet lists each deposit and withdrawal with a reference. Match that reference against the confirmation bKash or Nagad sends you. If an entry looks wrong, keep the reference handy when you contact us, because it is the quickest way for us to find the same record.
When a clause is unclear, or you think it has been applied wrongly, send the account detail and the timing through the published route. Tell us what you expected and what you saw. We check our own records and answer on the same channel, so keep that thread for yourself.
You can ask us to update how we hold your account details, or to close the account entirely. Send the request from the contact details on your profile so we can confirm it is you. Closing an account does not cancel a payment a wallet operator is still processing.
Questions about these terms go through the support route we publish in the site navigation, and that is the only place we handle account and policy matters. There is no private phone number to call and no agent who will message you first — if someone contacts you claiming to be from 299bf, treat it as suspect and check with us through the published page. When you write, keep it specific. Tell us the heading you are reading, what your account shows, and what you expected to happen. If a bKash or Nagad transfer sits behind the question, paste the reference your wallet displays, so the record can be found without guesswork. We reply on the same route, which keeps the thread in one place for your own reference. Never send your password, a wallet PIN or a code you received by message. Support can explain how a clause applies to your account and can check our own records, but it cannot change what a wallet operator or a game studio decides under its own rules, and it does not give legal advice about your local situation.
The support link in the site navigation is the route we publish for account and policy questions. Open it while signed in so your account reference travels with the message, and describe what you need in your own words. We answer on the channel you pick there.
Ask about a specific clause and quote the heading you are reading, for example the part on wallet records. That reaches the right place faster than a general message, and it lets us point you to the exact paragraph covering your case rather than a summary of it.
For anything tied to a deposit or withdrawal, include the wallet reference your account shows. The support route is not the place to send a password or a one-time code, and we will not ask you for them through a message. Keep the reference — it does the work.
We hold the smallest set of details the account needs to work. Your name, contact number, wallet reference and the records of what you deposit are kept so the account can be opened, checked and served, and so a transaction can be traced back when you ask us to. Cookies on this site do the ordinary jobs: keeping you signed in between pages, remembering your display choice on a small screen, and showing us where a page loses people. We do not treat a policy question as a reason to collect more. Account security sits largely with you, in a good way — the password you choose, the device you sign in from, and signing out when you hand the phone to someone else. Keep your bKash and Nagad PINs out of anything you send us. If you want to know what we hold, or you want a correction or a removal where your local law allows it, that is a request you can make through the published support route, and we answer it in writing.
Account details, wallet references and transaction records. We keep them because a deposit you made last month still has to be visible to you this month, and because a query about a payment cannot be answered from memory. We do not sell that data on.
The cookie set keeps you signed in as you move between the lobby and your wallet, holds your display choices, and shows us which sections people actually open on a phone. You can clear them in your browser at any time; parts of the signed-in area then need a fresh login.
Your password and wallet PIN belong to you alone. Sign out on shared phones, and check your profile if a device was not yours. Anything unfamiliar in your wallet history should be reported through the published support route with the reference number attached to it.
Records tied to deposits and withdrawals stay as long as local rules require them, then we remove what is no longer needed. Ask us what we hold, how long we keep it, or for a correction, and we answer that request in writing through the same support route.
Most of the messages we get about these terms come from people who spotted something in their wallet and could not tell whether it was our rule or their provider's. Fair question. Above, you can see who owns which part of the process. The answers below handle the rest: whether opening an account is what accepts the terms, what you can edit yourself, who to write to when a rule looks wrongly applied, and what happens to the details we hold when you ask us to remove them. Read them with your account open on the same device, so each answer can be matched to what you see on screen. If your situation is still not covered, the published support route is open, and a specific question with a wallet reference will always get a clearer reply than a general one.
Yes. Opening the account and signing in means the wording on this page covers what you do here, from the login itself to wallet records and lobby behaviour. If your local law restricts online play where you are, that restriction applies first, and eligible regions decide what is actually available.
The section above on how we apply these terms, and the wallet area in your signed-in account, are the two places to look. The terms explain our side of the process; the wallet shows the bKash or Nagad reference you can match against the confirmation from your provider.
Sign in and open your profile. Name spelling, contact number and language preference can be edited there and saved straight away. A verified wallet number, or anything you cannot change yourself, goes through the published support route, where we confirm it is you before anything moves.
Use the support route published in the site navigation, and keep the message specific: the heading you are reading, what your account showed, and when you saw it. We check our own records and reply on the same channel, so your thread stays in one place.
No, and that boundary matters. Studios such as Microgaming, PG Soft, Pragmatic Play and CQ9 supply the game content you open, while wallet operators run the transfers. Their own terms sit alongside ours, so a question about a transfer is handled by that provider while we answer for our records.
When our processes change, the wording here changes with them, and the version on this page is the one covering your account. Keep signing in after an update and you are accepting the revised text; if you do not accept it, stop using the site and ask us to close the account.
Send the request through the published support route, from the contact details on your profile, so we can confirm it is you. Closing the account stops your access to the lobby and wallet. Where local law gives you rights over your own data, say what you want and we handle it in writing.