Casino / App
3ok bet keeps its legal terms on one page, so you can see how your account, your wallet records and your access to the lobby are covered before you use them. Access still depends on your local law and on eligible regions, so the version showing in your account area is the one that applies to you.
We keep our legal wording plain where we can, because a policy you cannot read is a policy you cannot use. What sits on this page explains how our terms reach your account, and how they shift with your location and with what local law allows. Access to any part of the lobby, and to the payment rails shown in your account, depends on where you are and on eligible regions, so some options may not appear for you at all. Nothing here sets a fixed result: when a route is not open to you, the account pages show what is. Payment names appear on this page as context, not as an offer. Nagad, Upay and Bank Transfer are listed because those are the rails we present in the wallet area, and a term that touches a transfer touches them. Your transaction records, the terms you accepted when you opened the account, and any notice we place inside the lobby all sit alongside this page and should be read together. If two documents appear to disagree, write to us through a published support route and we will point you to the version that governs your account. We change wording when the way we operate changes. The version visible in your account area at the time you use the site is the one that applies to that use, so it is worth a look before you complete a step you have not done before. Where a clause cannot apply in your region because of local rules, the rest of the terms continue as written.
These terms reach the parts of the site that sit under our control, and they stop where someone else's rules begin. Your sign-in, the details on your profile, the records we hold for Nagad, Upay and Bank Transfer movements and the content we publish in the lobby are all inside. A wallet app on your phone and a bank page you open yourself are outside, because those run on their own terms and we cannot apply ours to a step that happens there. Region matters too. Where local law restricts a category such as live tables, crash games or cricket markets, that restriction applies before anything else you see on the site, including a tile that is still visible in the lobby. We would rather tell you that plainly than leave you to find it at the last step of a transfer. If you are unsure whether something falls inside these terms, ask before you act, and a short message through a published support route is enough.
Opening the account, signing in from your phone or your desktop and keeping your details current all fall under these terms. Where access is restricted in your region, that restriction applies before anything else on the site, including any lobby tile or wallet route you happen to see listed there.
Nagad, Upay and Bank Transfer movements tied to your account, along with the records we keep for them, sit inside this policy. A rail behaving differently on your device does not change a term; the account pages show what is open to you before you confirm anything at all.
Game tiles, studio names, category labels and lobby copy are covered as content, not as a promise about a result. A title from a studio in our lobby being visible does not mean it plays in every region, and we treat a listing as no more than what the lobby shows.
Some routes point outside the site, such as a wallet app on your phone or a bank page you open yourself. Those services run under their own terms, and we cannot apply ours to a payment step that happens inside an app we do not control.
Being able to see what we hold about your account is the starting point. Your account area shows your profile details and the transaction records tied to your Nagad, Upay and Bank Transfer movements, so you can check them yourself before writing to us. If something there is wrong, a mistyped mobile number, an outdated name, a record that does not match your wallet statement, tell us and we will look at it with you. We can act only on the details we can see in the account, so keeping those current saves everyone time. Questions about how a term applies are welcome, and you do not need a reason to ask. Write through a published support route, describe the term or the record you mean, and keep the reply you get, because it stays useful if the same question comes up later. Where local law gives you a right we have not described here, that right still stands, and nothing on this page is written to take it away from you.
Your account area shows your profile details and the transaction records tied to your wallet movements. Look there first when you want to see what we hold, because your own account always shows the current version rather than a copy someone has to fetch for you.
A mistyped mobile number, an outdated name or a record that does not match your wallet statement can all be raised with us. Tell us which field is wrong and what it should say, and keep it in the same thread so we can compare both.
You can put a question about any part of these terms to us without explaining why you want to know. Name the clause or the page and describe your situation, and the reply you get is worth keeping if the same question comes up again.
When something on the account is not behaving the way these terms describe, use a published support route and set out what you expected against what you saw. We work from the account itself, so sign in before you write wherever you can.
Every policy question runs through the routes we publish on the site, so start from your account area and open the help pages there. That is where the current contact options appear, and it is the same place any follow-up about your request will arrive. Describe the term, the record or the page you are asking about, and add the account detail that helps us find it, such as the wallet identifier for a Nagad, Upay or Bank Transfer movement or the email address on your profile. If you write from somewhere else and we cannot match you to an account, we may ask you to continue from inside the signed-in area before we can say anything about your records. We do not publish a fixed response time on this page; where a route sets its own expectations, follow what it shows you. Keep the thread intact so the whole exchange stays readable for both sides.
Sign in and open the help section of your account area. That is where our contact routes are published and where any follow-up about your request arrives, so starting there keeps the exchange attached to your account rather than to a mailbox you might lose.
For a question about a clause, a record or a page on the site, use the message form and name what you are asking about in the first line. Add the wallet identifier for a Nagad, Upay or Bank Transfer movement when the question concerns a transfer.
Where chat is shown in your account, it is a direct way to ask something short before you complete a step. Keep the request to one subject, and if the answer needs a record check, continue through the message form so the details stay in one place.
Your data reaches us through the account you open and through the wallet routes you use, and we hold it to run that account rather than to build a profile for someone else. Cookies and small device signals do a narrow job here: they hold your sign-in state, remember the language you read the site in and tell us when a page fails so we can repair it. You can clear them from your browser settings whenever you like, though you will sign in again afterwards. Account safety is shared work, so we keep the details you gave us tied to your account and we ask you not to reuse a password from another site or hand your sign-in details to anyone who contacts you first. Records stay with us for as long as the account, the transactions behind it and the legal duties that apply where you live require them. When you want a detail changed or want to know what we hold, use a published support route and say what you need.
The profile details you give when you open an account, and the wallet identifiers tied to your Nagad, Upay or Bank Transfer movements, are held against your account so a support request can be matched to the right person rather than to a name alone.
Cookies keep your sign-in state, remember your language choice and record page errors so we can repair them. They do not decide what you see in the lobby. Clearing them in your browser is fine, and the only effect is that you sign in again on your next visit.
Keep your sign-in details to yourself and avoid reusing a password from another site, because a shared password is the most common way an account is lost. If you think someone else has your details, write through a published support route so we can look at the account with you.
We keep account and transaction records for as long as the account and the legal duties around it require. Ask through a published support route when you want a detail corrected or want to know what we hold, and we will explain what can change and what has to stay as recorded.
Most of what people ask about these terms comes down to three things: where the rules apply, what we keep, and who to speak to. The answers below take them in that order, and each one points back to something you can see for yourself in your account rather than to a promise about a result. If your situation is not covered here, do not guess from the wording. Open your account area and use a published support route, because an answer that matches your account is worth more than one written for a general case. We have kept each answer short on purpose, so you can check it on a phone between other things. Anything you read here sits alongside the terms you accepted when you opened the account, not in place of them.
They are published on this site, and the version showing in your account area when you use it is the one that applies. Your transaction records and the terms you accepted when you opened the account sit alongside them, and all three are meant to be read together.
Yes. The same terms cover you on a mobile browser, on a desktop or on a tablet, and nothing about the device changes what applies. What can change is which routes are open to you, depending on your local law and eligible regions, so check the account pages after you sign in.
Payment availability depends on your local law and on eligible regions, so the rails listed in your wallet area reflect what is open to you rather than a fixed set. Nagad, Upay and Bank Transfer appear as context where they apply, and the account pages are the place to look.
Open your account area, find the record and compare it with your wallet or bank statement before you write to us. Then send the identifier for that movement through a published support route. We can act only on what the account shows, so matching the two first saves time on both sides.
You can, and you do not need a reason. Name the clause or the page you are asking about and describe what you want to know. The answer you get stays useful later, so keep the message thread rather than starting a fresh one each time.
Wording changes when the way we operate changes. The version visible in your account area when you use the site is the one that applies to that use, so it is worth opening before you complete a step you have not done before. Where local rules block a clause, the rest continues.