Slots / Live
bt299 collects only the account and transaction data needed to run your wallet, process payments through Nagad and Upay, and keep your session secure. This page explains exactly what we collect, how we use it, and the steps you can take to review or correct your records — all subject to your local law and eligible regions.
When you open an account with us, we collect the information you enter directly — your name, contact details, and the payment method you choose to connect, which may include Nagad or Upay. We also record transaction references tied to deposits and withdrawals so that your account wallet reflects an accurate history you can check at any time from the account area. Beyond what you type in, our systems capture standard session data: the device type, browser version, IP address and pages visited during each session. We use this to detect unusual access patterns and keep your account secure. We do not sell this data to third parties, and we do not share it with advertisers. Data we hold is kept only as long as your account remains active or as required by the applicable rules of the jurisdiction governing your access. If your account is closed, we follow a defined retention schedule before removing personal records. Where local law in Bangladesh or the eligible region you access from imposes specific obligations on how long data must be held or how it must be deleted, those rules take precedence. Availability of our service itself depends on your local law and the eligible regions we operate in at the time you access the site.
This privacy policy applies to all activity conducted through the bt299 domain and its account systems. It does not extend to third-party sites linked from our pages, external payment providers, or any service you access independently outside of the bt299 session environment. Read the sections below to understand how scope is divided across the main areas of your account experience.
Data collected when you log in, update your profile or change account settings falls fully within this policy. This includes the email address, password hash and any session tokens generated during authentication. All of this stays within our systems.
When you initiate a deposit or withdrawal using Nagad or Upay, the transaction reference is logged in your account history. The payment rail itself is operated by the respective provider — their own privacy terms govern what happens on their side of the transfer.
Game session data — rounds played, session duration, balance movements — is recorded for account accuracy and session control purposes. This data is held within the bt299 account environment and is accessible to you from the account history section.
Links to external sites, game studio interfaces or payment apps that open outside the bt299 domain are not governed by this policy. Once you leave our environment, the privacy practices of the destination service apply. We encourage you to read those terms separately.
You have several practical routes to act on the data we hold about you. The most direct is your account area — log in and open the profile section to see the personal details currently on file. If something is incorrect, you can edit most fields directly from that screen; for records tied to a verified payment method like Nagad or Upay, contact our support team to request a correction, since those fields link to transaction history and cannot be changed unilaterally. If you want to know what data we hold beyond what appears in your account view, you can submit a data enquiry through the support channel. We will respond with a summary of the categories of data held against your account. Requests to delete your account and associated personal records can also be submitted through support — note that applicable local law and the rules of the eligible region you access from may require us to retain certain records for a defined period before deletion is completed.
Open your account profile page after logging in. Personal details, payment method references and session history are visible there without needing to contact support first.
Most name and contact fields can be edited directly in the profile section. For Nagad or Upay-linked payment details, raise a correction request through the support channel so records stay consistent with your transaction history.
If you want a summary of all categories of data held on your account, send a request through our support route. We will provide a clear response covering what is held, why, and for how long.
Account closure and data deletion requests go through the support team. Retention timelines depend on local law and the jurisdiction rules applicable to your eligible region at the time of the request.
If you have a question about this privacy policy, want to exercise a right listed above, or need clarification on how your Nagad or Upay transaction data is handled, the routes below are the ones we actively monitor. Use the channel that fits your situation — account-specific questions go faster when you include your registered contact detail so we can locate the right record without delay.
Open the chat widget from any page while logged in. This is the quickest route for account-level privacy questions, including requests to review what session or wallet data is currently held against your account.
Send your privacy request or data enquiry to our support email address, which is listed in the contact section of the site. Include your registered email and the nature of your request so we can route it to the right team.
The help section inside your logged-in account area contains links to submit formal requests — including correction, data summary and deletion. This route creates a tracked record of your request within our system.
We apply access controls and encryption at the account level so that your personal data, session records and payment references are not accessible to anyone outside the teams that need them to operate your account. Our approach to data handling covers four areas — storage, cookies, retention and who can request changes — each described below so you know exactly where your information goes and how long it stays.
Personal data and transaction records — including Nagad and Upay references — are stored on access-controlled systems. Staff access is limited to what each role requires. No personal record is visible to teams outside account operations and compliance without a logged reason.
We use session cookies to keep you logged in and to record how the site is navigated during a session. You can manage cookie preferences through your browser settings. Disabling certain cookies may affect how some account features behave — the account area will note which ones are required.
Active account data is held for as long as your account remains open. After closure, retention follows the timeline set by applicable local law and the rules of the eligible region you access from. We do not hold data longer than those rules require.
Any change to personal data, account details or a request to remove records goes through the support team or the in-account help section. We do not process deletion requests submitted through chat alone — a formal request route is required so the action is properly tracked.
The questions below cover what we hear most from account holders about how their data is handled, what rights they have, and how to act on those rights. If something is not covered here, the support routes in the section above are the right place to ask.
We collect the details you enter during registration — name, contact information and your chosen payment method, which may include Nagad or Upay. We also log standard session data such as device type, browser and IP address to keep your account secure and functioning correctly.
We do not sell your personal data or share it with advertisers. Transaction references connected to Nagad or Upay are handled by those payment providers under their own privacy terms. Outside of that, data is shared only where local law or the rules of your eligible region require it.
Log in and open the profile section — most personal details and transaction references are visible there directly. For a fuller summary of all data categories held against your account, submit a data enquiry through the support channel or the in-account help section.
Most profile fields can be edited directly after logging in. For details linked to a verified payment method like Nagad or Upay — which connect to transaction records — raise a correction request through support so the change can be applied consistently across your account history.
After account closure, we follow a retention schedule set by the applicable local law and the rules of your eligible region. We do not keep data longer than those rules require. The exact timeline may vary depending on which jurisdiction applies to your access at the time of closure.
Submit a deletion request through the support team or the formal request route inside your account's help section. Chat alone is not sufficient — a tracked request is required. Processing timelines depend on local law and any retention obligations that apply to your eligible region.