Mobile / Live
ck22w collects only the account and transaction data needed to keep your session running and your wallet records accurate. This policy explains what we collect, why we hold it, and what choices you have — clearly, without legal padding.
When you open an account with us, we collect the information you provide during registration — your contact details, login credentials and, where relevant, the payment method you use to transact. For Bangladesh, that includes transaction references tied to Nagad, Rocket and Upay wallet activity. We use this data to verify your account, process wallet requests and keep your session history available when you return. We do not sell your personal data to third parties. We do not share it beyond what is operationally necessary to run the platform or to meet any applicable legal obligation in the regions where access is permitted. Data held on our servers is subject to access controls, and your account password is stored in a form that cannot be read back in plain text. Cookies and similar browser signals are used to maintain your logged-in session and to understand how the mobile interface is being navigated — not to build a profile for advertising. This policy applies to data collected through the ck22w website and mobile browser session. Access to, and use of, this platform depends on your local law and the eligible regions we serve.
Not every piece of data or every service falls under this document. Understanding the scope helps you know exactly what we are responsible for and where a third party's own terms take over. This distinction matters especially when your Nagad or Rocket wallet is involved, because the payment provider operates under its own privacy framework.
Login activity, session tokens and device identifiers collected when you access your ck22w account through a mobile browser or desktop are fully within this policy. We control how that data is stored and for how long.
Deposit and withdrawal references linked to Nagad, Rocket or Upay appear in your account wallet history. We hold these records on our side. The payment provider holds its own copy under its own terms, which are separate from this policy.
Pages you visit, game lobbies you open and sports sections you browse generate navigation data. We use this to keep the mobile interface consistent across return visits — not to share browsing behaviour with advertisers.
Links to external sites, embedded studio content from providers in our lobby, and third-party payment gateways are governed by those parties' own policies. Once you leave our platform or interact with a third-party frame, this policy no longer applies.
You have several concrete options when it comes to the data we hold on your account. None of these require specialist knowledge — each one starts from within your signed-in account area or through a direct message to our support team. If you believe a record in your account is wrong — a transaction amount, a registered phone number, an email address — you can raise a correction request. We will check the record against our transaction logs, including any Nagad or Rocket reference tied to that entry, and update what can be verified. If you want to understand what data we hold for your account specifically, you can submit a data enquiry. We will respond through the contact route you used to reach us. If your account is no longer active and you want to ask about data removal, contact support with your account identifier. Removal requests are assessed against any retention obligations that apply in the regions we operate. These rights apply subject to your local law and the eligible regions covered by this platform.
Open your signed-in account area to see your transaction history, registered contact details and current session information. This is the fastest way to check what we hold without contacting support.
If a phone number, email or payment reference is recorded incorrectly, raise it through the support channel. We verify corrections against the original transaction log before making any change.
Send a message to our support team asking what personal data is held for your account. Respond with your registered contact detail so we can confirm your identity before replying.
Accounts that are closed or inactive can request data deletion. We process removal requests in line with any applicable retention period required in eligible regions, and confirm the outcome in writing.
If this policy raises a question you cannot resolve through your account settings, our support team is the right route. Use the channel that suits you — the response goes back to the same address or number you used to contact us, so keep that consistent with your registered account detail.
Open the chat widget from any page on ck22w while signed in. State that your question is about account data or privacy and the team will route it correctly.
Send your privacy or data question to the support email address published in the contact section of our site. Include your registered account identifier so we can locate your record.
The account help section within your signed-in dashboard includes a direct form for data and privacy queries. This form pre-fills your account detail, which reduces back-and-forth on verification.
We keep your account data behind access controls that limit which internal processes can read it. Passwords are hashed before storage — we cannot retrieve your password in plain text, and neither can anyone else reading our database. Cookies placed on your device are session-functional: they keep you logged in across page loads and remember your mobile browser preferences on return visits. We do not use tracking cookies for advertising. Retention periods vary by data type — active account data is held while your account remains open; payment reference records are kept for as long as required by any applicable legal obligation in the regions we serve. If you want to know the retention period for a specific data category, ask through the support routes above.
Your login password is hashed at the point of entry. We store only the hash, not the original password. Even internal processes cannot read your password back in its original form.
Session cookies keep your login active across page changes on mobile and desktop. We do not place advertising or cross-site tracking cookies. You can clear cookies through your browser settings at any time.
Nagad, Rocket and Upay transaction references tied to your wallet are retained in line with applicable legal requirements for the eligible regions we serve. The exact retention window depends on regional obligations.
When this policy changes in a material way, we publish the updated version at this address and note the change date at the top of the document. Continuing to use the site after a change means you have seen the updated terms.
The questions below cover the situations that come up most often when you want to understand how your account data is handled. If your question is not here, the support routes in the section above are the right next step.
We collect the contact detail and login credentials you enter at registration. If you add a payment method, the reference data for that wallet — such as a Nagad or Rocket number — is associated with your account. We do not collect payment credentials directly; those stay with the payment provider.
We do not sell your personal data. We may pass limited information to payment processors — for example, when confirming a Rocket or Upay transaction — but only what is operationally necessary. Any such sharing is subject to the processor's own terms and applicable legal requirements in eligible regions.
Open your signed-in account area first — your registered details, transaction history and current session data are visible there. If you need a broader view of what we hold, submit a data enquiry through the support chat or email, including your account identifier.
Yes. If your account is closed or inactive, contact support with your account identifier and a deletion request. We process these requests against any retention obligations that apply in the regions we operate, then confirm the outcome to your registered contact address.
Cookies on this site are session-functional — they keep your login active and remember mobile browser preferences. We do not use advertising or cross-site tracking cookies. You can remove or block cookies through your browser settings, though doing so may interrupt your logged-in session.
This policy governs data collected through the ck22w website and mobile browser session. Access to the platform depends on your local law and the eligible regions we serve. If local law in your location restricts use of this type of platform, that restriction applies and this policy does not override it.