Casino / Sports
ck44445 sets out its legal position clearly so you know exactly what governs your account, your transactions via Nagad or Upay, and your use of the lobby. Access to this platform depends on your local law and eligible regions — read this page before you proceed.
Our legal terms govern every interaction you have with the ck44445 platform — from the moment you open an account through to each transaction you record in your wallet. The framework is designed to be readable, not buried in language that obscures your obligations or ours. Where local law in Bangladesh restricts or conditions access, those restrictions apply in full and we do not override them. Your use of the site, including any deposits processed via Nagad, Upay or bKash, is subject to the version of these terms active at the time of that action. We update the policy when the platform changes in a material way, and the revision date at the foot of this page reflects the current version you are reading. If you have questions about how a specific account action — a wallet transfer, a game session, or a request to correct your details — falls under these terms, the right step is to contact support through the route shown on this page. Do not assume a previous version applies if you have not checked the current text. Legal availability of this service depends on your location and the laws of your eligible region.
Not every activity on the platform sits under the same section of these terms. Understanding the boundary helps you direct questions to the right place and read the correct part of the policy before contacting support.
Creating an account, logging in, changing credentials and requesting closures are all covered directly by this policy. Any access restrictions due to your location or local law are applied at this layer and are not overridden by platform navigation.
Wallet moves processed through Nagad, Upay or bKash are within scope as account-level financial records. The policy covers how we store transaction data and what you can request — it does not set payment-provider rules, which come from those services directly.
Game content from studios such as CQ9, Habanero, JDB and Pragmatic Play is available through the lobby. The legal terms cover how that content is presented and accessed via your account, but game-level rules are set by each studio independently.
External payment networks, device operating systems and mobile browsers sit outside our policy scope. We do not control those environments. Where a third-party service condition conflicts with ours, check the relevant provider's own published terms.
You have practical options available to you whenever you need to act on this policy. Reviewing your account history is the first step — your signed-in account area shows transaction records, session data and the details we hold against your profile. If anything looks incorrect, you can raise a correction request directly through the support route listed on this page. We do not require a formal procedure for straightforward account-detail changes; describe the issue clearly and the support team will confirm what documentation, if any, is needed. For questions that go beyond a simple detail change — such as asking what data we retain, how long we keep it, or how a specific wallet entry was processed — use the written contact route so the response is on record. Account actions tied to local law, such as access eligibility or regional restrictions, are handled case by case and depend on the applicable rules at the time of the request.
Open your signed-in account area to see the transaction history, session log and profile details we hold. Everything visible there is the live record — not a cached snapshot.
If a name, contact detail or wallet reference is wrong, raise it with support. Describe the specific field and what the correct value should be. We confirm any identity verification needed before making the change.
Written questions about data retention, regional eligibility or a specific transaction are handled through the email route. State your account reference clearly so the response addresses your exact situation.
For access issues — locked accounts, failed Nagad or Upay transactions or login problems — use the live chat route for faster handling. Keep your registered contact detail ready when you reach out.
If this policy raises a question you cannot resolve by reading the text, three contact routes are available. Use the one that matches the urgency and type of your query — a written route for formal requests, live chat for access issues, and the on-site help section for general policy reading.
Available through the signed-in account area. Use this for account-access questions, failed transaction queries or quick clarifications on how a policy clause applies to your current session.
The written route for formal requests: data queries, correction requests, jurisdiction questions and records of exchanges you want documented. Include your account reference and the specific policy section you are asking about.
The help area within your account lists policy documents, terms versions and common questions. Check there first before opening a support ticket — many policy readings are answered by the published text already on file.
Our approach to the legal obligations on this platform is built around keeping your account record accurate and your data handled consistently. We do not share account-level data outside the scope described in these terms, and we do not retain transaction records — including Nagad, Upay and bKash entries — beyond the period needed to fulfil our obligations. Any change to retention practice is reflected in an updated policy version with a new revision date.
Account data — your profile fields, wallet references and session records — is held only for the period our terms require. After that period, records are removed in line with the retention schedule set out in the current policy version.
We use session cookies to keep you logged in and to remember lobby preferences across mobile and desktop. No advertising tracking is applied beyond what the cookie notice in your account settings describes. You can review and adjust that from settings.
Keeping your login credentials secure is your responsibility. If you believe your account has been accessed without your knowledge, contact support immediately via live chat so we can flag the session record and guide the next steps.
When we update these terms in a material way, a notice appears in your account area on next login. Continuing to use the platform after that notice constitutes acceptance of the revised terms, so read the change summary before dismissing it.
These are the questions we see most often when someone reads this policy for the first time. If your question is not here, use the email support route with your account reference included.
Access and the applicability of these terms depend on your local law and eligible region. If your location restricts access to this type of platform, those restrictions apply regardless of what the policy says. Read the access eligibility section or contact support for your specific situation.
Yes. Send a written request via the email support route with your account reference. Describe what you are requesting — transaction history, profile data or session records — and we will respond with what the current policy permits us to share and how long it takes.
Transaction records for Nagad, Upay and bKash entries are kept for the period set out in the current policy version. You can view the history in your signed-in account area at any time. Requests to query a specific entry should go through the written support route.
Open a support request — live chat for straightforward changes, email for anything requiring documentation. State the specific field and the correct value. We confirm any verification step needed before updating the record, so have your registered contact detail ready.
A notice appears in your account area when terms are updated in a material way. The revision date at the foot of this page also changes. Check that date whenever you return to this page — if it is newer than when you last read the policy, review the change summary shown at the top of the updated version.
Use the email support route and include your account reference along with the specific clause or section you are asking about. For access eligibility questions tied to your region or local law, describe your location context so the response addresses the correct legal framing.