Sports / Mobile
This page sets out the record cn6666 keeps on your account: the sign-in detail you give us, the device you reach us from and the wallet route you fund through. Read it once and you know what sits with us, how long it stays and where to send a request to change it.
This policy covers cn6666 and the account you open here, and nothing beyond that. Where it sits legally depends on your local law and eligible regions — the rules on what a site may collect, how long it may keep it and what it must tell you differ from country to country, and we follow the version that governs where you are. That is why the wording stays practical rather than quoting a statute you would have to look up. What we hold is narrow. Your account details, the mobile number or email you sign in with, the device and browser behind that session, and the payment route attached to your wallet — bKash, Upay or Bank Transfer — sit in one record. We do not gather more than that record needs, and we do not sell it to anyone. Two things to know before you read on. When you start a deposit, that transfer passes through the wallet or bank you chose, and their own terms cover their side of it. And this page changes when our process changes: the text here is the version in force, so check it before relying on a copy you saved earlier.
A policy is only useful when you can tell what it does not touch. Ours follows your account record: the sign-in detail you give us, the device and browser that carried the session, and the payment route attached to your wallet. That is the core. Around it sit the lobby pages you open, which tell us what loaded properly on a phone screen, and the deposit instructions you follow, which tell us a transfer was started. What we never see is the other side of a bKash, Upay or Bank Transfer payment — the wallet balance, the statement line, the identity checks those services run. Those belong to the provider. The four blocks below split this out, so you can see which record sits with us, which sits with someone else, and which document to open when something looks wrong.
Sign-in details, the mobile number or email you use, and the device and browser that carried the session. This is the record we match when you raise a question, which is why keeping the sign-in detail current matters more than any other single update you make.
When you start a deposit through bKash, Upay or Bank Transfer, we record that the route was opened and what came back. The wallet balance, the statement line and the identity checks behind them stay with that provider, under their own terms.
Pages you open, game categories you browse and notices you read inside the lobby. This tells us which parts of the site work on a small screen and which do not, and it stays tied to your account rather than being sold on.
Anything outside our account record — the payment provider's own app, a site you reach from a link — runs on that company's policy, not this one. We can tell you where our part ends; we cannot change what they do with what they hold.
You do not need a reason to ask what we hold about you. Send the request through the support route published on this site, say what you want to see, and we work from your account record rather than asking you to rebuild it from memory. Most requests fall into the four buckets below. Some are straightforward — correcting a saved mobile number, for example, so a confirmation reaches the right device. Others need care: a removal request can close parts of your account that depend on that record, and where local law requires us to keep a transaction line for a set period, we will tell you that instead of deleting it. Either way you get an answer tied to your own account, not a copied clause. Include the sign-in detail you used so we can match the request quickly. Which options apply to you depends on your local law and eligible regions.
Ask for the account record we keep on you and we will show what sits in it: sign-in details, device history, wallet route and transaction lines. Bring the sign-in detail you used, so we match the request to the right account without a back-and-forth.
A mobile number that changed, a device you no longer carry, a wallet route you want swapped — tell us and we update the record. Correct details are what let a confirmation reach you instead of an old handset sitting in a drawer.
If a paragraph here reads oddly or does not match what you expected, say so through the support route. You get an answer about your own account rather than a pasted clause, and if the wording itself is unclear we would rather hear it.
You can request that we remove what we are not required to keep. Some transaction records stay for the period local law sets, and we will name those rather than promise a clean delete we cannot deliver on.
A privacy question moves faster when it lands in the right place, so we keep three visible routes on this site and nothing buried behind a phone tree. Pick the one that matches what you need. A question about what a paragraph in this policy means goes to the support form. A question about your own record — a stale mobile number, a device you no longer use, a wallet route you want changed — goes through the account help area, because we have to match the request to a signed-in account before we act on it. Anything touching a payment provider's own records starts in the same place, and we will point you onward from there. We do not print hours we cannot keep, so treat the reply you receive as the timeline rather than a number written on a page.
The form published on our support page is the entry point for anything about this policy. Write in plain English, mention the section you are asking about, and include the sign-in detail attached to your account so the reply lands on the right record.
Signed-in requests about your own data — a stale number, an old device, a wallet route — move faster here, because we can see the account as you do. Open the help area from your account menu and follow the fields shown there.
This page and the terms sitting alongside it are the version in force. If a request involves a payment provider's own records, start with us anyway; we will tell you which document on their side to open instead of sending you in circles.
Three kinds of data keep an account working here: the cookie that holds your session between pages, the device and browser details that tell us where a sign-in came from, and the transaction lines tied to your wallet. We use the first so you are not re-entering details every time you move from the lobby to your account, and the second to spot a session that does not match how you normally reach us. Device continuity is the cheapest protection an account has, and it is the one we lean on. Cookies you can clear whenever you like; you will simply sign in again. Records stay while your account is open, and for whatever period local law requires afterwards. If we change how any of this works, this page changes with it, and the text you read here is the one in force.
A cookie keeps you signed in between pages, so switching from the lobby to your wallet does not mean typing your details again. Clear cookies in your browser and the session ends; nothing else about your account changes, and you simply sign back in.
We check whether a sign-in matches the phone or browser you usually use. A session from an unfamiliar device is where account trouble tends to start, so that single check does more for you than any password rule printed on a page.
Your account record stays while the account is open, and transaction lines stay for the period local law requires after that. We do not promise a deletion timeline we cannot control, because part of that clock is set outside this site.
When our handling changes, this page changes with it, and the current text is the one that applies to your account. If you saved an older copy, check back here before relying on it — an out-of-date clause helps nobody.
These are the questions that reach us most, answered the way we would answer them at a cashier desk. If yours is not here, the support form on this site takes it, and a person reads it with your account record open rather than reaching for a script. Payment availability, account options and what we are able to store can differ by market, so where an answer touches access or eligibility, treat your local law and eligible regions as the deciding factor. Nothing on this page widens what we collect or shortens what you can ask us to correct.
Your account record: the sign-in details you give us, the device and browser you reach us from, the wallet route you fund through and the transaction lines that come back. It also covers the lobby pages you open. It does not cover what bKash, Upay or your bank holds on their side.
Yes. Ask through the support route on this site and we will show what sits in your record. Have the sign-in detail you used ready, because that is how we match a request to an account and avoid handing anything to the wrong person.
A deposit has to pass through the provider you chose, so the details that transfer needs go to them, and their own terms apply from that point. We do not hand your account record to anyone else for their own use, and we do not sell it.
They matter more, because a phone is the device you carry everywhere. The cookie is what keeps you signed in between the lobby and your wallet; clear it and you sign in again. Device details also help us notice a session that does not look like your usual one.
Send the request through the account help area with the detail you want changed. Corrections are usually simple. Removal depends on what the record is — transaction lines tied to local law have to stay for their period, and we will name those rather than promise a full wipe.
It applies to the account, not the handset, but a shared phone changes who can reach that account. Sign out when you finish, and if a device in your record looks unfamiliar, raise it through the account help area so we can look at the session with you.