Slots / Mobile
Our Terms & Conditions set out what a 777gb account gives you and what we ask in return, from your sign-in steps to the way your wallet records are kept when you use bKash, Nagad, Rocket, Upay or bank transfer. Access depends on your local law and eligible regions, so the opening clause on this page is worth reading first.
These Terms are the agreement between you and 777gb when you open and use an account. They are written to be read once, not skimmed. Where anything in them meets a rule that applies in your region, the stricter of the two applies, and access to some parts of the platform depends on your local law and eligible regions. Nothing here is a promise about outcomes. We describe the account route, the wallet steps and the published support path as they exist on this site, and we ask you to follow the fields, limits and verification instructions shown inside your own account rather than any third-party claim about them. You stay in control of the account you opened. Keep your sign-in details to yourself, use the device you normally use, and tell us through the published support route if something on the account does not look right. If we change these Terms, the version live on this page is the one that applies, and we keep a record of the wording so you can see what moved. Payments sit inside this policy too. When you move money with bKash, Nagad, Upay, Rocket or bank transfer, the wallet provider's own rules run alongside ours, and their confirmation records are what your account reconciles against. We do not control, and do not speak for, the wallet or bank handling the transfer. If any clause here is unenforceable where you live, the rest of these Terms stand.
These Terms follow your account, not the whole internet. They cover the sign-in you use to reach the lobby, the wallet activity recorded against your profile, the house rules for slots, live casino tables and our cricket-led sportsbook, and how we handle the details you give us. They do not cover a wallet app's own screens or a bank's own process. Picture the split by where you stand. Inside the lobby, opening Crash Velocity, a Baccarat Viproom table or a Bangladesh Live Room 507 seat, our rules apply. Inside bKash, Nagad, Upay or Rocket confirming a transfer, their rules apply, and we only see the record they pass back to your account. Third-party links are the clearest case. Tap out to something we do not run and that site's own terms take over, so treat those pages as you would any unknown site. Everything else falls outside this policy, and access to any part of the platform depends on your local law and eligible regions.
Covered. Everything from the sign-in route to the profile details saved against your name sits inside these Terms. If a device you do not recognise turns up in your own records, raise it through the published support route so we can look at the account activity alongside you.
Covered, with a boundary. bKash, Nagad, Upay and Rocket transfers you make to your account are recorded here, and your transactions are what we reconcile against. The wallet's own screens, its confirmation wording and its internal checks stay under the wallet provider's terms.
Covered. House rules for slots, live casino tables and the sportsbook sit in these Terms, including how a round is settled and where you read the outcome. Cricket-led markets are part of that picture, with Cricket Live Lines sitting beside our table rooms and slot titles.
Outside. Links out to a payment page, a stats source or any other site leave this policy behind, and that site's own terms, cookies and data practice apply from the moment you land there. Read them the way you read ours.
Agreeing to these Terms does not end your say. Four moves stay open to you at any point, and none of them needs a special request. Start with your own records. Sign in, open the transaction list for your wallet, where bKash, Nagad, Upay, Rocket and bank transfer entries all land in the same history, and check each line against the confirmation the wallet sent you. If a line does not match, that is exactly the sort of thing we want to hear about. Your profile details are editable from inside the account, so keep your contact route current, because a stale number or address is the usual reason a check stalls. When your question is about a clause rather than a payment, raise it through the support route published on this site and quote the section you are reading, which saves us both a round of messages. You can also end the arrangement. Close the account from inside the signed-in area and we handle the record as this policy describes. Access and eligibility still depend on your local law and eligible regions.
Sign in, open the transaction list and compare each line with the confirmation your wallet sent. bKash, Nagad, Upay, Rocket and bank transfer entries appear in the same history, so one pass covers all of them. Flag anything that does not line up.
Your contact route lives in your profile and you can change it yourself once signed in. Keep the number you actually carry current, because that is the route a check comes back on, and an old one is the most common reason a follow-up stalls.
Paste the section you were reading into your message when you contact support. Quoting the wording lets us answer your actual question instead of a general one, and it keeps the back-and-forth short. The support route is published on this site.
If you no longer want to use your account, the closing route sits inside the signed-in area rather than behind a phone call. Once you take that step, we keep and handle the record the way this policy sets out, and you can ask what is held.
Terms questions are ordinary questions, and they get treated that way. If a clause reads oddly, if a wallet record does not match, or if you are unsure whether something is covered, use the support route published on this site rather than a channel someone passed you in a group chat. Write down what you were doing, the section of these Terms you had open or the wallet transfer you were checking, and send it in one message. Specific beats long: a line about a Nagad transfer missing from your history is easier to act on than a paragraph about something being wrong. Keep the messages inside the account where you can. It means your account context travels with the request, and the reply lands somewhere you can find again. We do not publish a fixed response time, and we would rather say that plainly than invent one. Anything you send us about the account is handled under this policy, and access to any part of the platform still depends on your local law and eligible regions.
The contact path we publish on this page is the one staffed for account and terms questions. Use it for clause wording, wallet record mismatches and access problems. Do not rely on a phone number or link a stranger shared, because we cannot vouch for where it takes you.
Writing from inside your account keeps your profile, wallet history and earlier messages in one thread. It saves you explaining the background twice, and it gives us the transaction record we need in order to trace the actual entry you are asking about.
When a transfer question comes in, the confirmation your wallet shows is the reference point. Have it beside you for bKash, Nagad, Upay or Rocket, and make a record of the amount and time it displays, so we can line it up with your account history.
What you hand over when you open an account is the part of these Terms we move slowest on. Profile details, wallet history and support messages are held so we can run the account and answer you when you ask what is on file. Cookies do a narrower job than people expect. They keep you signed in between pages and remember how you like the site to display, so the lobby does not reset every time you open a tab. They do not follow you around other sites. Keeping the account closed is mostly your routine, with ours behind it. Sign in on the device you normally use, keep your details off shared screens, and sign out when you hand the phone to someone. If your history looks off, tell us early. Retention is the last piece. We keep account and transaction records as long as this policy and applicable record-keeping rules require, then remove them. You can ask what is held about you and request a correction through the published support route.
Profile details and wallet history are held against your account for as long as the record-keeping this policy describes requires, then cleared. You can ask what is on file and request a correction at any point through the support route published on this site.
Cookies keep you signed in between pages so the lobby does not reset on every tab. They also store display choices. They do not follow you onto sites we do not run, and clearing them simply means signing in again the next time you return.
Your sign-in details are the first lock, and the one only you hold. Use your own device, avoid saving credentials on a shared handset, and sign out when you pass the phone over. If your history shows something you did not do, say so early.
Requests about what we hold go through the published support route, from inside the account where you can. Say what you want changed and we work through the record with you. Access to the platform still depends on your local law and eligible regions.
Most of what comes in about these Terms falls into the same handful of questions, so here they are in one place. If yours is not among them, the support route published on this site is the way to ask, and quoting the section you were reading gets you a sharper answer. The pattern behind the answers is simple. We describe what our own account, wallet and lobby routes do, and we leave the parts we do not control, such as a wallet's internal checks, a bank's own process, or the law where you live, to the people who do control them. Nothing here overrides a rule that applies in your region. Where an answer touches payments, the wallet's own confirmation is the record to keep. Where it touches account access, sign in and look before you write. Where it touches eligibility, remember that access to any part of the platform depends on your local law and eligible regions.
Yes. Opening an account and staying signed in means you accept the wording on this page as it stands today. If you disagree with a clause, the practical option is to step away from the account and close it from inside the signed-in area rather than carry on while unhappy with it.
Keep the confirmation your wallet gave you, whether that was bKash, Nagad, Upay or Rocket, then check your transaction list again after signing in. If the entry is still missing, send the wallet confirmation details through the published support route so we can line it up against your account record.
Yes, from inside your profile once you are signed in. Keep your contact route current, because that is the number or address a follow-up comes back on, and an out-of-date one is the usual reason a check sits unresolved. Anything the profile will not let you edit, ask support to change.
Wallet apps, bank processes and any site we do not run sit outside this policy. Their own terms and data practice apply the moment you are on their screens. Everything you do inside the lobby, your account and your wallet records sits inside ours.
We hold account and transaction records for as long as this policy and applicable record-keeping rules require, then remove them. You can ask what is held about you and request a correction through the support route published on this site, writing from inside your account where you can.
Use the support route published on this site rather than a number or link from a group chat, which we cannot vouch for. Quote the section you were reading, so the reply addresses your actual question instead of repeating wording you already have in front of you.