Sports / Live
When you open an account with ck366, you share certain personal details with us — and this policy explains exactly what we collect, why we hold it, and what choices you have over it. Access to our platform depends on your local law and eligible regions, and we handle your information accordingly.
When you create an account, we collect the details you submit directly — your name, contact number, email address and the wallet identifiers you use for transactions, such as your bKash, Nagad or Rocket account references. We use this to verify your identity, process wallet top-ups and withdrawals, and keep your account accessible across sessions on your phone or browser. We also collect session-level data automatically: your device type, browser version, IP address and pages visited within ck366. This helps us detect unusual access patterns and keep your account secure. We do not sell your personal details to third parties. Where we share data — for example, with payment processors handling your bKash or Nagad transaction — it is only to complete the service you requested. Any third party we work with is bound to handle your data only for that stated purpose. We retain your information for as long as your account remains active, and for a period after closure as required by applicable rules. The exact retention period depends on jurisdiction-specific obligations, and you can ask us directly about records held on your account at any time through our support channel.
Used only to process your deposit or withdrawal request. We do not store your full bKash PIN or password — only the reference needed to complete the transaction you initiated.
Nagad transfer details are passed to the payment processor in encrypted form. Once the transaction closes, only a reference ID remains in your account history, not the full wallet credential.
Your Rocket payment history appears in your account transaction log. This record is held for account management and any dispute resolution you raise with our support team.
This policy covers data collected directly by ck366 through account registration, wallet activity and your in-session behaviour on our platform. It does not extend to third-party services you reach from our pages, and it does not apply to how payment processors like bKash or Nagad manage data on their own systems. Understanding the boundary helps you know exactly who to contact when you have a question about your information.
Login timestamps, device identifiers and session tokens generated when you sign into ck366 fall inside this policy. We use these to keep your account secure and to let you stay signed in across your phone and browser.
Transaction references linked to bKash, Nagad or Rocket top-ups and withdrawals are covered here. The full processing of those payments is governed by each payment provider's own terms, which sit outside our policy.
Game session logs — which titles you opened, how long you played — are held on our systems and covered by this policy. We use this data only for account history and any disputes you raise, not for profiling or resale.
Any service you reach by leaving ck366 — an external link, a payment app, a social login — is outside the scope of this policy. Those services operate under their own privacy terms, and we have no control over them.
You have real choices over the data we hold. The most direct route for most account holders is to log in and check your profile settings — your name, contact number and linked wallet references are visible there, and you can update them when something changes. If you find a detail that looks wrong and cannot correct it from your account page, our support team can make the update after verifying your identity. For a full record of what we hold — beyond what the account dashboard shows — you can submit a data access request through our support channel. We will respond with details of the information stored against your account. If you want to close your account and have data removed, you can raise that request the same way. We will confirm what can be deleted immediately and what we are required to retain for a set period under applicable rules. Availability of these rights depends on your local law and the eligible region your account falls under.
Log into your ck366 account and open the profile section. Your registered contact details, wallet references and recent transaction history are shown there without needing to contact support.
Update your name or contact number directly from the account settings page. For wallet-linked details like a bKash or Nagad reference, contact support so the change can be verified before it takes effect.
Send a data access request through our support channel with your account email. We will compile the information we hold and share it with you, subject to any retention obligations under applicable local rules.
Raise a closure request via support. We will confirm which data is deleted straight away and which records must be kept for a defined period as required by the rules that apply to your account's region.
If you have a question about how we handle your data, the fastest route is through our live chat or email support channel. For wallet-specific queries — such as a transaction record linked to your bKash or Nagad account — include your account email and the date of the transaction so we can locate the record without delay. We aim to respond to data-related questions promptly, though response times depend on queue volume.
Open the live chat icon from your account dashboard after login. Describe your data or privacy question and our team will locate your account record and respond directly.
Send your data access or correction request to our support email address listed in your account help section. Include your registered contact number so we can verify your identity before making any changes.
Your account dashboard contains a dedicated help area with links to submit privacy-related requests. It also shows the current status of any open support ticket you have raised about your data.
We apply access controls to limit who within our team can view your account data, and transmission between your device and our platform is encrypted. Cookies are used to maintain your session state — so when you return to ck366 on your phone, you stay logged in without re-entering your details each time. You can manage cookie preferences through your browser settings, though disabling session cookies will affect how the account functions. Data we no longer need for account operations is deleted on a schedule governed by applicable rules for your region. For any change to this policy, we will post the updated version on this page, and the revision date will be shown at the top. If a change affects how we use your wallet data — such as the bKash or Nagad references linked to your account — we will notify you through the contact detail registered on your account before the change takes effect.
All data sent between your device and ck366 is encrypted in transit. This applies to account login, wallet references and transaction requests, whether you are on mobile or a desktop browser.
We use cookies to keep your session active after login. No personally identifying information is stored in the cookie itself — it holds only a session token that expires when you log out or after a set period of inactivity.
Account data is held for as long as your account is active and for a defined period after closure. The exact schedule depends on the rules applicable to your region. You can ask our support team about retention periods for your specific account.
When this policy is updated, the new version is published on this page with a revised date. For changes that affect how we use your bKash, Nagad or Rocket wallet references, we will contact you at your registered address before the change applies.
These are the questions our account holders ask most often about how we collect, store and handle their data. If your question is not answered here, reach us through the support channel in your account dashboard.
We share your data only where it is needed to provide the service — for example, passing a wallet reference to a payment processor handling your bKash or Nagad transaction. We do not sell your data, and any third party we work with is restricted to using it only for the stated purpose.
A transaction reference ID is stored in your account history so you and our support team can locate the record if needed. Full wallet credentials — your PIN or password — are never stored on our systems. The payment processor handles those details under their own security terms.
Log in and open your profile and transaction history pages — those show the most common account records. For a complete summary of all data we hold, submit a data access request through our support channel with your registered email, and we will compile and share the details with you.
Yes. Raise a closure and deletion request through support. We will confirm which records are removed straight away and which must be retained for a period under the rules applicable to your region. Availability of full deletion depends on your local law and the eligible region your account falls under.
We use session cookies to keep you logged in across pages and to remember your account state on your phone. You can disable cookies through your browser settings, but doing so will affect how your account session works — you may need to log in again each time. No personal wallet data is stored in a cookie.
The updated policy is published on this page with a revised date shown at the top. If a change affects how we handle your wallet data — such as your Nagad or Rocket account references — we will send a notification to your registered contact detail before the change takes effect.