Slots / App
8777brt collects only the account and transaction data needed to run your wallet, process bKash or Nagad payments, and keep your session secure. This policy tells you exactly what we hold, why we hold it, and what you can do about it — access depends on your local law and eligible regions.
When you open an account with us, we collect the details you submit during registration — name, contact information and the wallet identifiers you connect, such as your bKash or Nagad number. We also record transactional data: deposit timestamps, withdrawal requests, and the Rocket or Nagad reference numbers attached to each movement of funds. This lets us resolve payment questions against a concrete record rather than asking you to rely on memory. Beyond account and payment data, we log device and browser signals — IP address, session tokens and page-interaction data — to detect unusual access patterns on your account. We do not sell this data to third parties for advertising. We share it only with payment processors needed to complete your transaction, or where applicable law requires disclosure. Data we collect is kept for as long as your account is active and for a period afterward as required by applicable regulations in the regions where this service is available. You can ask us to review what we hold at any time through the contact routes listed in this policy. Access to and availability of this service depends on your local law and eligible regions.
This policy covers the data 8777brt processes directly through your account, your wallet connections and your activity on our platform. It does not extend to third-party services you reach through links on our site, and it does not govern how payment processors such as bKash or Nagad handle data on their own systems. Understanding the boundary helps you know who to contact when a question arises.
Any data collected when you log in, verify your account or update your profile is covered by this policy. This includes login timestamps, device identifiers and any identity documents you submit through our account verification flow.
Transaction records created when you deposit or withdraw via bKash, Nagad or Rocket are covered here. The payment processor's own data handling on their platform follows their separate privacy terms, not ours.
Cookies and session data gathered while you browse the lobby, load game pages or navigate sports markets fall within this policy. You can manage cookie preferences through your browser settings at any time.
Links that take you away from 8777brt — whether to a payment app, a game studio page or any external resource — are outside this policy's scope. Those services operate under their own privacy terms independently of us.
Your account record is yours to review. Log in and open the account section to see the profile details, wallet connections and transaction history we hold against your registered number. If any detail is wrong — a name spelling, a contact number, or a bKash wallet identifier — you can correct it directly in the account settings page or ask our support team to update it on your behalf. You can also ask us to tell you what categories of data we hold, how long we keep them, and whether we have shared any record with a third party. We handle these requests through the contact routes listed in this policy. Where applicable law in your region gives you a right to request deletion of certain records, we will follow that process and confirm the outcome to you in writing. Response times depend on the nature of the request and the requirements of applicable regulations.
Open the account section after logging in to see the data attached to your profile, including wallet identifiers and the transaction timestamps we hold on file.
Update your name, contact information or linked bKash and Nagad wallet numbers directly in account settings, or submit a correction request through our support channel.
Send a written query through our support route to find out what categories of data we hold, why we hold them and whether any record has been shared with a third party processor.
Where your local law allows it, you can request deletion of certain records. Contact us with your account reference and the specific record in question; we will confirm the outcome in writing.
If you have a question about this policy, a concern about how your data is handled, or a request to review or correct a specific record, reach us through the routes below. Use your registered account contact detail when you write so we can locate your record without delay. All privacy-related queries are handled separately from general account support to keep your request on file.
Open the live chat widget from any page on the site. Quote your registered account number and describe the data question; the agent will log it as a privacy request.
Send your privacy query to the support email address shown in your account dashboard. Include your registered bKash or Nagad number so we can match it to your record quickly.
The Help Centre inside your signed-in account lists published routes for data queries, correction requests and escalation steps. Start there to see the current contact options available.
Account security, data retention and cookie behaviour are each managed through distinct controls rather than a single blanket policy. We aim to keep each area clear so you know exactly where to look when a question comes up.
We use session cookies to keep your account active while you navigate between the sports markets and the casino lobby. Persistent cookies track preferences only; you can clear or block them through your mobile browser settings without losing your account access.
Access to your account record is restricted to authenticated sessions. If we detect a login from an unfamiliar device or location, we flag it and may ask you to verify via the contact method registered to your account.
Transaction records — including bKash deposit timestamps and Nagad withdrawal references — are kept for the period required by applicable regulations in supported regions. Once that period passes, records are removed from active storage.
When we update this policy, we publish the revised version at this URL and note the change date at the top of the page. Continued use of your account after a published update means you have seen the revised terms; check this page periodically for changes.
These questions cover the data points our account holders ask about most often — from what we log when a bKash deposit goes through to how to request a copy of your own record.
We collect the name, contact number and wallet identifier you enter during registration — for example your bKash or Nagad number. We also record the IP address and device type used during sign-in. We do not collect data beyond what your account and payment activity generates.
Yes. Every deposit and withdrawal reference we receive from bKash, Nagad or Rocket is stored against your account record with a timestamp. You can view these in the transaction history section of your signed-in account at any time.
We share data only with payment processors needed to complete your transaction — such as the processor handling your bKash or Nagad transfer — and where applicable law requires disclosure. We do not sell account or transaction data to advertisers or marketing platforms.
Send a written request through live chat or the support email shown in your account dashboard. Quote your registered account number and specify what record you want to review. We will confirm receipt and respond according to the requirements of applicable regulations in your region.
Where your local law gives you a deletion right, yes. Contact us with your account reference and the specific records in question. Note that transaction records tied to payment obligations may need to be kept for the period required by applicable regulations before deletion is possible.
We use session cookies to keep you logged in while you move between the sports betting section and the casino lobby, and preference cookies to remember your display settings. You can block or clear cookies in your mobile browser settings. Blocking session cookies will require you to log in again each visit.