Mobile / Slots
These legal terms set out how bd2233 operates your account, handles your data, and defines the scope of our policy for Bangladesh and other eligible regions. Access and participation depend on your local law — read the sections below to understand what applies to you and how to raise any question with us directly.
bd2233 operates as a private member support platform. Whether you can access and use the platform depends entirely on the laws of the country or region where you are located. We do not represent that access is lawful in Bangladesh or any other specific jurisdiction — that determination is yours to make before you open or use an account. Where your account is active and in good standing, transactions processed through local payment channels such as bKash and Rocket are governed by the transaction terms set at the point of submission. Each transaction record is held in your account wallet history, and you can review any entry there after login. We do not alter transaction records after they are written. Our policy documentation — including these legal terms, our privacy position and our account terms — is accessible from the footer of every page. If any conflict exists between a specific page and these overarching legal terms, the legal terms take precedence. We update these terms when our operating posture changes; the current version is always the one shown on this page. Continued use of your account after a published update constitutes acceptance of the revised terms. If you do not accept a change, you should contact support and request account closure before the change takes effect.
bKash transaction entries are recorded at submission time and held in your wallet history.
Rocket payments are logged under the same account record system — viewable after login.
The version shown on this page is always current. Earlier versions are not in force.
Not every part of your experience falls under the same policy provision. This section draws a clear line between what our legal terms govern directly and what sits outside that scope — so you know where to look and who to contact for each type of question.
Account creation, login, session controls and account closure are covered by these legal terms. Eligibility to hold an account depends on local law in your region. We apply the access rules shown in your account settings; we do not override region-level restrictions.
Deposits and withdrawals processed through bKash or Rocket are within scope. The amounts, records and wallet entries for each transaction are governed by the terms accepted at submission. Currency and method availability depend on your account region and the payment channel's own terms.
Game content supplied by studios such as Pragmatic Play and Spadegaming is delivered under their own content licences. We host that content in the lobby but do not control the underlying game rules or RTP figures, which each studio exposes only where their own system permits.
External links, payment processors and device platforms (such as your mobile network or app store) operate under their own terms. Our legal terms do not extend to those third parties. Where a dispute arises with a payment processor, the resolution route runs through that processor's own support, not ours.
Your account is yours to manage, and this policy gives you concrete actions — not just abstract entitlements. After login, your account dashboard shows every session record, transaction entry and setting change in chronological order. If any detail looks incorrect, you can raise a correction request directly through the support channel rather than waiting for a scheduled review. For account data questions — such as what we hold about you, how long we keep it, or who can see it — the correct route is a written query to our policy contact address, which we respond to in the order received. If you want to close your account and request deletion of your data, that request should also go to the same contact. We aim to acknowledge all policy queries and act on verified correction requests; the timeline depends on the nature of the request and any verification we need to complete. The key point is that every right listed here has a real, navigable route — not a general gesture toward a settings page.
Log in and open your account dashboard. Every transaction, session entry and setting change is listed there in order. You do not need to contact support to read your own records — they are visible to you directly after authentication.
If a name, contact detail or wallet reference in your account is wrong, submit a correction request through the live chat or email support channel. Include the field in question and the correct value. We verify the change before writing it to your account.
For questions about data retention, what we hold about you, or how a policy clause applies to your account, send a written query to our policy contact address. State your account identifier and the specific clause or concern so we can respond precisely.
A closure and data-deletion request must be submitted in writing. Open a support ticket or email the policy contact address. We confirm receipt, complete any outstanding transaction records, and then process the closure in the order the request was verified.
Policy queries have a different priority path from general account help. Use the route that matches your question — live chat for account-level corrections, email for formal written requests, and the FAQ section below for common eligibility questions. Each route is monitored; response time depends on query volume and the verification steps needed for your specific case.
Open the chat widget from any page after login. State that your query is a policy matter so the agent routes it correctly. Suitable for account correction requests and session-record questions.
Send formal written requests — data queries, deletion requests, policy disputes — to our policy contact address shown in the footer. Include your account identifier and the specific policy clause or record you are asking about.
Many policy-related records are self-serve. Log in, open the account section, and check the transaction or session history before raising a ticket. The current state of your account data is shown there without needing to contact support.
Account security and data handling are not separate concerns — they are part of the same policy commitment. We apply session controls at the account level, which means your login state, wallet access and transaction history are each protected by the authentication step you completed at sign-in. We do not share account-level data with third parties except where a transaction processor (such as bKash or Rocket) requires the minimum data to complete your submitted transaction. Cookie usage on the platform is limited to session management and account state — we do not use advertising cookies without disclosure. Data retention follows the period required to maintain accurate transaction records and comply with the terms under which your account was opened; once that period ends and your account is closed, retained data is handled according to our deletion policy. If you have a specific question about what data we hold or how long we hold it, the email route in the support section above is the correct path.
Your session state is tied to your authenticated login. Account actions — including wallet access and transaction submission — require an active authenticated session. Session timeout is applied automatically after a period of inactivity shown in your account settings.
We use cookies for session management and to keep your account state consistent across pages. We do not use third-party advertising cookies without disclosure. The cookie notice shown on your first visit explains what is active and how to manage your preferences.
Transaction records and account data are retained for the period required under the terms of your account agreement. After account closure, data is handled per our deletion policy. You can request a summary of what we hold by contacting the policy email address in the footer.
Correction and deletion requests are handled in writing. Submit through live chat or the policy email address. We confirm receipt, verify your identity against the account, and process the request. No changes are written without that verification step being completed first.
The questions below cover what we hear most often from account holders asking about policy scope, data rights, access eligibility and how to raise a formal request. If your question is not answered here, the support routes in the section above are the right next step.
Access and participation depend on your local law and eligible region. We do not confirm that use is lawful in Bangladesh or any specific location — that is your determination to make. If you are in an eligible region, these terms govern your account from the point of creation.
The version shown on this page is always the current one. There is no separate archive of older versions in force. If we update the terms, the change is reflected here and we note it in the updated date shown at the top of this page.
We hold the account details you submitted at registration, your transaction history (including bKash and Rocket entries), session records and any support correspondence. To request a summary of what we hold specifically about your account, send a written query to the policy contact email shown in the footer.
Submit a correction request through live chat or the policy email address. State the field that needs correcting and the correct value. We verify the change against your account before writing it. We do not edit account data without that verification step being completed.
Retention follows the period required to maintain accurate transaction records under your account agreement terms. After that period, data is handled per our deletion policy. If you want specifics on the retention period for your account, contact the policy email address in the footer.
Log in and review the entry in your account dashboard first — the record includes submission time and the payment channel used (such as bKash or Rocket). If you still believe the record is incorrect after checking, raise a support ticket through live chat and include the transaction reference shown in your wallet history.