App / Slots
At 8up8 the legal side is written for one reader: you, on a phone, wanting a straight answer about your own account. This page sets out how we run accounts, how wallet records and lobby rules sit together, and what you can ask us to change — with access depending on your local law and the eligible regions we serve.
Legal wording is where a platform either earns your confidence or loses it, so we keep our side short and readable. These terms set out what you agree to when you open an account with 8up8: how you sign in, what you may do in the lobby, how wallet activity is recorded, and what happens when something goes wrong. We write for one reader — a returning member in Bangladesh holding a phone — so sentences stay plain and the order follows the questions you actually ask. A clause should be something you can act on, not something you scroll past. Availability is not ours to decide. Whether you may hold an account and use a wallet route such as bKash, Nagad, Rocket, Upay or a bank transfer depends on your local law and the eligible regions we can serve, so check what applies where you live before you register. Where local rules differ from anything written here, local rules win. When we change a clause we publish the new version on this page, and the version showing when you next sign in is the one that applies. Older copies stay available so you can compare them. If a line reads oddly, ask through the support route listed on our support page instead of guessing what it meant.
This page draws a line, and it helps to know which side your question lands on. Account access sits inside the policy — how you register, how you sign in from a phone browser, and what your profile may hold. Wallet activity sits inside as well, at least the part we control: the record our side keeps of what you sent and what came back to you. The lobby sits inside too, including how titles from Spadegaming, JDB, Pragmatic Play or Bigtime Gaming are listed and what our own pages say. What sits outside is anything a partner runs under its own rules, such as the wallet app on your phone or the provider handling a transfer. Your local law and eligible regions still decide whether any of this is open to you. When a question touches two sides at once — a wallet entry, for example — start with us and we will tell you which part we can answer ourselves.
Registration and sign-in sit inside this policy. That means the details on your profile, the password you choose and the way your session behaves on a phone browser are governed by the terms on this page. If you change a field, keep it accurate. A stale number slows every later question.
Transfers you send through bKash, Nagad, Rocket, Upay or a bank transfer appear in your account record, and that record is what this policy governs. The wallet app you send from runs to its own conditions, so the provider's wording and ours both apply — one to their side, one to ours.
How games from Spadegaming, JDB, Pragmatic Play and Bigtime Gaming are listed in the lobby, and everything our own pages say, sit inside this policy. Individual game rules are shown with the game itself, so check those before you argue a round from the wrong rulebook.
Some of your journey belongs to companies we work with rather than to us. A wallet app, a bank's transfer screen and the provider sitting behind a payment are outside this page and run to their published terms. Questions about their side go to them, though we can tell you which part is ours.
Opening the account area is where most of your choices actually live. Sign in on your phone and the profile screen shows the details we hold for you — your name, your contact number, and the records tied to your sign-in. Read them once in a while; a wrong digit in a phone number is the kind of thing that slows a wallet check later. Everything on this page is a request you can make, not a favour you have to hope for. You can ask what we hold, ask us to fix something that is wrong, ask why a transaction was handled the way it was, or ask us to close the account. Use the support route listed on our support page and quote the section heading you are reading, so your request reaches the right people the first time. If local rules give you a stronger right than this page describes, that right stands.
Sign in on your phone and the account area shows what we hold: your name, your contact details, your sign-in history and the wallet entries tied to your profile. Check it against what you know. Reading your own record first saves a round of messages later.
If a number, a spelling or an old address is wrong, correct it in your profile rather than mentioning it later. Corrections are usually quick, and they keep a wallet check from stalling on a mismatch. Where a change needs a document, we say so before it is applied.
When a transaction or an account decision looks wrong to you, ask why. Say what you expected, what you saw and when, and quote the section of this page you are relying on. A clear question moves faster than a long complaint, and you can ask again if the first reply misses the point.
You can ask us to close your account, and you can stop using it at any time without asking. Some records stay with us after closure because local rules require it, and we will explain which ones when you send the request through the support route.
Policy questions are the ones people sit on for weeks, so we would rather you send them straight away. Everything we publish as a channel is listed on our support page, and that page is the only list that counts — if a contact route is not shown there, it is not ours. From a phone, the route is two taps: menu, then support. When you write in, say what you were doing, which section of this page you are reading, and which wallet you used — bKash, Nagad, Rocket, Upay or a bank transfer — because that detail decides who picks up the question. Keep any reply you get, clause heading and all. Signing in first helps too, since a request from inside your account is already tied to your profile and we do not have to ask you to prove who you are twice. Nothing is settled in passing that is not written down.
Every policy question starts at our support page, which lists the contact options we actually run. Open it from the menu on your phone, describe the clause you are asking about, and quote the section heading so the reply points at exact wording instead of a general answer.
Sign in before you write and your request arrives tied to your profile, so you never have to explain which wallet you used or which phone number is yours. Writing from inside your account also keeps the thread together, ready for you to pick up again later.
This page is what we answer to. If a support reply and a clause here disagree, read the clause once more and write back — we would rather correct our reply than leave a rule open to two readings. Keep the reply with the clause heading beside it.
Behind this page sits the unglamorous work: what we keep about you, why we keep it, and how long it stays. Your account record holds the details you gave at sign-up, your sign-in history and the wallet activity tied to your profile. We use it to run your account and to answer you when you ask a question, not to fill your messages with things you did not ask for. Cookies do a smaller job than people expect here. They keep your session open so you are not typing your password on every page turn, and they remember basic layout settings for a small screen. Clear them on your phone and you will sign in again, which is normal behaviour rather than a fault. Account security is shared work — keep your password to yourself, and tell us through the published support route the moment anything on your account looks unfamiliar to you.
Your profile keeps the details you gave when you registered, the record of your sign-ins and the wallet activity tied to your account. We use that to run the account and to answer you, and we keep it only as long as local rules and ordinary record-keeping require.
Session cookies keep you signed in while you move around, so you are not typing a password on every page turn. Settings cookies remember how the layout should appear on a small screen. Clear them and you will need to sign in again, which is normal, not a fault.
Your password is yours alone — nobody from our side will ask you for it in a message. If something about your account looks unfamiliar, change the password straight away and tell us through the published support route so we can look at it with you.
Requests to correct, export or remove what we keep go through the same support route. We answer every request that reaches us, and we explain a refusal when local rules force us to hold a record. Nothing is deleted quietly without telling you.
The questions below are the ones a reader sends us most often after opening this page. Answers stay short on purpose — a policy reply should fit in a message, not a wall of text. Where a question touches your wallet, the payment provider's own conditions sit alongside ours, so read both before you act. Nothing here overrides your local law; the wording on this page sits under it, and eligibility depends on your local law and the eligible regions we serve. If your question is missing, the support route published on our support page is the quickest way to a straight answer, and asking early costs you nothing. Keep the reply you get, because it stays useful if the same issue comes up again later.
Whether you may open and keep an account depends on your local law and the eligible regions we can serve, not on anything written here. Check the rules where you live first, then register only if you are covered. If local rules say no, this page cannot change that.
It governs the part of a transfer that lands in your account record — a bKash, Nagad, Rocket, Upay or bank transfer entry and the history tied to your profile. The wallet app you send from runs under the provider's conditions, so read those as well before you confirm anything.
When we change a clause we publish the new wording on this page, and earlier copies stay on file so the older text can be compared with the current one. Sign in and ask through the support route if you need a specific date checked, and quote the section heading you mean.
Yes. Open your profile in the account area, check each field against the documents you use for wallet checks, and send the correction through the published support route. Some changes may need a document check before they take effect, and we will tell you if that applies to yours.
Put it in writing through the support route published on our support page. Say which section of this page you are relying on, what you expected and what happened, and keep any reply you receive. Where local law gives you a right to escalate beyond us, that right stays open to you.
They do a small, practical job. A session cookie keeps you signed in while you move between pages on your phone, so clearing cookies means typing your password again next time. Settings cookies remember how pages should display on your screen. A cookie never replaces the account record tied to your profile.