Slots / Casino
This page sets out the legal framework that governs your use of ckl44, including how we handle your account, your data, and the choices available to you. Access to our platform and its features depends on your local law and the eligible regions we serve.
ckl44 operates as a private member platform. Whether you can access specific features depends entirely on the laws that apply in your location and whether your region falls within our eligible service areas. We do not make blanket availability claims, and we do not override local legal restrictions by design or by omission. When you use our platform, the terms published here apply to your account activity, your transaction records — including those you can cross-check in your bKash or Rocket app history — and the content we make available in the lobby. Any transaction you initiate through bKash or Rocket creates a record in both our system and your mobile wallet, and those records are the primary evidence of account activity. Our published terms sit alongside applicable local law; where the two conflict, local law takes precedence. We revise these terms when our service structure changes, and we publish the updated version at this address. You should review this page whenever you have a question about what rules govern your account. If anything here is unclear, our support path is the right place to raise it.
Understanding what falls inside and outside our legal terms helps you know where to direct a question and what record to check first.
Our terms govern how your account is created, verified and maintained. Steps for login, identity confirmation and account suspension decisions are all covered here. What falls outside scope is any third-party authentication service you use to reach your device.
Deposits and withdrawals processed through bKash or Rocket are covered by our transaction policy. The record in your mobile wallet app reflects the same event logged on our side. Fees or timings applied by bKash or Rocket are governed by their own terms, not ours.
Game content supplied by studios available in our lobby — including titles you can browse now — is covered under our content licence arrangements. We do not control the game rules set by individual studios, and those rules sit outside our direct policy.
Any external link, payment app interface or mobile browser behaviour falls under the terms of those third parties. Our policy does not extend to what happens inside your bKash or Rocket app after a transfer is confirmed from our platform.
You have several concrete actions available to you under the terms published here, and each one has a clear starting point inside your account. To review your transaction history, open the wallet section of your account and check the records listed there — these match what appears in your bKash or Rocket app, so you can verify both sides independently. If any account detail is out of date or incorrect, the profile section of your account is where you submit a correction request; we action those requests through our support queue rather than automatically. If a policy question is not answered on this page, raising it through the support route is the documented path — we do not accept policy queries through social media or unverified contact forms. Requesting a full account record or asking for account closure is also handled through support, and we respond through the same channel you opened. None of these steps require you to provide payment credentials again; your account login is sufficient to initiate any of them.
Open the wallet section in your signed-in account to see all logged transactions. Cross-check against your bKash or Rocket app history to confirm both records match.
Navigate to the profile section of your account to submit a correction for any detail that is wrong or outdated. Our team reviews and updates the record through the support queue.
If this page does not answer your question, contact us through the published support route. We handle policy queries the same way we handle account questions — directly and on record.
Account closure requests go through our support channel. You do not need to re-enter payment credentials; your account login and a written request through support are enough to start the process.
If you have a question about your rights, your account records or how our terms apply to a specific transaction, these are the routes we publish for reaching us. Use the channel that matches your question type.
The live chat option is accessible from your signed-in account area. Use it for account-specific questions, transaction queries you cannot resolve by comparing your bKash or Rocket records, and anything that needs a quick written exchange.
For formal policy questions, account closure requests or written records of a dispute, email is the appropriate route. Details are published in the contact section of the site. Keep a copy of your sent message as your own record.
Inside your signed-in account there is a support ticket option. This route creates a logged thread that both you and our team can reference. It is the route we recommend for anything that requires a documented response.
Our approach to the information connected to your account is grounded in what we can describe accurately and what you can verify through your own records and device settings.
We retain the information you provided at registration and the transaction records generated by your activity, including bKash and Rocket deposits. You can request a summary of held data through the support ticket route at any time.
Our site uses cookies to maintain your session and remember your account preferences. Your browser settings give you control over cookie storage. Disabling cookies may affect login persistence but does not prevent account access through normal login steps.
Your account is protected by the login credentials you set. We do not ask for your bKash or Rocket PIN through any support channel. If a message requests your mobile wallet PIN, do not respond and report it through the support ticket route immediately.
We keep transaction records for the period required by our internal policy. If you want to know the current retention period or request that outdated information be reviewed, contact us through email or the in-account support ticket — not through social channels.
These questions cover what we hear most often about account rights, data handling, policy scope and how to act on the options available to you.
Access depends on your local law and whether your location falls within our eligible regions. We do not make a universal availability claim. If you are unsure whether access is permitted in your area, check the applicable local regulations before proceeding with registration or transactions.
Open the wallet section of your signed-in account. Every deposit and withdrawal processed through bKash or Rocket appears there. You can independently verify the same transaction in your bKash or Rocket app history, since both sides log the same event.
Yes. Go to the profile section of your account and submit the correction through the form shown there. If the correction cannot be made through that route, raise a support ticket from inside your account and we will handle it through the documented support queue.
Send the request through email or an in-account support ticket. Include your registered account details so we can locate your record. We do not accept data requests through live chat or social media channels, as those routes do not create a verifiable written record on your side.
No. We will never ask for your mobile wallet PIN through any channel — not live chat, email or support ticket. If you receive a message requesting your bKash or Rocket PIN and it claims to be from us, treat it as fraudulent and report it immediately through the in-account support ticket.
We retain your transaction records for the period set by our internal retention policy, even after account closure. This is to maintain an accurate record of completed transactions. You can ask about the specific retention period by emailing us or opening a support ticket before or after requesting closure.