Slots / Casino
beet299 collects only the information needed to run your account, process your wallet transactions through bKash, Nagad, and Rocket, and keep your session secure. This policy explains exactly what we collect, why we collect it, and what you can do about it — your access and rights depend on your local law and eligible regions.
When you open an account with us, we collect the registration details you provide — your name, contact number and email address — along with the account activity generated during your sessions. This includes login records, device type, browser identifiers and the IP address your connection comes from. When you move funds through bKash, Nagad or Rocket, we retain a transaction record tied to your account: the wallet reference, the amount direction and the timestamp. We do not store your mobile wallet PIN or any credential that belongs to those payment services — that authentication happens entirely within the respective wallet app. We also collect behavioural data: which sections of the site you open, how long a session runs, and which account pages you visit. This helps us improve navigation and spot issues before they affect your experience. We do not sell this data to third parties or share it outside the operational scope described in this policy. Retention periods follow the requirements of applicable law in the regions where access is permitted, and we review stored records on a scheduled basis to remove data that is no longer needed.
This policy covers data processed directly by beet299 through your account. It does not extend to third-party services you connect to from our platform. Understanding the boundary helps you know where to direct a privacy question.
Any data you provide during registration, login or account verification falls under this policy. That includes your contact details, password hash and the security questions linked to your profile. We control this data directly and you can request a review at any time.
Records of deposits and withdrawals processed through bKash, Nagad or Rocket are stored in your account transaction log. We hold the platform-side record; the wallet provider holds its own. Questions about the wallet provider's data handling go to that service directly.
Cookies placed by beet299 to maintain your session, remember your language preference and measure page performance are covered here. You can manage cookie acceptance through your browser settings. Disabling certain cookies may affect how pages load in your session.
Game studios whose content appears in the lobby — such as Pragmatic Play, Microgaming or Habanero — operate their own data environments for game-round records. Their privacy practices are governed by their own policies. We do not control what those services collect on their side.
You have practical options available to you at any point. Reviewing what we hold starts in your account settings page, where your registered details and transaction history are visible without needing to contact us. If any detail is incorrect — your phone number, email address or payment preference — you can update it directly from the account profile section. For records that are not editable in the interface, such as historical transaction logs, you can submit a formal data request through our support channel and we will respond with the relevant records. If you believe data is being held incorrectly or beyond the period it should be retained, raise it with us in writing and we will investigate. Your ability to exercise these rights depends on the applicable law in your region, and we will always tell you if a local legal requirement limits what we can act on from our side.
Open the account settings page to see your registered contact details, active session information and payment history. No separate request is needed for information already visible there.
Update your email, phone number or linked wallet preference directly in the account profile section. If a field cannot be edited in-app, contact support with the correction and we will apply it after verifying your identity.
Send a written request through the published support route if you want a copy of data we hold beyond what is visible in your account. We will confirm receipt and respond within the timeframe required by applicable law.
If you have a concern about how your data is being used, write to us through the contact route listed in this policy. We treat privacy questions as separate from general account queries and route them to the appropriate team.
Privacy questions are handled separately from general account support. Use the routes below to reach us; we route each enquiry to the right team based on the subject you describe. Do not share your wallet PIN or full account password through any of these channels.
Open the chat widget from any page of beet299 while you are signed in. Type your question and mention it is a privacy matter so our team routes it correctly. Available through the site interface.
Send your privacy request or data correction query to the support email address listed on the Contact page of beet299. Include your registered account number and a clear description of the data matter you are raising.
The Help Centre linked from your signed-in account menu contains published articles on data requests, cookie settings and account controls. Check there first — many common privacy questions are answered without needing to raise a direct request.
We apply a practical set of controls across the account, payment and session layers to keep your data handled consistently. These are not marketing claims — they describe the operational decisions we have made about how your information is stored, who can access it and how long we keep it.
Session and analytics cookies on beet299 can be managed through your browser settings. Essential cookies required for login and account security cannot be disabled without ending your session. Non-essential cookies, including those used for performance measurement, can be turned off without affecting core account functions.
Access to your account data within our systems is restricted to authorised operational roles. Your password is stored as a hash, not in plain text. bKash, Nagad and Rocket credentials are never stored on our side — those are authenticated entirely by the respective wallet service.
We retain account and transaction records for the period required by applicable law in regions where access is permitted. When data is no longer required for legal or operational purposes, it is scheduled for deletion or anonymisation. You can ask us what period applies to your specific account record.
When this policy changes in a material way, we publish the updated version at beet299/privacy-policy/ and note the revision date at the top of the page. Continuing to use your account after a policy update means you have had the opportunity to review the revised terms. You can always contact us if a change raises a question.
These are the questions we receive most often about how beet299 handles account data. If your question is not covered here, use the support contact routes listed on this page.
We collect your name, phone number, email address and the details you provide during account verification. We also record device type, browser identifier and IP address for each session. Payment records from bKash, Nagad or Rocket transactions are stored as platform-side logs, not as wallet credentials.
We do not sell your data. We share it only where required by applicable law or where a service provider operates a function on our behalf under a data processing agreement. Game studios listed in our lobby hold their own game-round data; their handling is governed by their own policies, not ours.
Yes. Your registered details and transaction history are visible in the account settings page without any formal request. If you want records held outside that view — such as archived session logs — submit a written request through live chat or email and we will respond with what applies to your account.
Open your account profile section and edit the field directly if it is available for self-service editing. For fields that cannot be changed in-app, contact our support team through live chat or email, confirm your identity when asked, and we will apply the correction and confirm it in writing.
Retention periods follow the legal requirements applicable in your region. We review stored data on a scheduled basis and remove or anonymise records that are no longer required for legal or operational purposes. Contact support to ask about the specific retention period that applies to your account type.
Closing your account ends active data processing for operational purposes. We retain records for the minimum period required by applicable law — typically related to transaction history and account verification — and then delete or anonymise the remaining data. Contact us in writing to confirm what will be retained and for how long after closure.