App / Mobile
These are the fa3333 Terms & Conditions — one document covering how you open an account, move money through Rocket or Upay, and use the lobby on whatever phone you are holding. What you can reach depends on your local law and eligible regions, so read the wording with your own market in mind.
One document runs the whole site, and it works the same whether you signed in from a phone browser or a desktop. We set these terms so every step you take — opening an account, adding funds through Rocket, Upay, bKash, Nagad or a bank transfer, joining a live table — sits under rules you can read before you act rather than after. Short does not mean vague. Each clause sets out what you agree to and what we commit to in return. Where a term depends on where you are, we say so instead of writing as though one rule fits everyone. Access to parts of the lobby, and to any wallet route, depends on your local law and eligible regions, and the markets we can serve change as those laws change. If a clause cannot apply where you live, it drops away and the rest of the agreement still stands. Nothing is hidden either: the full text stays on this page with a version date. We keep the wording in everyday English rather than legal shorthand, because a term you cannot follow is a term you cannot lean on. If you keep using your account after we publish a change, that counts as accepting the updated version. If you would rather not, stop using the account and ask us to close it. Questions about a single line go through the support routes listed below.
Not every question about the site belongs in this document, so it helps to know what these terms do and do not reach. They sit at platform level: the agreement between you and us when you hold an account, move funds through the wallet routes we have configured, and use the lobby. They follow your sign-in rather than a device, so the same rules cover phone and desktop sessions. Inside the scope you will find account obligations, wallet wording, acceptable use, how changes are published and how you raise a dispute. Outside it sit the rules a game runs on, the agreements Rocket, Upay or your bank holds with you, and the services your network or browser provides. Local law sits above everything on this page. Where a clause and your local law disagree, the law takes precedence and the clause does not apply to the extent of the conflict. Access depends on your local law and eligible regions, so a lobby area open in one market may not be offered in another.
These terms cover the account you open with us, the email and password that protect it, and the details you keep on file. You are responsible for entering accurate details and for what happens under your sign-in. If you notice access you did not start, tell support straight away so we can act on it.
Every top-up and withdrawal you begin runs through a payment route we have configured, such as bKash, Nagad, Rocket, Upay or a bank transfer, and each one leaves a line in your account history. Wallet providers run their own agreements, so check their terms too when a transfer leaves your phone.
Rules for a round come from the game itself. Slot feature behaviour in Slot Blenders, table procedure in Roulette Masterclass or Blackjack Action, and cricket markets in Cricket PowerPlay are set inside each title and shown on screen. Our terms govern how you reach and use them, not how a round resolves.
Your mobile network, your browser or operating system, and the wallets and banks you use sit outside this agreement. We cannot rewrite how another company handles a transfer or an app update. When something breaks on their side, we point you to the right place and help where we can from ours.
Terms work both ways. We set obligations, and you get a set of moves you can make when something looks off. Four come up again and again. First, check your own records. Every wallet movement you start — a bKash deposit, a Nagad transfer, a Rocket payment — leaves a line in your account history with the date and route used. Second, keep your profile accurate. If your email or phone number changes, update it in the account area so confirmations reach the right place. Third, ask before you act: if a clause reads oddly, send the exact wording to support and we will explain how we apply it. Fourth, request a change. You can ask for a correction to stored details or for the account to be closed, and we will tell you what that step involves. We publish the route for each of these, and every question you raise carries a reference number so the thread stays together. Local law may give you further options; where those exist, they sit alongside this agreement.
Open the account area and the movement lines are already there: date, route and status for each bKash, Nagad, Rocket or Upay entry. Read them against your own wallet messages. If a line does not match, copy its reference before you contact support so a single transfer can be traced.
Your name spelling, email and phone number drive every confirmation we send, so keep them current in the account area. Change them yourself when they move, rather than letting messages land somewhere you no longer read. If a field will not save, tell support which one and we will look at the record with you.
Send the exact sentence, not a summary, and we can point to how it is applied in practice. Questions about wallet wording, acceptable use or account closure all go the same way. You will get a reference number to keep, and you can reply on that same thread rather than starting again.
When you want stored details changed or the account closed, say so plainly and we will set out what the step involves before anything is done. Closure is handled by a person, not a button: you will be told what happens to any balance and which records we keep. Using the published support route keeps the request traceable.
Questions about this policy do not need to go through guesswork. We publish the routes we answer on, and each one leaves a record you can point back to. The entry point sits inside your account area, so the form carries your account context before you type a word; the live chat control stays in the site header while you read this page. Nothing about either channel changes when you switch from a phone to a desktop, because both follow the sign-in rather than the device. What we cannot do is promise a reply within a set number of minutes, and we do not print handling hours on this page because any current details belong on the support page where they can be kept up to date. What we can say is that every message you send is attached to a reference, and the reference is what we ask for when you follow up. If your question is not about the terms at all — a wallet transfer that has not landed, for example — that still starts in the same place.
Sign in and the support entry point sits in your account area, where the form already knows which account is asking. Paste your transaction reference or the clause you are querying, and the message arrives with the right context attached. That route handles anything touching wallet lines, account details or a term you want explained.
The chat control stays visible in the header while you browse, so you can ask a short policy question without leaving the page you were reading. Keep it for things that need a quick answer, such as where a clause sits or which document covers a step, and use the written route when the reply needs a reference number.
Formal requests — a correction to stored details, an account closure, or a disagreement over how a clause was applied — belong on the written support route published on this site, so there is a dated record on both sides. Quote the version date shown on this page when you write, and the thread can be traced.
There is no separate document hiding behind this one. Data handling, cookie use, sign-in protection and how long we keep records are all set out here, in the same terms you are reading, so you do not have to hunt across pages to understand what happens to your details. Two things drive what we keep. The first is running the account: a sign-in, a profile, wallet lines and support threads — the material that lets you trace a Rocket or Nagad transfer or have a detail corrected. The second is local law, which may require us to hold certain records for a period and may also give you the right to ask what is on file. Where those two meet, the law sets the floor. Access to your own record is straightforward: sign in and the account area shows your profile, movement history and any threads you have open. If something there is wrong, you can correct it yourself or bring it to support with a reference. Nothing in this section gives us a right to your password.
We hold what the account needs to run: your sign-in details, the profile fields you enter, wallet movement lines and the support threads you open. That record is what lets a transfer reference be traced or a correction be made. We do not ask for anything a clause here does not cover.
Cookies keep a signed-in session alive so you land back in the same place after a reload, which matters on a phone where tabs get dropped. Your browser settings let you clear them, though doing so signs you out and you will need to log in again. We keep cookie use to what the session needs.
Your password is yours alone. Choose one you do not reuse elsewhere, and treat any code or link sent to your phone as private. If a device is lost or shared, change the password from the account area and tell support, so we can look at the sign-in with you. We never ask for your password in a message.
Records tied to wallet movements and account history stay for as long as the agreement and local law require, and then they go. When we change this policy we publish a new version date, and the change applies from that date. Requests to see, correct or remove stored details go through the published support route.
The same few questions land in our support threads again and again, so we answer them here in plain words rather than sending you back into the agreement. If your situation is not covered, send the exact clause you are reading and we will walk through how we apply it to your account.
Yes. Holding an account means the agreement applies, and we cannot run a wallet or a lobby without it. You are free to stop using the account at any time and ask us to close it. If you keep signing in after a new version is published, that counts as accepting it.
We publish a version date with the text, and the date moves when the wording does. The current version stays in one place, so what you read on this page is the live wording. Check the date shown above the first clause if you are comparing what you agreed to.
Local law takes precedence. Where a clause here conflicts with a rule that applies where you live, that clause does not apply to the extent of the conflict, and the rest of the agreement still stands. Access to parts of the site also depends on your region and eligible areas.
The wallet wording covers the routes we have configured, including bKash, Nagad, Rocket, Upay and bank transfer, and it explains what you agree to when you move funds through them. Each provider also holds its own agreement with you, so read that side as well when a transfer leaves your phone.
The agreement attaches to your sign-in, not to a device, so a phone session and a desktop one sit under the same wording. Your profile and movement history follow you between them. Cookies only keep the session alive, and how long they last is set by your browser.
Closure is handled by a person, not a button. We will set out what the step involves and what happens to any balance before anything is finalised, and you will be told which records we keep and for how long. Ask through the written support route so the thread is dated.