Live / Mobile
This page sets out how 2w44 operates its policy framework for accounts accessed from Bangladesh — covering your rights, our obligations, and the conditions that govern your use of the platform. Access and eligibility depend on your local law and the eligible regions we serve.
Our legal framework applies to every account registered and accessed through 2w44. It governs how we collect, store and process account data, how transactions are recorded against your wallet, and how disputes are routed. Where you use a local payment method — such as Nagad or Rocket — the transaction record sits in your account history and is governed by these terms alongside the payment provider's own conditions. We do not override the payment provider's terms; both sets apply in parallel. Access to 2w44 depends on whether your jurisdiction permits participation in online gaming services. We do not make eligibility determinations on your behalf — that responsibility rests with you and, where relevant, your local authority. If you are uncertain whether access is permitted in your region, we recommend reviewing your local law before continuing. Our policy terms are updated from time to time. The version published on this page is the one currently in effect. Continued use of the platform after a policy update constitutes acceptance of the revised terms. If you disagree with a change, the correct action is to stop using the platform and raise your concern through our support route before your next session.
Understanding the scope of these terms helps you know where to direct a question — whether that is to us, to your payment provider, or to a third-party service. The four areas below set the boundary clearly.
These terms govern your registered account on 2w44 — login, session activity, wallet balance and transaction records. Actions you take while signed in fall within this policy. Account suspension or closure decisions are made under these terms.
Deposits and withdrawals processed through Nagad or Rocket are recorded in your account wallet and subject to these terms. The payment provider's own conditions also apply. We do not govern processing timelines set by third-party payment rails.
Game content supplied by studios — including Microgaming, JDB, PlayStar and Pragmatic Play — is governed by the respective studio's content licence. We make that content available in the lobby; we do not modify or extend the studio's own terms for individual titles.
Links or integrations leading away from 2w44 — including external payment pages or identity verification services — fall outside this policy once you leave our domain. We recommend reviewing the terms of any third-party service before submitting data to it.
These terms are not only obligations — they also set out practical actions you can take. You have the right to review the data held on your account, request a correction where something is inaccurate, and ask us to clarify how a decision about your account was reached. If you believe a transaction record in your wallet is incorrect — whether that transaction was made via Nagad, Rocket or another route — you can raise a dispute through the support channel and we will review the record against our logs. We aim to acknowledge all policy-related requests received through a published support route; response handling depends on the volume of requests in the queue. You cannot waive rights granted to you under applicable local law by accepting these terms — those rights remain in place regardless of what this policy says.
Open the account history section once signed in to see every transaction and session event logged against your wallet. This is the authoritative record we work from when reviewing a dispute.
If your registered name, contact address or wallet identifier is incorrect, submit a correction request through the support route. We will verify the change against the details provided at registration before updating the record.
Any question about how a specific term applies to your account can be submitted through the support channel. State the relevant section and your account reference so we can give you a precise answer rather than a general one.
If you need assistance with access, a locked account or a data-related concern, our support route is the correct path. Do not share account credentials through any channel other than the verified login page.
For any legal or policy-related concern, use the contact routes published on this site. We do not accept policy disputes raised through social media or unverified third-party channels — submit through the routes below to receive a traceable response.
The live chat option on the site is the fastest route for account and policy questions. Start a session while signed in so our team can access your account record directly during the conversation.
For formal policy requests — including data correction, access disputes or written clarifications — use the support email address published in the site's contact section. Include your account reference and the specific policy point you are querying.
The help centre linked from your signed-in dashboard contains published policy summaries, wallet FAQs and step-by-step account guides. Check there first — many policy questions are answered without needing to open a support ticket.
Our policy conduct is built around four operational commitments that you can verify through your account settings and the published support routes. These are not aspirational claims — they reflect how the platform is configured.
Account data — including wallet transaction records and session logs — is retained for the period required by the terms in effect at registration. We do not share your account data with third parties except where required to process a transaction through Nagad, Rocket or another payment rail.
We use session cookies to maintain your signed-in state across the mobile lobby. No advertising cookies from third parties are set without disclosure. The cookie notice on first visit sets out what is active and gives you the option to manage non-essential cookies.
Your account credentials are stored in hashed form. We do not have access to your password in plain text. If you believe your account has been accessed without your permission, use the account recovery route on the login page immediately and then contact support.
When we update these terms, the revised version is published on this page with a note of what changed. For material changes that affect account rights, we send a notification to your registered contact address before the change takes effect.
The questions below cover what we hear most from accounts in Bangladesh about how the policy works, what your rights are, and how to act on them.
Yes. The same policy applies whether you access the platform through a mobile browser or a desktop session. Eligibility still depends on your local law and the eligible regions we serve — mobile access does not change that condition.
We hold registration details, session logs and wallet transaction records. To request a summary of the data held on your account, contact support through the published email route with your account reference. We will respond through the same channel.
Open your account transaction history and note the reference number for the entry in question. Then raise a dispute through live chat or email support, quoting that reference. We cross-check against our payment logs and respond with the outcome.
We can close or suspend accounts that breach the terms in effect. For suspensions related to a policy review, we notify the registered contact address before acting where that is practicable. You can request a written explanation of any closure decision through the support email route.
Submit a correction request through the support channel and include the current incorrect detail, the correct version, and your account reference. We verify the request against your registration record before making any change to protect your account from unauthorised edits.
Send your concern to the support email address with the specific section you disagree with and the reason. Continued use after the updated policy takes effect is treated as acceptance, so raise your concern before your next session if you want a response before that point.