Slots / Mobile
This page sets out how 89bbd operates its policy framework for accounts accessed from Bangladesh and other eligible regions — covering what applies to your account, how we handle your data, and the steps you can take if something needs correcting. Access and eligibility depend on your local law and the region from which you are connecting.
89bbd operates under a policy framework that reflects the laws of the jurisdictions where our services are made available. If you are connecting from Bangladesh, your access and the terms that apply to your account are shaped by local law and regional eligibility — we do not claim legal certainty across all locations, and we encourage you to review whether access is permitted where you are. When you hold an account with us, the legal relationship covers your registered profile, the transaction records attached to it, and the communications you send through our support channels. Payments processed through bKash, Nagad or Rocket are subject to the terms of those respective services in addition to our own account policy. We do not override the terms of those payment providers; we operate alongside them. This policy is not a substitute for local legal advice. If a provision conflicts with a rule in your jurisdiction, the local rule takes effect to the extent required by that law. The current version of this policy is the one shown here; we will update this page when material changes occur and note the change at the top of the document.
Transactions via bKash fall under both our account policy and bKash's own service terms.
Nagad transfers are governed by Nagad's service conditions alongside our internal transaction rules.
Rocket payments operate within Rocket's published framework; our policy covers the account record, not the wallet itself.
Our policy applies to registered accounts, site content we publish directly, and transactions processed through our platform. It does not extend to third-party services you may reach through links on our site, nor to the internal policies of payment providers like bKash, Nagad or Rocket. Understanding where our responsibility begins and ends helps you know exactly who to approach when a question arises.
This policy governs how your account is created, maintained and closed. Eligibility depends on your local law and the region you are connecting from. We do not override national access restrictions.
Payment records held in your account wallet fall within our policy scope. The underlying rails — bKash, Nagad, Rocket — are governed by their own provider terms, which exist separately from ours.
Game content from studios in our lobby, promotional copy we publish and the support material on this site are all covered by our editorial and legal standards. We are responsible for what we publish.
External links, partner services and payment provider interfaces fall outside our direct policy scope. We are not liable for the terms, conduct or data practices of services we do not operate.
Holding an account with 89bbd comes with a set of practical actions you can take at any time. You can review the transaction history attached to your wallet — including records of payments made via bKash, Nagad or Rocket — by navigating to the account dashboard after login. If any detail in your registered profile is incorrect, you can request a correction through our support channel; we will verify your identity before making changes to sensitive fields. If you want to understand how a specific policy provision applies to your account, raise a written question through the support route on this page. We will respond with reference to the relevant section rather than a generic reply. For formal requests — such as asking us to review a transaction record or close an account — use the contact path marked for policy matters so your request reaches the right team without delay.
Your full transaction history, including bKash, Nagad and Rocket entries, is visible in the account dashboard. Log in and open the wallet section to see every record we hold against your account.
If your registered name, contact details or payment reference is wrong, contact support with the correct information. We verify identity before updating any sensitive field on your account.
Written questions about how a specific clause applies to your situation are answered by our policy team. Use the support contact on this page and reference the section you are asking about.
Account closure, transaction dispute or a formal record review each follow a specific process. Flag the request type clearly in your message so it routes to the correct team without additional delays.
When a legal or policy matter concerns your account, the channel you use matters. Routine account questions go through general support; formal policy and data requests should be directed specifically to our policy contact so they are handled by the right team. Each path below is available to accounts registered in eligible regions.
For questions about how our legal terms apply to your specific account or transaction, contact us through the policy support channel listed in your account settings. Include your account reference and the policy section you are asking about.
To correct a registered detail or dispute a transaction record, use the account help route inside the dashboard. Identity verification is required before any change is applied to your profile.
General questions about policy scope, your data or access eligibility can be sent through our support contact form. We respond in writing so you have a record of the answer for your reference.
We collect the account data needed to operate your profile and process transactions. That includes registration details, payment method references for bKash, Nagad or Rocket, and session logs used to verify activity. We do not sell account data to third parties. Cookies on this site are used for session continuity and fraud detection; you can review which cookies are active through the settings link in the site footer. Account security is maintained through the verification steps shown during login and the identity checks required before sensitive changes are made. Retention periods for transaction records are set by our internal policy and, where applicable, by the legal requirements of the jurisdictions we serve. If you want to know how long a specific record type is kept, raise the question through our policy support channel.
We hold your registration details, payment references — including bKash, Nagad and Rocket entries — and session logs. This data supports account operation and transaction verification, nothing beyond that scope.
Cookies on 89bbd handle session continuity and detect unusual activity. The active list is accessible from the footer settings link. We do not use advertising-network cookies that track you outside this site.
Login verification and identity checks before sensitive changes are the two main security gates on your account. If you notice activity you did not initiate, contact support immediately using the policy contact path.
Transaction and session records are retained according to our internal policy and any applicable legal requirement in the jurisdictions we serve. Ask our policy team for the retention period that applies to a specific record type.
These are the questions we receive most often about how our policy works, what rights you hold as an account holder, and how to take action when something needs attention.
Access and the terms that apply depend on your local law and the region you connect from. If access is permitted under your local law and you are in an eligible region, this policy applies to your registered account, your transaction records and your communications with our support team.
After logging in, open the account dashboard and go to the wallet section. Every payment processed through bKash, Nagad or Rocket is listed there with a reference, date and status. If a record looks wrong, raise a correction request through account support.
Yes. Send a correction request through the account help route inside the dashboard. We verify your identity before updating any sensitive field — including your registered name, contact address or payment reference. The verification step is there to protect your account from unauthorised changes.
Formal requests — covering transaction disputes, data queries or account closure — go to our policy support channel, not general support. Routing it correctly means the right team sees your request without additional steps. Include your account reference and describe the action you are requesting.
Retention periods depend on our internal policy and, where relevant, legal requirements in the jurisdictions we operate. We do not publish a single figure because it varies by record type. Contact our policy team through the support channel on this page to ask about a specific record.
Local law takes effect to the extent required. We do not claim legal authority above what your jurisdiction permits. If you believe a specific provision conflicts with a local rule that applies to you, raise it through our policy contact channel so we can address it directly.