Live / App
This is where bj688 publishes the notices that sit behind your account: what you agree to when you register, how your wallet is treated, and what happens when something needs to be challenged. Access depends on your local law and the regions we can serve, so check your own position before you sign in.
bj688 sets these notices out before you deposit, not after, because you should know the ground rules at the point you sign in. They cover what happens when you open an account, how your wallet balance is treated, how a transaction is recorded, and what we expect from you while you use the sports markets, live tables and slot rooms in the lobby. The payment chips above - bKash, Nagad, Rocket, Upay, bank transfer - are context, not a promise: which rails we can support depends on your local law and your eligible region, and the account page shows what is live for you. Where a term depends on where you are, we say so instead of guessing. Registration, deposits, withdrawals and game availability can differ between regions, and some categories are restricted in some places. That is why the wording here stays general and the specifics appear in your account and in the published terms. You agree to these notices when you create an account; if you disagree with any part of them, do not use the service. We can update the wording when the product changes, and the version published here is the one that applies. Read the account page alongside this page so nothing takes you by surprise at withdrawal time.
Our notices reach the parts of the service you actually touch, and they end where another company's rules take over. Account access sits with us: how you register, how you sign in, and what you must not do with your credentials. Transactions sit with us as well, from the moment you move money through bKash, Nagad, Rocket, Upay or a bank transfer into your wallet to the point a withdrawal is settled under the fields shown in your account. Site content is ours too. The sports markets and casino categories we list, the way a bet is placed, and the rules on a game round are set out in the terms linked from the lobby. What we cannot write rules for is anything outside our own pages: a wallet provider's charges, a bank's own processing decisions, a data connection that drops mid-session, or a studio's separate end-user terms. Those belong to the third party, and you deal with them directly. Where a category is restricted by local law, we do not offer it to you rather than hide it behind a rule.
Registration, sign-in and the credentials that keep your account yours sit inside these notices. If someone uses your login with your consent or because you shared it, that activity is treated as yours. Keep your password to yourself, sign out on shared phones, and tell support the moment something looks wrong.
Deposits through bKash, Nagad, Rocket, Upay and bank transfer, plus the withdrawals you request, are covered by the notice on payments. We record every movement against your account. You are responsible for sending from a wallet in your own name, and we can ask for the details shown on the account page before a withdrawal is released.
The markets we list, Live Cricket Odds and Football Oddszone among them, plus the live tables, slot rooms and rounds like Crash or Cash, sit inside these notices. Corrections to a market, a void round or a settled bet follow the wording published with that title, so read it before you commit.
Your mobile wallet, your bank, your network and your device all live outside our pages, and each one runs on its own rules. We cannot rewrite a wallet provider's charges or a bank's processing decision. If a transfer failed outside our system, raise it with that provider first, then bring the reference to our support route.
Reading these notices is not the same as being stuck with them. You can ask to see the records we hold against your account, and you can ask us to correct a detail that is wrong: a misspelled name, an old phone number, an email address you no longer use. Do that from the account area so the change is tied to your login rather than to a message from an address we cannot match to you. If a deposit or withdrawal looks off, raise it with the reference number shown in your transaction list. We will check what our side recorded and tell you what we see. Where a question is about the notices themselves, what a clause means or how it applies to your situation, write to the support route published on the site and we will answer in plain terms. You can also close your account and ask what happens to your data afterwards. We will walk you through the steps the account page asks for; we cannot promise an outcome on a charge that sits outside our system.
Your account area lists the transactions, bets and sign-in activity we hold for you. Open it whenever you want to see what a deposit, a withdrawal or a settled bet looks like on our side. If something there does not match your own record, that mismatch is what support needs to hear about.
A phone number that has changed or an email you no longer read can lock you out of your own account. Update it from the account area while you are signed in. If a field is greyed out, that change needs support to make it for you, so ask, and we will explain why it is held.
Bring the reference shown against the transaction when you write in. It tells us which bKash, Nagad, Rocket or Upay movement you mean without a long back-and-forth. We will tell you what we recorded and what the wallet provider reported back to us.
If you want out, ask us to close the account and to explain what happens to the details we hold afterwards. Settle any balance and let open bets finish first, since the account page shows the steps for both. Asking us before you walk away keeps a pending withdrawal from being stranded.
When a question is about the notices rather than about a game, the support route published on the site is where it goes. Start on the account page: the contact points linked there are the ones we answer, and using them means your message arrives attached to your account instead of floating in as an anonymous message. Write with the facts. Tell us which clause you are asking about, what you expected, and what you saw instead, and add the reference number if a payment is involved. Vague messages about the terms cost you a reply cycle; a specific one usually gets a specific answer the first time. We do not publish a phone line for these questions, and we cannot give you a firm answer on a wallet provider's own decision, because that sits outside our system. What we can do is tell you what our records show, explain the wording you are reading, and point you to the account field or the published term that covers your case. If you think a rule was applied to you wrongly, say so plainly.
Signed in, the account page is the first place to take a query about your own position. It links the contact points we answer and keeps your message tied to your login. Ask about a transaction, a closed bet or a change to your details here before you write anywhere else.
For a question about the wording of these notices, use the support page linked from the site footer. Describe the clause and your situation in a sentence or two. That is the route for policy questions, so your message reaches the desk that owns the wording.
The form asks for your account email, a subject and your message. Attach the reference number when a payment is involved and pick the closest subject so it is routed rather than forwarded. Keep it short: one question per message gets a clearer reply.
Your account details are held so we can run the service you signed up for: keeping you signed in, settling your bets, moving money through your wallet and answering you when you write in. We do not sell your details on. Access to that data inside our own operation is tied to the job someone does, which is why a support agent sees your transactions but not the password you chose. Cookies do a narrow set of jobs here. They keep your session alive while you move between the sportsbook and the casino floor, remember that you have dismissed a notice, and tell us whether a page loaded properly on your phone. Blocking them will still let you read these pages, but signing in and holding a session will not work without them. We keep records for as long as the service and the applicable rules require, and no longer than we can justify. When you ask us to close an account, we tell you what has to stay on file and why. Requests to see, correct or remove your data go through the same support route.
When you deposit through bKash, Nagad, Rocket, Upay or a bank transfer, we hold the reference and the amount against your account so a query can be traced later. We do not keep your wallet PIN or your bank password, because those never reach us. What we see is the transaction a provider confirms.
Cookies here keep you signed in, remember dismissed notices and measure whether a page loaded on your device. You can clear them from your browser settings at any time; you will simply be asked to sign in again. Nothing about reading our pages depends on accepting them.
Your password, your device and your own habits do most of the work. Use a password you do not reuse elsewhere, sign out on a shared phone, and treat any message asking for your login as something to ignore. Support will not ask you for your password.
We keep account records only as long as the service and the rules that apply to us need them, then remove what we can. To see what we hold, correct a field or ask for removal, write in through the support route and tell us which account you mean.
The questions we get asked most about these notices are about access, records and what stays on your file. The short answers sit below; the full wording sits in the published notices themselves, and your account page shows how any of it applies to you. Query anything that reads differently for your region.
The notices you agree to when you register are linked from the footer and from the sign-up form itself. Read them alongside your account page, because the fields there show what applies to you. Anything that differs by region is flagged in the wording rather than assumed.
Registration depends on your local law and the eligible regions we can serve, so the sign-up form is the honest answer: if it lets you through, you are in a supported region. If it does not, we cannot accept the account, and we will not pretend otherwise.
We remove what we no longer need and keep what the rules require us to keep, such as transaction records tied to a settled bet or a withdrawal. Ask us and we will tell you which parts stay on file, and for how long, before you close anything.
Yes, transactions sit inside these notices, but the first check is with the wallet itself, because sometimes the money has not left the provider. If it has, send us the reference from your bKash, Nagad, Rocket or Upay transaction and we will compare it with our own record.
Any charge that comes from a wallet provider or a bank is theirs, not ours, and it appears on the provider's own record. The amounts that apply to your account are the ones shown where you start a transaction, so read them before you confirm, and ask support if something looks unfamiliar.
Write to the support route published on the site, describe what happened and what you expected, and include any reference number. We will explain which part of the notices applies and what we can do about it. If the matter sits with a wallet provider, we will say so.