Casino / Sports
ab08 keeps one clear set of legal terms, and they cover your account, the bKash and Bank Transfer routes you connect to your wallet, and the way you use the lobby. Whether a route or a game category is open to you depends on your local law and eligible regions, so read the terms that apply to you before you start.
This page is where we put the legal position into plain words. Our notice explains what you agree to when you open an account with ab08, what we expect from you while you use the lobby, and what you can expect from us in return. It covers registration details, the way wallet activity is recorded, how a dispute is raised, and how changes to these terms are published. Deposits made through bKash and Bank Transfer sit inside the same framework, so the terms that cover your account also cover the payment routes you connect to it. Because availability of any route or game category depends on your local law and eligible regions, some clauses may not apply to you in the same way they apply to someone elsewhere. We do not promise a fixed outcome for any dispute, and we do not list a licence authority here. Instead we point you to the sections that describe your obligations, our obligations, and the steps you take when something looks wrong on your account. Read the notice once when you register, then come back to it whenever your registered details, your payment route or your access region changes. If a clause is unclear, contact support and ask before you act on it. We would rather answer a question early than correct a problem later, and the same address that handles wallet questions handles policy questions.
Not every part of what you see on screen is covered by the same document. Account access, the wallet attached to it, bKash deposits, Bank Transfer funding and withdrawals back to those routes all sit inside this policy, along with how we record session activity and handle a complaint about a transaction. What sits outside are the third-party services you reach through us, such as a bank or a mobile wallet app; those run under their own rules, and the operator's terms govern the transfer itself. Game content is separate again, because how a round resolves comes from the game and its provider, not from this page. If local law where you are does not permit a particular route, a cricket market or a game category, that part of the site falls outside your scope of use, whatever these terms say in general. When something on screen does not match what you read here, treat the account record as the reference point and ask support to confirm it.
Signing in, the details you registered and the session you are holding all sit inside this policy. If you share a phone with family, sign out when you finish, so the record on your account stays yours and any later transfer under your name is one you actually made.
bKash deposits, Bank Transfer funding and withdrawals back to those routes are covered here, including the reference shown on each entry. The bank or wallet app itself runs on the operator's terms, so keep that receipt, since it is what you will need if a movement is questioned later.
What you read on our pages, this one included, sits inside the policy as published. Game rules are the exception: how a slot feature resolves or a live table settles comes from the game and its provider, and those rules appear in the game itself, not in this document.
Services you reach through the site but do not run ourselves are outside this policy. That includes your bank and your mobile wallet app, each of which has its own user agreement and its own complaint route. Raise the issue with them first when the problem starts inside their app.
Your side of this policy is mostly about keeping your own account accurate. Sign in and open your account area to check the details we hold: the name on the account, the mobile number tied to your wallet, and the bKash or Bank Transfer route you last used. If a line is wrong, correct it there rather than leaving it, because the record we hold is the one we act on when you contact us. Every wallet movement should appear in your transaction list, and if a transfer you made is missing or looks different from what you expected, raise it with support and quote the reference shown on the entry. You can also ask what data we hold about you, request a copy, or ask what we changed and when. If you disagree with an outcome, say so in writing and we will tell you which section of the terms we applied. Closing the account is available too, though we may keep a record of transactions as the terms describe.
Sign in and open your transaction list to see every wallet movement tied to your account, with the reference each one carries. Read the entry before you raise anything, because the reference and the date are the two details we ask for first when you write in.
Update the name, registered mobile number or payment route in your account area whenever something changes. Those fields decide how we reach you and which route we treat as yours, so a stale entry can slow a wallet question down before it even starts.
Write to the published support address with your account number and the clause you are asking about. If you disagree with a decision, say which decision and when you received it, and we will point you to the section of the terms we applied.
You can ask what account details we hold, request a copy of them, and ask what has changed since you registered. We will tell you what we can amend and what the terms require us to keep, such as records of completed transactions.
Questions about the terms reach the same place as questions about your wallet. Send them to the support address published in the site footer, and put your account number in the message so we do not have to ask twice. If your question is about a specific transfer, paste the reference from your transaction list along with the date you see on it, because that single detail usually decides how quickly we can point to the right clause. For anything about signing in, changing your registered mobile number or reconnecting a bKash or Bank Transfer route, use the help links inside your account area, since those steps need you signed in to complete. Policy questions and wallet questions run through one published contact route, so you do not need to work out which team to approach. If you are writing about an outcome we gave you, say clearly which decision and on what date you received it. We answer in the order messages arrive, and we reply to the address your account is registered to.
The support address published in the site footer is the route for policy questions and wallet questions alike. Include your account number, and where a transfer is involved, the reference from your transaction list, so the reply can name the clause that applies rather than asking you to write in again.
Inside your account area you will find the help links for signing in, changing your registered number and reconnecting a payment route. Those steps need you signed in, so start from your account rather than a public page and follow the fields as they are shown.
If you are writing about an outcome, reply to the message you received so the whole thread stays together, and state clearly which decision you are questioning along with the date on it. That keeps the history in one place for both sides.
We keep your account details because we need them to run your wallet, and we hold them no longer than the terms describe. Cookies do the everyday work: they keep your session open so you are not asked to sign in on every page, and they remember the payment route you selected. You can clear them from your browser whenever you want, though you will sign in again afterwards, and on a shared phone that is a sensible habit after each session. Sign-in protection rests on your own password and on the details you registered, so never share them in reply to a message. Our support team will not ask you for your sign-in or wallet password by chat or phone. If someone claims to be us and asks for it, stop the conversation and report it through the published support address. Records of completed transactions stay in your account area so you can check them later, and access to account data is limited to the teams that need it to answer you.
We keep the details you register and the record of wallet activity tied to your account, because answering you needs them. Inside our team, access is limited to the people who handle account and payment questions, and nothing is passed on for unrelated purposes.
Cookies hold your signed-in session and remember the payment route you picked last. Clear them from your browser whenever you like; you will simply sign in again, and on a shared phone that is worth doing at the end of each session.
Your sign-in details are yours alone. Our team will never ask you to share your password or your wallet password by message or over the phone. If someone claims to be us and asks for either, stop the conversation and report it to the published support address.
Records of completed transactions stay available in your account area so you can check them later. If you want a detail changed, write to the published support address, and we will explain what we can amend and what the terms require us to keep.
These are the questions our support inbox gets most often about the terms, gathered in one place so you can check before you write in. The short answers below name the route, the record or the section of the policy that settles the point. Where an answer depends on your region, we say so plainly instead of pretending the rules are the same for everyone. Read the account, wallet and data questions first if you are new, because they cover what most first messages ask about. If your question is not here, or if the answer turns on details only your account record shows, send it to the published support address with your account number. We will answer the specific case rather than pointing you back to this page. Nothing here changes the published terms themselves; it explains how we apply them in practice.
It covers your account access, the wallet attached to it, any bKash deposit or Bank Transfer funding you make, withdrawals back to those routes, and how we record session activity. Third-party bank or wallet services run under their own terms instead, so their rules apply to the transfer itself.
That depends on your local law and eligible regions, not on anything we can switch on for you. If a route, a cricket market or a game category is not permitted where you are, it falls outside your scope of use even though the terms exist on the page. Ask support if you are unsure about your region.
Sign in and open your account area, then update the field that is wrong: the name on the account, the registered mobile number, or the payment route you use. Changes you make there are the ones we act on, so correct them rather than telling support and leaving the old entry standing.
Open your transaction list and check the entry against the reference your wallet or bank gave you. If the movement is missing, or the amount looks different from what you expected, send the reference and the date to support and we will tell you which section of the terms applies to your case.
Write to the published support address from the email registered to your account, and say which detail you want changed and why. We will confirm what we have on file, tell you what we can amend, and explain anything the terms require us to keep, such as records of completed transactions.
The current version always sits on this page, and your account area shows the wording you agreed to when you registered. When a clause changes, the updated text replaces what you read here, so read the section again before you rely on an older copy.