Slots / Mobile
888ed runs one account across our sportsbook and casino floor, and these terms are the rules that sit behind it — your login, your wallet balance and every market you open. Whether you can register and play depends on your local law and eligible regions, so read this page with your own country in mind.
Terms are the working agreement between you and 888ed, and we write them so the whole thing can be read on a phone between overs. Nothing here overrides the law where you live. If a clause conflicts with a rule that applies in your region, the local rule wins, and we will tell you which parts of the account we have to restrict. That is why a feature described on one page may not be switched on for every country. Money moves through the wallet routes shown in your account — bKash, Nagad, Rocket, Upay or Bank Transfer where those are available to you. These clauses set out what we expect when you move money: the wallet must be in your own name, the details you type must match your account record, and we may ask you to confirm a payment before it is completed. We do not promise a processing time here, because the route your money takes depends on the wallet, the bank and your region. Your side of it is simple to state. Keep your login details to yourself. Do not let anyone else use your account. Tell us quickly if something looks wrong. Ours is to keep the rules visible, apply them the same way to every account, and give you a route to ask when a clause is not clear. Read the full text before your first deposit so you know what applies to you.
These terms sit over four areas of the site, and it helps to know which one you are reading about. Account access takes in how you open an account, how you sign in and what happens when a session is left open on a phone you share. Transactions take in the wallet side: the deposit you send through bKash, Nagad, Rocket or Upay, the balance you see on screen and the withdrawal you request from it. Site content takes in the lobby itself — the cricket markets in our sportsbook, slots and live tables, and the studio titles we carry from JDB, PlayStar, Microgaming and Bigtime Gaming. Third-party services are the parts we do not run: your mobile wallet, your bank, your network and the browser you installed on the phone. When a problem sits inside a third-party service, that service's own rules apply first and we can only work from our side of the handover. Read every clause with that split in mind and you will know who to ask.
Account access means opening an account, signing in, resetting a password and what we do when a session stays open on a phone you share. If you register from a country where the site is not offered, we cannot keep that account open, and these clauses do not apply to it.
Every deposit and every withdrawal request sits under these clauses, along with the wallet details you type in. We expect that wallet to be in your own name and to match your account record, and we may ask you to confirm a payment before we complete it.
The lobby itself falls under these clauses: the sportsbook markets such as Live Cricket Odds and Football SuperGoal, the slots and live tables, and the studio titles we carry from JDB, PlayStar, Microgaming and Bigtime Gaming. We can add or remove a title, and we can correct an obvious error on a page.
Your mobile wallet, your bank, your network provider and the browser on your phone are not ours, and their own terms rule inside them. When something fails there, raise it with that provider first; we can help from our side of the handover, though we cannot rewrite their rules.
Much of a terms page is about what you can ask for, so here is your side in plain words. Open your account record whenever you want and read what sits against your profile, your wallet entries and your sign-in history. If a detail is wrong, ask for it to be corrected and we will tell you what proof we need first. If a clause reads oddly, ask about it before you act on your own reading; a quote of the heading or line makes the answer quicker. Questions raised through the published route come back in writing, so you have a record rather than a half-remembered call. If a transaction entry and your own receipt disagree, ask us to go through it with you. You can close the account whenever you decide to, and the clauses on records stay in force afterwards.
You can open your account record whenever you like and read what sits against your profile, your wallet entries and your sign-in history. Ask through the published route if a line does not make sense; we would rather explain an entry than have you guess at it.
A misspelled name, an old phone number or a wallet reference that no longer matches is worth correcting early. Send us the change through the published route and we will tell you what proof we need before a record is amended, because account and wallet details have to line up.
If a sentence reads oddly, put the question to us before you act on your own reading of it. Quote the heading or the line you are asking about and we will answer in writing, so you have something to keep. It takes a short message and saves a longer argument later.
Every policy answer we send comes in writing, and the reply carries a reference you can quote if you come back to the same question. Keep it beside your wallet receipts. If you later close the account, that written trail is the cleanest way to settle anything still open.
Policy questions are not the same as game questions, so we keep the routes apart. Anything about a clause — what a line means, why a wallet entry was flagged, what proof we need to change your details — goes through the contact route we publish on the site. Open it from your signed-in account and your account reference travels with the message, which saves a round of going back and forth. Quote the heading or the line you are asking about. If your question is about a market or a table instead, use the route shown in the lobby, and if it is about a deposit, keep the wallet receipt beside you. We answer in writing so you can look back at it later, and the reply stays attached to your account rather than sitting in someone's memory.
The contact route we publish on the site is where policy questions land. Use it rather than a social channel, because a written message keeps your account reference attached and gives you a reply you can quote later if the same question comes back to you.
Opening the route while you are signed in is the quicker path. Your profile loads with the message, so you do not have to type an account number from memory, and the history stays with your account when you return to the same clause another time.
For a question about a deposit or a withdrawal, keep the wallet receipt beside you. It carries the reference bKash, Nagad, Rocket, Upay or your bank showed you, and that reference lets us find the entry on your account instead of guessing which payment you mean.
How we hold your data follows the same logic as the rest of the site: take what a sign-in or a transaction needs, keep it somewhere we can protect, and let you ask what is on file. We do not sell your details to anyone. Cookies do a few quiet jobs — keeping you signed in on your own phone, remembering the language you picked and showing us which parts of the lobby get opened most so we can lay them out better. Clear them in your browser settings whenever you like; you will simply have to sign in again. Account security is shared work, so we ask for your login details, you keep them to yourself, and we flag a sign-in that looks unusual. Records stay for as long as the account, the law that applies to us and any open dispute need them, then they are removed. Write to us through the published route to see or change what we hold.
Enough to run the account and nothing spare: your registration details, your sign-in history, your wallet entries and the support messages you send us. We do not sell that data, and we do not pass it to a marketing list. You can ask what sits on file.
Cookies keep you signed in on your own phone, remember the language you chose and tell us which lobby sections are opened most. Clearing them in your browser settings is your call; the only cost is signing in again on the next visit to the site.
Your login details are yours to protect. Do not share them, and avoid signing in on a device you do not control. If you spot a sign-in you do not recognise, tell us through the published route and we can review the session history on your account with you.
Records stay while the account is open, while the law that applies to us requires it and while a dispute is unsettled. After that they are removed. To see, correct or ask us to delete what is not required, send the request through the published route from your signed-in account.
The clauses above raise the same handful of questions from Bangladesh accounts, so the answers sit here in the same plain words we use everywhere else. Each one describes what we do and what you can ask us to do — not what we would like you to believe. Where a rule turns on where you live, the answer says so rather than suggesting the same thing works for everyone. If your question is not here, the published contact route is the place for it, and the written reply reaches you with your account reference attached. Read these first; a good few of them are probably the exact thing you were about to ask, and a question you send about a clause gets answered in writing that stays with your account.
They can, and we will not pretend otherwise. When a clause is updated, the version live on the site is the one that applies to your account from that point. If a change affects what you can ask for, we flag it in your account area.
The rules where you live come first. We write these clauses to fit as many regions as possible, but if your local law says something different, that law wins. Availability of the site, and of any wallet route, depends on your region.
Yes. The page is built for a phone browser, so you can read a clause while you wait for something else. Headings let you jump to the part you need, and nothing here sits behind a desktop-only layout. If a line is still unclear, ask us about it.
Actions taken in your account sit on your account, so tell us as soon as you notice. We can review the sign-in history with you and lock the account while we check. Keep your password and any code you are sent to yourself.
Use the contact route published on the site and open it from inside your signed-in account, so your account reference travels with the message. Quote the heading or the line you are asking about, and we will answer you in writing.
Yes. bKash, Nagad, Rocket, Upay and any bank route you use carry their own terms, and those govern what happens inside their app. Our clauses cover what we do with the payment once it reaches your account wallet.