App / Sports
cx6666 is a casino lobby built for Bangladesh, and this Privacy Policy sets out in plain terms what we hold about your account, why we hold it and what you can ask us to change. Open an account when you are ready — the wording here applies to every screen you reach after signing in, from the game catalog to the wallet pages where bKash, Nagad, Rocket and Upay activity is recorded.
Nothing here hides behind jargon. Our privacy posture is simple to state: we collect what an account needs to work, we keep it inside the systems that run cx6666, and we tell you where to look when you want to see or change something. Access to the lobby, and to the local payment rails shown on our wallet pages, depends on your local law and eligible regions, so what you see while signed in is the final word for your account, and this page works alongside those screens rather than replacing them. Where local rules add obligations, those rules come first, and we adjust how we handle data to match them. Where a question is left to your own choices, the screens in your account area are where you act: reading what we hold, correcting a detail, or asking us to look at something again. We do not sell account data. What we share is limited to what is needed to complete a transfer you asked for, or to answer a question you raised through our published contact route — nothing beyond that. Payment habits and local rules both change, so we revise this page from time to time. When we do, the wording here replaces the earlier version and the date on the page marks when that happened. Cash-in and cash-out steps through bKash, Nagad, Rocket, Upay or bank transfer leave their own records inside your account wallet, and those records follow the same rules described here.
This policy comes into force when you first open our site and stays with you while your account is active. It covers what we do with data across cx6666 — nothing more and nothing less. Accounts you hold elsewhere, wallets you keep on your own handset and pages run by another company sit outside it. If you are unsure whether something belongs here, the short answer is this: if you reach a screen after signing in, it is ours to explain; if a different company's name appears on the page, their rules apply there. A transfer you start inside bKash, Nagad, Rocket or Upay begins in an app we do not run, and our part of the story begins when that transfer reaches your account wallet. Access and eligibility still depend on your local law and the eligible regions we serve, and the four areas below are where that distinction matters most.
Your sign-in details, the email address tied to your account and the profile details you fill in sit inside this policy. When you update a phone number or an address, the change flows through the same account area, and the record we keep matches what you entered.
Every move you ask for through bKash, Nagad, Rocket, Upay or bank transfer leaves a record in your account wallet, and those records are covered here. What happens inside the wallet app on your phone, before the money reaches us, follows that provider's own policy.
The catalog you browse — slots, live tables, crash titles and cricket-led sportsbook markets — lives on pages we run, so the way we handle data there falls under this policy. Cookies that keep your session running through the catalog sit in the same group.
Links that lead away from our pages, and any app you install from somewhere else to manage your money, sit outside our control. We cannot describe or change how those services treat your data, so read their own policy before you share anything with them.
You are not stuck asking us to explain things twice. The signed-in area of your account is where most of this happens on your own: the profile screen shows the details we hold, and editing them there is the quickest way to correct a spelling mistake, an old phone number or an email you no longer use. Anything you cannot change yourself — a record tied to a transfer, a detail attached to a closed session — is a question for our published contact route, and you can raise it as soon as you spot it. If you want to know what we hold, say so plainly and tell us which part of the account you mean; a specific question gets a specific answer. If you would rather hear from us only when something needs your attention, sign-in settings are where you turn the extra messages off. The current wording of this policy stays on this page, so you can read it whenever you want without asking us for it.
Open your profile while signed in to fix a name spelling, a phone number or an email address. The change lands straight away, and the account area shows what we now hold, so you can see the updated detail yourself rather than waiting on a reply.
Send a specific question through our published contact route, and say which part of the account you mean — a wallet record, a session, or the profile itself. A precise question is easier for us to answer accurately, and we reply through the same route you used.
Sign-in settings control the messages we send about the lobby and your account. If you would rather hear from us only when something needs your attention, that preference lives there, and you can change your mind whenever you like.
This page carries the wording that applies to your account today, across every region we can serve. If an older copy you saved reads differently from what you find here, the version on this page is the one that counts, and it stays readable without asking us.
Privacy questions are not an emergency, but they should never feel like a dead end either. One contact route is published on our site, and anything about your data should go there — whether you want to correct a detail, ask what we hold, or flag something that looks wrong in your account wallet. Start your message with the email address registered to your account, because that is how we tie a question to the right records without asking you to send anything sensitive. Describe the screen you were on and what you expected to see; a short, accurate picture usually saves a round of messages. If your question is about a transfer through bKash, Nagad, Rocket, Upay or bank transfer, mention the wallet and the date shown in your account area, and we can look at the matching entry. Anything touching access or eligibility depends on your local law and the eligible regions we can serve, and we will say plainly if a request falls outside what we can do.
Use the contact link shown on our site for anything connected to this policy. Write from the email address registered to your account so we can find the right records, and keep the message specific about the screen or the entry you are asking about.
Many questions answer themselves once you sign in: the profile screen shows the details we hold, and the wallet area lists the bKash, Nagad, Rocket or Upay activity recorded against you. Look there first if you only need to check a detail.
If you are unsure whether you can hold an account where you live, ask before you deposit. Access depends on your local law and the eligible regions we can serve, and we would rather answer that question up front than after a transfer.
Data handling at cx6666 follows the same logic as the lobby itself: keep it visible. Account details, wallet records and the sessions you play stay inside the systems that run the site, and they reach only the people and services that need them to answer you or complete a step you asked for. Nothing sits in a folder you cannot ask about. Cookies do a narrow job here. They keep you signed in between pages and remember small choices so you are not re-entering the same preference on every visit; they are not there to build a picture of your day. Your account security rests on details you choose, so guard your sign-in credentials, keep the email address on your profile current, and tell us through the published contact route if a wallet entry or a session looks unfamiliar. Records stay while the account needs them and for the periods local rules set, then they go. If you want something corrected or explained, the request starts the same way every time — a message from your registered email.
Account details, wallet records for bKash, Nagad, Rocket, Upay and bank transfers, and the history of the sessions you play. We keep these together so a question about one entry can be answered without you having to repeat the whole story from the beginning.
Cookies keep you signed in as you move between the catalog and your wallet, and they remember small choices so pages behave the same on your next visit. You can clear or block them in your browser, though parts of the account may then ask you to sign in again.
Your sign-in details protect everything inside the account area, so keep them to yourself and update the email address on your profile if it changes. If a wallet entry or a session looks unfamiliar, tell us through the published contact route rather than waiting.
Records stay while your account is open and for the periods local rules require, after which they are removed. If you want a detail corrected or explained, send the request from your registered email so we can match it to the right account.
It covers what we hold about your account — profile details, wallet records for bKash, Nagad, Rocket, Upay and bank transfers, and your session history — plus the cookies that keep you signed in. Pages run by other companies sit outside it.
Yes. Sign in and open your profile to see the details on file, and check the wallet area for the payment activity recorded against you. If you need something explained rather than displayed, send a question through the published contact route we show on the site.
Open the profile screen while signed in and edit the field yourself. Your change applies to the account and the updated detail appears straight away. If a correction is not something you can make there, ask us through the published contact route.
Account data stays inside the systems that run the site. What we pass on is limited to what is needed to complete a transfer you asked for or to answer a question you raised — the wallet you chose and the record matching it, for example. We do not sell account data.
It applies whenever you use cx6666, wherever you are reading from. Whether you can hold an account at all depends on your local law and the eligible regions we can serve, so check that before you deposit. If something is not available to you, we will say so plainly.
Write to us through the contact route published on our site, using the email address registered to your account. Describe the screen or entry you mean — a wallet record, a profile detail, a session — and we will take it from there.
Yes. When payment habits or local rules shift, we update this page and the revised wording replaces the earlier version, with the date on the page marking that change. Access conditions continue to depend on your local law and the eligible regions we serve.