Mobile / Sports
bft99 operates under a set of published policies that govern how your account, transactions and personal data are handled on this platform. Access to our services depends on your local law and eligible region — we ask that you review these terms before using your account.
Our legal policy sets out the relationship between bft99 and anyone who opens or holds an account on this platform. It covers how we collect, store and use the information you provide when registering, logging in, or completing a transaction. This includes payment activity routed through bKash, Nagad and Rocket, each of which operates as a separate payment service — their own terms apply to the wallet side of any transfer, and bft99 is not a party to those agreements. Where your account holds a transaction record, that record reflects activity processed through our platform only. We do not share personal account data with third parties except where required by applicable law or where you have given explicit consent. Availability of any account feature — including deposits, withdrawals and game access — depends on your local law and the eligible regions we serve at the time you log in. If local regulations restrict access, those restrictions take effect regardless of account status. We keep this policy updated; the version shown in your account area is the current one. For questions about a specific clause, the support routes listed on this page are the right place to start.
Not everything connected to your account falls under a single policy. This section shows where our terms apply directly and where a separate framework governs the experience.
Your login, session data, password management and account-level settings all fall within this policy. If access is restricted in your region, that restriction is applied at the account layer and is covered here.
Deposits and withdrawals recorded in your account wallet — including activity via bKash, Nagad and Rocket — are within scope. The wallet provider's own terms govern the mobile-money side of each transfer separately.
Game content supplied by studios available in the lobby, odds formats and promotional notices on the platform are governed by our content terms. These sit alongside, not inside, the personal data policy.
Any service you reach by leaving bft99 — including your mobile wallet app, a bank interface or an external link — falls outside this policy. We have no control over how third-party platforms handle your data once you leave.
This policy is not just a list of our obligations — it outlines what you can actively do with your account data. You have the right to review the transaction and personal data records held against your account, and you can request a correction if any detail is inaccurate. If you believe a record is incomplete or was recorded in error, the correction process starts with a support request — not an in-app self-edit, because changes to core account fields go through a verification step on our side. You can also ask what categories of data we hold about you and how long we keep them. That request should be made through the contact route listed in our support section, with your account reference included so we can locate the correct record. We aim to handle data requests in line with the obligations described in this policy; response times depend on the nature of the request and are not contractually fixed. If your question involves your bKash or Nagad wallet history, note that wallet-side records sit with the payment provider — we can confirm only what our platform recorded at the transaction layer.
Open the transaction history section of your account to see what our platform has logged. If a record looks wrong, note the date and amount before raising a support request — it speeds up verification.
Name, contact details and linked wallet references can be corrected by contacting support with your account reference. Core identity fields go through a manual check before any change is applied.
If a clause in this policy is unclear or you want to know how a specific rule applies to your account, send your question through the published support route with the relevant section noted.
You can ask what personal data categories we hold, why we hold them and for how long. Submit this through the support contact listed on this page; include your account reference so we can pull the right record.
For any question about this policy, the account data we hold, or a correction request, use one of the routes below. These are the channels we maintain for policy-related contact — do not use game lobby chat for data or legal requests, as those are handled by a different team.
Send your policy or data query to our support email address, which is listed in your account's help section. Include your account reference and the specific clause or record you are asking about.
Live chat is available through the account dashboard. For policy questions, select the account or data category when starting the chat so it routes to the right team rather than general game support.
The help centre in your account area carries published policy documents, common data questions and the form you can use to submit a formal request. Check there first before opening a support ticket.
We manage personal data, cookies and account security with a consistent set of internal controls, described here so you know what to expect when you use any part of the platform.
Account and transaction data is kept for as long as required under the applicable policy period. Once that period ends, records are removed from active systems. If you want to know the retention period for a specific data category, contact us via the published support route with your account reference.
We use session cookies to keep you logged in across your mobile browser or desktop session. Functional cookies are required for the account to work; analytics cookies can be adjusted in your browser settings. We do not use cookies to deliver third-party advertising.
Your account credentials are stored in hashed form and are not visible to support staff in plain text. If you suspect unauthorised access, contact support immediately using the live chat route — account suspension pending review can be requested at that point.
To update how we use your data, withdraw consent for non-essential processing, or ask for a record to be removed, send a written request through the support email shown in your account. Changes take effect after we verify your identity and confirm the request applies to your account.
These are the questions we hear most often about this policy. If your question is not covered here, the support routes in the section above are the right next step.
Access and the policy's application both depend on your local law and eligible region at the time you log in. We ask every account holder to confirm they are accessing from an eligible region. If local regulations restrict access, those rules take precedence regardless of account status.
We hold the registration details you provided, your login and session history, and the transaction records generated when you deposit or withdraw via bKash, Nagad or Rocket. You can request a full category summary through the support email listed in your account's help section.
Yes. Send a correction or removal request through the published support contact with your account reference and the specific record in question. Core identity fields go through a verification step before changes are applied. Removal requests are handled in line with the retention rules described in this policy.
Our platform records the transaction reference and amount at the account layer when a bKash or Nagad transfer is completed. We do not store your full wallet credentials. The wallet provider — bKash or Nagad — holds their own records separately under their own terms, which are outside the scope of this policy.
Use the support email or live chat route shown in the support section of this page. Describe the concern clearly and include your account reference. Policy and data concerns are handled by a dedicated team, not general game support, so selecting the correct contact category helps route your request promptly.
We update the policy when our practices or applicable requirements change. The current version is always the one shown in the policy section of your account area. We do not commit to a fixed update schedule, but material changes that affect how we handle your data are flagged within the account before they take effect.