Slots / Sports
This page sets out the legal framework that governs your use of bee98. Access to our platform and its features depends on your local law and eligible regions — read the sections below to understand how this policy applies to your account.
bee98 operates under a policy framework where access, account eligibility and permitted use depend on the laws that apply in your location. We do not make blanket statements about legality in any specific region. If local law in your region restricts or prohibits access to platforms of this kind, that restriction applies to you and it is your responsibility to check before using the site. When you create or use an account on bee98, you confirm that you have checked your local legal position and that you are accessing the site in an eligible region. We may limit or suspend account access where we identify access from a restricted area, based on the information available to us at the time. Your account wallet — whether linked to bKash, Nagad or Upay — is subject to the same policy scope. Transactions processed through those local payment rails are recorded against your account and covered by the data handling practices described in the sections below. If a transaction is flagged for review, we follow the steps set out in this policy before any action is taken on your account. Questions about specific account situations should be sent through our published support route rather than assumed from general policy wording.
Not everything connected to your experience on bee98 falls under this single policy document. The table below draws the line clearly — so you know where this policy applies directly and where a separate set of rules or a third-party service takes over.
This policy covers how we manage your account, what information we hold and under what conditions access may be paused or closed. Login steps, wallet linkage and account verification all fall within this scope.
Deposits and withdrawals processed through bKash, Nagad or Upay are within scope. We record these against your account and apply the data retention practices set out here. We do not control what your payment provider records on their side.
Game content supplied by studios in the lobby — including titles from CQ9, JDB and Spadegaming — is governed by its respective provider terms. This policy covers your access to that content, not the content itself or its rules.
Where you follow a link or use a service outside the bee98 platform, that third party's own terms apply. We are not responsible for external sites, tools or payment services not directly operated by us.
You have a set of concrete actions you can take in relation to your account and the data we hold. These are not abstract rights — each one corresponds to a step you can actually take through your account or through our published support route. To review the records held on your account, log in and check your account history section. Transaction records tied to bKash, Nagad or Upay deposits and withdrawals are listed there with dates and status. If something looks incorrect, you can raise a correction request through the support route — do not assume an error will resolve on its own. For corrections to personal details such as your registered mobile number or name, the account settings section is the first place to check; some changes require support verification before they take effect. If you want to ask a question about how your data is used or stored, that goes to our support team via the contact route published on the site.
Log in and open your account history to see all transactions and account events. Records linked to bKash, Nagad and Upay payments are listed there with status details.
Go to account settings to update your registered mobile number or other personal details. Changes that affect wallet linkage or verification may require support confirmation before they apply.
If any section of this policy is unclear in relation to your account situation, send your question through our published support route. We do not handle policy queries through social channels or unverified contact forms.
For access issues, payment record queries or account-level disputes, contact our support team directly. Give your registered account details so the team can locate your records promptly.
Policy questions and account-related concerns should come through the routes we have published on the site. We handle each contact based on the account details you supply, so make sure your registered information is current before reaching out.
The live chat option is accessible from the account area once you are logged in. Use this for account-specific questions where you need a direct response tied to your records.
For policy queries that need a written record — such as data correction requests or formal account questions — use the email address published on the site's contact page. Include your account reference.
The help centre on the site covers common account and policy questions. Check there first before raising a direct support ticket, as many queries about wallet linkage and account steps are answered there.
Account security and data handling are managed according to the practices described in this policy. When you link a payment method such as bKash, Nagad or Upay, the connection is held at the account level and used only for transactions you initiate. We do not share wallet or transaction data with unrelated third parties.
We use cookies to keep your session active and to record site preferences. You can manage cookie settings through your browser. Continued use of the site after reading this policy means you are aware of and accept this practice.
Your account is protected through login credentials you set at registration. If you suspect unauthorised access, go to account settings and change your password, then contact support through the published route immediately.
We keep account and transaction records for as long as is required by our internal policy and by the obligations that apply to us. You can ask about the retention period for your specific records through our email support route.
Requests to correct, update or remove personal data should be made through the email support route with your account reference included. We respond based on the information available in your account at the time of the request.
These are the questions we hear most often about how this policy works in practice. If your question is not covered here, use the published support route to ask directly.
Yes. Transactions you process through bKash, Nagad or Upay are recorded under your account and fall within the scope of this policy. The data handling and retention practices described here apply to those records. Your payment provider holds their own records independently under their own terms.
Access depends on your local law and the region you are accessing from. We do not make a blanket statement about legality in any specific location. It is your responsibility to check whether access to platforms of this kind is permitted under the laws that apply to you before using the site.
Start in the account settings section where basic profile details can be updated. Changes that affect your registered mobile number or wallet linkage — such as a linked bKash or Nagad number — may need to go through the support team for verification before they take effect.
We hold the registration details you provided, your account activity history and transaction records linked to your payment methods. You can review transaction records in your account history section. For a fuller account of what data is held, send a request through our email support route.
Records are retained for as long as our internal policy requires and for as long as obligations applicable to us dictate. If you want to know specifically how long your records will be held, ask through our email support route with your account reference included.
Go to account settings and update your password immediately. Then contact support through the live chat or email route published on the site, providing your account reference. Do not share your login credentials with anyone and do not use unverified login links.