Live / Sports
go666 operates under terms that govern how your account, transactions and site access work. Whether you use bKash, Nagad or Rocket to manage your wallet, the legal framework here sets out your rights and our obligations — availability always depends on your local law and eligible region.
Our terms set the conditions under which you open and use a go666 account. They cover how we collect and handle account data, what you can expect when you transact through local payment routes like bKash or Nagad, and the rules that apply when you access game content from studios including Pragmatic Play, Habanero and Microgaming. These terms do not establish a legal claim on behalf of any specific jurisdiction — access and eligibility depend on the law where you are located. If local law in your region does not permit access to this kind of platform, these terms do not override that. Where we refer to transactions, we mean account-wallet activity recorded in your go666 account history — not a guarantee of any particular processing outcome. You can review the terms at any time from your account settings. If anything in the policy is unclear, our support team is reachable through the channels listed on this page. We update these terms when material changes occur and note the revision date at the top of the policy document. Continuing to use the account after a revision means you have read and accepted the updated version.
This policy applies to your go666 account and the activity tied to it. It draws a clear line between what falls inside our responsibility and what sits outside it, so you know exactly where to direct a question.
The terms apply to your personal go666 account — login, wallet balance, transaction history and account settings. Any action you take while signed in falls inside this scope. Shared or transferred accounts are not covered and are not permitted.
Deposits and withdrawals processed through bKash, Nagad or Rocket are covered by our payment terms. The record visible in your account history is the reference point for any transaction query. External wallet fees set by those providers fall outside our control.
Game content from studios such as Pragmatic Play, Habanero and Microgaming is covered at the platform level — meaning our terms govern how that content is presented to you. Individual game rules displayed inside each title are set by the studio, not by us.
Services operated by third parties — including payment providers, device manufacturers and any linked external site — are outside the scope of this policy. We are not responsible for their terms, privacy practices or service availability. Check each provider's own policy separately.
You have practical choices available at every stage of your account. Reviewing your own data is straightforward: open your account dashboard and navigate to the transaction history or account details section — everything recorded against your account is visible there. If a detail is wrong — say, a name, contact number or wallet reference — you can request a correction through the support team rather than editing directly, so the change is logged correctly on our side. Raising a policy question does not require you to close your account or escalate immediately; the first step is always to message support with the specific section you want clarified. We aim to acknowledge policy questions and account-detail corrections through the same contact routes we publish. Account closure is also your right — if you choose to close, the request goes through our support channel and we retain only the records we are required to keep.
Your transaction history and account details are visible inside your signed-in account. Navigate to the account or wallet section to see what is recorded — no separate request is needed to view your own data.
If your name, contact or wallet reference needs updating, contact support with the correct information. We log corrections formally so your account record stays accurate and traceable.
If a section of our terms is unclear, message support and quote the relevant part. You do not need to escalate or close your account to ask a question — we handle policy queries through the same published contact routes.
Closing your account is your right. Submit the request through our support channel. We retain only the records we are obligated to keep and will confirm when the closure is processed.
Policy and account questions go to the same support routes we publish on the site. Choose whichever channel works for you — there is no separate legal department contact; all queries come through the routes below and are directed to the right team.
Open the live chat widget from any page on go666 to ask a policy or account question in real time. This is the fastest route for account-detail corrections or transaction queries tied to bKash or Nagad.
Send a detailed policy question or account closure request to the support email address shown in the site's contact section. Include your account reference and the specific policy point you are asking about so we can respond accurately.
The help centre on go666 covers common policy questions, account steps and transaction queries. Check there first — many questions about scope, rights and wallet records are answered in published articles without needing to open a live chat.
Account data is held and used only for the purposes described in our policy — running your account, processing wallet activity and handling support requests. We do not sell or share personal data with third parties outside the operational relationships needed to run the platform.
We use cookies to keep your session active and to remember account preferences. You can manage cookie settings through your browser at any time. Disabling certain cookies may affect how account pages load on your mobile device.
Your account login is protected by the credentials you set. We do not store payment PINs or wallet passwords. If you suspect unauthorised access, contact support immediately through live chat and we will walk you through the account-lock steps.
We keep account and transaction records for as long as required by the operational and legal obligations that apply to us. After account closure, we retain only what we are obligated to retain — not your full activity history indefinitely.
To request a change to how your data is used, or to ask what records we hold, contact our support team by email with your account reference. We handle data requests through the same published routes as all other account queries.
These questions cover the policy points we hear most often from account holders in Bangladesh. If your question is not here, the live chat and email routes above are the right next step.
Access and eligibility depend on your local law and the eligible region. Our terms govern your account if you are able to use the platform legally where you are located. We do not override local law — if local rules prohibit this kind of service, our terms do not change that.
The full policy is published on go666 and accessible without logging in. You can also find a link to it inside your account settings once you are signed in. The revision date at the top of the document shows when it was last updated.
Contact support through live chat or email with the correct information and your account reference. We process corrections formally so the change is logged against your account record. Direct self-editing of certain fields is restricted to keep your account history accurate.
Transaction records tied to your bKash, Nagad or Rocket wallet activity are part of your account history. After closure, we retain only the records we are legally obligated to keep. You can request a summary of your transaction history before closing the account.
Yes. Send a data query to our support email with your account reference and we will respond with the relevant details. We handle these requests the same way as any other account query — through the published contact routes, not a separate process.
Start with our live chat or support email — quote the specific policy section and explain what you disagree with. Our team will review it and respond through the same channel. There is no separate escalation address; all policy disputes begin with the same published support routes.