Live / Sports
87bdd collects only the information needed to run your account, process transactions through payment rails like bKash and Upay, and keep your session secure. This policy sets out exactly what we collect, why we hold it, and the choices available to you — with access subject to your local law and eligible regions.
When you open an account or use 87bdd, we collect information in a few distinct ways. Registration data — your name, contact details and account credentials — is gathered at sign-up. Transaction data is recorded each time you make a deposit or withdrawal using bKash, Upay or any other configured payment rail; those records show the amount, timestamp and payment method used. Device and session data is collected automatically: your browser type, operating system, IP address range and the pages you visit within the site. We use this data to authenticate your account, process payments accurately, detect irregular access patterns and improve how the site performs on mobile. We do not sell your personal data to third parties for their own marketing purposes. We may share limited data with payment processors — such as the mobile wallet operators handling your bKash or Upay transaction — strictly to complete that transaction. We may also share data where required by applicable law or a competent authority. Retention periods vary by data type: account credentials are held while your account remains active; transaction records are retained for the period required under applicable financial rules. Where local law in Bangladesh or another eligible region imposes stricter obligations on us, those obligations take precedence over any less restrictive standard in this policy.
Every bKash deposit and withdrawal generates a transaction record linked to your account. We retain these records for the period required under applicable financial regulations and make them visible to you from your account history.
Upay transactions are logged with the same detail as bKash entries — amount, date and payment status. You can review these entries directly in your account; contact support if a record appears incorrect.
Login identifiers and contact details are held for the lifetime of your account. If you close your account, we retain only what applicable law requires us to keep; the rest is deleted or anonymised within a reasonable period.
Not every interaction with 87bdd falls under the same part of this policy. Understanding the scope helps you know when our data practices apply directly to you and when a third-party policy takes over. The four areas below map out the boundary clearly so there is no ambiguity about who holds what data and under which rules.
Any activity requiring you to log in — placing a bet, loading a game, checking your wallet balance — falls squarely inside this policy. We process and store data generated during authenticated sessions under the terms described here.
Deposits and withdrawals processed through bKash or Upay are covered by this policy for the data we hold on our side. The payment operator's own privacy terms govern the data held within their network separately from ours.
Pages you browse while not logged in — such as reading this policy page — still generate anonymous session data. That data is used only for site performance and security monitoring; it is not linked to a personal profile.
Links to external sites, payment apps or wallet platforms are not covered by this policy once you leave 87bdd. We have no control over how third parties collect or use your data after you navigate away from our domain.
You have meaningful options when it comes to the data 87bdd holds on your account. Reviewing your records is straightforward: log in, open the account section and check the transaction history tab — every bKash and Upay entry is listed with its date, amount and status. Correcting account details follows a similar path; update contact or personal fields directly from the account settings page, and the change takes effect immediately. If a correction requires document verification — for example, a name change — the account section will show the document upload step. Raising a data question outside those self-service options is handled through our support route: open the support page, describe what you need changed or removed, and our team will respond through the same channel. Where your local law grants you a formal right to request data erasure or portability, you can submit that request through support and we will handle it in line with the applicable legal timeframe. Access to any of these actions is subject to your account status and your eligible region.
Log in and open the transaction history tab to see every payment entry — bKash, Upay or other configured method — with date and status. No separate request is needed to view your own history.
Personal and contact fields can be updated from the account settings page. Changes that require identity verification will show a document upload prompt inline; follow the steps displayed there.
For data queries that go beyond self-service — such as asking what specific records we hold — reach our support team through the contact route on the support page. Describe your request clearly so we can respond accurately.
If applicable law in your eligible region gives you a right to erasure or data portability, submit the request via support. We act within the timeframe that law requires and will confirm the outcome through the same channel.
If you have a specific question about how your data is handled, how a bKash or Upay transaction record appears in our system, or how to exercise a right under this policy, the routes below are the ones we actively monitor. Use the channel that suits the nature of your question — account-level queries are generally handled fastest through the in-account support route. Access to support channels depends on your account status and eligible region.
Log in and open the support section from your account menu. Describe your privacy question or data request in the message field. This route links your query directly to your account record, so no additional identity confirmation is usually needed.
A written record suits formal data requests, such as erasure or portability. Use the email address published on the site's contact page, include your registered account identifier and state the specific action you are requesting.
The help section of the site lists current support hours and additional contact options as they are made available. Check there if the above routes do not cover your specific query or if you need a status update on an existing request.
Knowing the mechanics behind this policy builds confidence in how your information is treated day to day. These four areas cover the practical layer: what we do with cookies, how account security is maintained, how long data is retained and how to request a change to what we hold.
We use session cookies to keep you logged in during a visit and analytics cookies to understand which parts of the site perform well on mobile. You can adjust cookie preferences through the cookie notice displayed on your first visit or via browser settings.
Access to your account data is protected by login authentication. We log access events — login attempts, session starts and payment initiations — so that irregular patterns can be detected. We do not store full payment credentials; bKash and Upay transactions route through those operators' own secure flows.
We hold account data for as long as your account is active and for the minimum period required by applicable financial rules after it closes. Data that is no longer required and is not subject to a legal hold is deleted or anonymised on a scheduled basis.
To update, correct or request removal of data we hold, use the in-account settings for self-service changes or contact support for requests that go beyond what the settings page covers. We confirm the outcome of every formal data request in writing through the channel you used.
These are the questions we see most often about how 87bdd handles personal data. If your question is not covered here, reach us through the support route listed on the support page.
We collect the name, contact details and login credentials you provide at registration. Once your account is active, we also record transaction data — including bKash and Upay payment entries — and session data such as device type and IP address range, used for security and site performance only.
Yes. Log in and open the transaction history tab in your account section. Every deposit and withdrawal processed through bKash, Upay or another configured payment rail appears there with its date, amount and status. No separate data request is needed to view your own history.
We share data only where it is necessary to complete a service — for example, passing transaction details to bKash or Upay to process a payment — or where applicable law requires it. We do not sell your personal data for third-party marketing purposes.
Open the account settings page while logged in and update the relevant field directly. If the correction requires identity verification — such as a name change — the page will display the document upload step. For corrections that cannot be made through settings, contact support with the specific detail to be changed.
Account credentials and personal data are held while your account is active. After closure, we retain only what applicable financial or legal rules require for the minimum period those rules specify. Data beyond that requirement is deleted or anonymised. The exact period depends on your eligible region and the applicable law there.
Where the law applicable in your eligible region grants you a right to erasure, you can submit that request through our support channel — by email or via the in-account support route. We handle it within the timeframe the applicable law sets and confirm the outcome through the same channel you used.
Access to 87bdd and the applicability of this policy depend on your local law and whether your region is eligible. If you are in a region where access is not permitted, this policy does not create an entitlement to use the service. Check your local legal position before accessing the site.