Live / Casino
beet177 handles your information — including details linked to Nagad transfers, Bank Transfer records and your registered contact — with care and purpose. This policy explains exactly what data we collect, how we use it, and the choices available to you under this policy, subject to your local law and eligible regions.
When you open an account, we collect the details you provide directly: your name, email address, mobile number and any payment identifiers connected to your Nagad wallet or Bank Transfer records. We also collect technical data — device type, browser session, IP address and on-site navigation — to keep the account environment working correctly and to detect unusual activity. We use this data for three core purposes: processing your account transactions, confirming your identity when you access the account, and improving how the platform responds to your device. We do not sell your personal data to third parties. Where we share data with service providers — for example, payment processors handling Nagad or Bank Transfer flows — those providers are bound by data handling agreements that restrict use to the specific task. We retain account records for as long as your account remains active and for a period thereafter as required by applicable law in the regions where this service operates. If your account is closed, we follow a documented retention schedule rather than deleting data immediately, as certain records must be kept to meet legal obligations. Your use of this service is subject to your local law and the eligible regions this platform supports.
This policy covers every interaction tied to your beet177 account — from the moment you register through to any transaction or support contact you make. It does not extend to third-party websites linked from our platform, and it does not govern data collected independently by payment processors operating their own services. Understanding the boundary helps you know which queries belong with us and which belong elsewhere.
Covers all data collected when you log in, update your profile or navigate the account area. This includes login timestamps, device identifiers and any changes made to your registered mobile number or email address.
Covers data created during deposits and withdrawals handled through Nagad or Bank Transfer. The transaction reference, amount and status are stored in your account history and governed by this policy.
Covers session data generated when you browse game categories, open the sportsbook or use the live casino area. This helps us understand which sections are accessed most and how navigation flows on mobile.
Does not cover how external payment processors, game studios or linked services handle your data on their own infrastructure. For those, you need to read the respective provider's own published policy.
You have practical options regarding the data beet177 holds on your account. These are not abstract entitlements — they are steps you can take through your account settings or by contacting support directly. The scope of what is available to you may vary depending on your local law and the eligible regions this service covers. If you believe any detail on your account is incorrect — your registered mobile number, email address or linked Nagad identifier — you can update it through the account settings page. For records you cannot edit directly, you can submit a correction request through the support route listed in this policy. We will confirm receipt and let you know the outcome. If you want to understand what data we hold, you can request an account data summary by contacting us through the published support channel. We do not charge for this. For account closure requests or questions about retention after closure, the same support route applies.
Request a summary of the data held on your account by contacting support through the published channel. We confirm receipt and respond through the same route.
Update your registered email or mobile number directly in account settings. For fields you cannot edit yourself, submit a correction request via support and we will handle it.
If any part of this policy is unclear or you have a concern about how your data is used, contact us through the support route. We treat policy questions separately from general account queries.
Account closure requests go through the published support channel. We will confirm the retention period that applies after closure, in line with the legal obligations for your eligible region.
If you have a question about this privacy policy — including what data we hold, how a specific transaction record is used, or how to request a correction — use the contact routes published on beet177. We do not publish unverified contact details here; reach us through the channels shown in your signed-in account area.
Open the live chat widget from your signed-in account to ask a privacy-related question directly. This is the fastest route for straightforward queries about your account data.
Send a written privacy request to the support email address shown in the contact section of your account. Include your registered mobile number so we can locate your account record.
The help section inside your account lists policy-related topics including data requests and correction procedures. Check there first — many common questions are answered without needing to contact support.
beet177 applies a set of operational standards to the data it holds — covering storage, access controls, cookie use and the process for updating this policy. These are not marketing claims; they are the operational practices behind the policy text above.
Access to your account data is restricted to authenticated sessions. If an unusual login pattern is detected — for example, a new device or location — the account area flags it. You can review active sessions in your account settings.
We use session cookies to keep you logged in and preference cookies to remember your language and region settings. You can manage cookie preferences through your browser settings, though disabling some cookies may affect account functionality.
We keep account data for as long as required by the legal obligations applicable to your eligible region. After that period, data is deleted or anonymised according to a documented schedule — not left in storage indefinitely.
When this policy changes in a material way, we publish the updated version at this address and note the revision. Continuing to use your account after a policy update means you have seen the revised terms.
These are the questions we receive most often about data, account records and your rights under this policy. If your question is not here, use the support channel in your signed-in account.
We collect the details you enter during registration — name, email address and mobile number — along with device and session data generated when you use the platform. Payment identifiers linked to Nagad or Bank Transfer are also stored as part of your transaction history.
We share data only with service providers needed to operate the platform — for example, payment processors handling Nagad or Bank Transfer flows. Those providers cannot use your data for any purpose beyond the task we have assigned them. We do not sell your personal data.
For fields like your registered email or mobile number, go to account settings and update them directly. If a field cannot be edited there, contact support through the published channel with your correction request and we will process it.
We follow a documented retention schedule based on the legal obligations that apply in your eligible region. Some records must be kept for a defined period even after closure. We can confirm the period that applies to your account if you ask through support.
Yes. Contact us through the email support route shown in your account's help section, include your registered mobile number, and request an account data summary. We confirm receipt and respond through the same channel. There is no charge for this request.
No. This policy covers only what beet177 collects and manages directly. If you follow a link to a third-party service — such as an external payment processor or game studio — their own published policy governs how they handle your data.