Sports / Live
This policy explains exactly what data bdbd33 collects when you use your account, how we store it, and what choices you have — including records tied to your bKash, Nagad or Rocket wallet activity. Access and data rights depend on your local law and eligible region.
When you open an account on bdbd33, we collect the information needed to run your account and process transactions through the payment channels you choose — bKash, Nagad, Rocket or Bank Transfer. This includes your registration details, wallet identifiers linked to your deposits and withdrawals, device type, and your activity log within the platform. We do not sell your personal data to third parties. Data is retained for the period required to maintain your account and meet any obligations applicable in your eligible region — the exact retention period depends on local law, which you should review independently. Cookies and similar tracking are used to keep your session active, remember your language preference, and measure how sections of the site are used. You can manage cookie settings through your browser at any time. Where we share data with payment processors — such as the services behind bKash or Nagad transactions — that sharing is limited to what those processors need to complete your requested transaction. No studio partner, including Spadegaming, CQ9, JDB, PlayStar, Joker or PG Soft, receives your personal account data; they supply game content only.
Not every part of your experience falls under this policy in the same way. Some areas are fully within our control; others involve third-party services that operate under their own policies. Understanding the boundary helps you know where to direct questions about your data.
Login sessions, account registration data, security settings and session history are all within scope. Any data created when you access the platform — on mobile or desktop — is covered by this policy and stored under the practices described here.
When you initiate a deposit or withdrawal using bKash, Nagad or Rocket, the transaction data we hold is covered here. However, the payment processor's own records are governed by their separate privacy terms — we do not control what they retain.
Your session history within the game lobby — which titles you opened, session length — is logged under your account and falls within this policy. Game studios like PG Soft or CQ9 do not receive personally identifiable information about you from us.
Any external site you reach by following a link from bdbd33 operates outside this policy. We have no visibility into or control over those sites' data practices. Check their own policies before sharing any personal details with them.
Your account comes with practical options to manage the data we hold about you. You can review your account details — name, contact information, linked wallet identifiers — directly from your account dashboard after login. If something looks wrong, you can correct it from the same settings page; follow the fields shown there and save the change. For records you cannot edit yourself, such as completed transaction logs for bKash or Nagad activity, you can raise a data query through our support channel and we will respond as quickly as our process allows. Where local law in your eligible region provides a right to request deletion or restrict processing, you can raise that request by contacting us at the address shown in the support section below. We will acknowledge your request and explain what action is possible given any legal retention obligations that may apply. These rights depend on your jurisdiction — we cannot confirm their exact scope for every region, so review your local rules or seek independent advice if needed.
Log in and open your account dashboard. Your registered details, linked wallet information and session history are visible there. No additional step is needed to read what we hold about your account.
Find the relevant field in your account settings and update it directly. For fields that are locked — such as your registered payment identifier — contact support with your request and we will process it through our verification steps.
If you have a question about a specific record — a transaction log, a session entry, or how a piece of data was collected — reach us through the contact paths listed in the support section. We respond to each query individually.
Where your local law gives you this right, send your request through our support email. We will confirm receipt, tell you what we can action, and explain any retention obligations that limit what we can delete at that time.
Questions about how we handle your data, requests to review records, or concerns about a specific transaction entry can all be directed to our support team. Use the channel that works for you — each path reaches the same team that handles account and data queries.
Send your data query or correction request to our support email address. Include your registered account identifier so we can locate your records without delay. We handle each message individually.
Open the live chat widget from your account page once you are logged in. This is the fastest path for straightforward questions about what data your account currently holds or how a wallet record was created.
For self-service review, your account dashboard after login shows your current registered details and linked payment identifiers — bKash, Nagad or Rocket — without needing to contact support at all.
The practices below describe how bdbd33 manages the data it holds, from the moment you register to the records created each time you use your account wallet. These are not abstract commitments — each point reflects something you can verify or act on from your account.
We use cookies to maintain your login session and measure site usage. You can adjust or clear cookie settings through your browser's privacy menu at any time. Turning off certain cookies may affect how your session behaves during account navigation.
When you use bKash, Nagad or Rocket, your wallet identifier is shared only with the processor completing that transaction. We do not store full wallet credentials on our side beyond what your account record requires for display in your dashboard.
We keep your data for as long as your account remains active and for any period required under applicable rules in your eligible region. When an account is closed, we follow the retention schedule relevant to that jurisdiction — not a fixed global timer.
All data-related requests — corrections, queries, or restriction requests — go through our support team. Reach us via the email or live chat paths shown in the support section. We confirm receipt and respond with a timeline specific to your request.
These are the questions we hear most often about how we collect, store and manage account data. If your question is not covered here, the support team handles individual queries through email and live chat.
We collect the details you enter at registration — name, contact information and the wallet identifier you link for transactions such as bKash or Nagad. Device type and session activity are also logged. We collect only what is needed to operate your account.
No. Studios such as PG Soft, CQ9, Spadegaming and others in our game lobby supply game content only. They do not receive your personal account data. Data sharing is limited to the payment processors that handle your bKash, Nagad or Rocket transactions.
Log in and open your account dashboard. Your registered details, linked payment identifiers and account history are displayed there. For records that are not visible in the dashboard, contact our support team and we will retrieve them for you.
Yes, where local law in your eligible region gives you that right. Send your deletion request through our support email with your account identifier. We will confirm what can be removed and explain any data we are required to retain under applicable rules.
Transaction records linked to bKash, Nagad, Rocket or Bank Transfer are stored in your account log and visible in your dashboard. The payment processor handling the transaction also holds their own record under their privacy terms, which operates separately from ours.
Access to bdbd33 and the data rights that apply to your account both depend on your local law and eligible region. We cannot confirm the precise scope of data rights for every jurisdiction. Review your local rules or seek independent advice if you have specific legal questions.