Sports / Mobile
bb345 collects only the information needed to run your account, process payments through bKash, Nagad or Bank Transfer, and keep your session secure. What we collect, why we collect it, and how you can review or correct it — this page covers all of that clearly.
When you open an account with bb345 or use any part of the platform, you share certain information with us. This policy explains what that information is, the reasons we process it, and the choices available to you. We collect the details you enter during account registration — your name, contact information and the wallet or bank details linked to payment methods such as bKash, Nagad or Bank Transfer. We also collect activity data generated during your session: pages visited, games opened, and actions taken inside the account area. This data helps us keep the platform working correctly for your device, confirm transactions, and respond to support requests you raise. We do not sell personal data to third parties. Where we engage service partners — for example, game content studios supplying titles in the lobby — those parties receive only the minimum data required to deliver their service, and they are contractually bound to handle it appropriately. Access to and use of bb345 depends on your local law and the eligible regions we serve; if local law restricts your use, this policy still applies to any data you have already shared with us. Retention periods follow what is operationally necessary and legally required. You can request a review of your stored data at any time using the contact routes shown in this policy.
Payment details linked to your bKash wallet are used only to process your transactions and verify account ownership. They are not shared outside of what transaction processing requires.
Nagad wallet data entered in your account is handled under the same data-minimisation principle — stored securely, used only for the transaction or verification step it supports.
Bank Transfer records are retained for the period required to confirm transaction completion and meet any applicable record-keeping obligation. You can query any record through support.
This policy applies to all data collected through bb345 directly — account registration, wallet linking, in-session activity and support communications. It does not extend to third-party websites linked from our pages, or to the internal data practices of game studios whose titles appear in the lobby. Knowing what falls inside and outside the scope helps you decide who to contact when a question arises. For anything within bb345's own account and payment systems, the contact routes below are the right starting point.
Data collected when you log in, verify your identity or update account details falls fully within this policy. This includes session tokens, device identifiers and any changes made to your profile or linked payment method.
Payment activity — deposits and withdrawals processed through bKash, Nagad or Bank Transfer — is recorded in your account history. That transaction data is within scope; the payment provider's own data handling follows their separate policy.
Pages you browse, game titles you open and lobby categories you visit generate activity data we use to maintain platform performance. This in-session data is within scope and not shared for marketing purposes outside the platform.
Game studios supplying content to the bb345 lobby — and any external link you follow away from bb345 — operate under their own privacy terms. We have no control over how those parties collect or use your data once you leave our environment.
You have concrete choices available to you regarding the personal data bb345 holds on your account. You can ask us to show you what information is stored, correct anything that is inaccurate, or raise a question about how a particular piece of data is being used. These are not abstract promises — each one has a clear process. Start by opening the account settings area inside your logged-in profile; a number of data fields, including contact details and linked payment methods, can be updated there directly. For records you cannot edit yourself — transaction history, verification documents or session logs — submit a request through the support routes listed on this page. We will confirm receipt and handle the request according to what is technically and legally possible. Eligibility for certain data actions may depend on your region and local law; where a restriction applies, we will explain it in our response rather than simply declining.
Request a summary of the personal data held against your account. Open a support query, identify the data category you want reviewed, and we will respond with what we hold.
Contact information, linked wallet names and similar profile fields can often be updated directly inside account settings. For fields locked after verification, raise a correction request through support.
If you are unsure why a particular piece of data was collected or how it is being used, send a question through the published support route. We will point to the relevant section of this policy in our answer.
For any privacy matter that account settings cannot resolve — data deletion, objection to a specific processing activity, or a regional eligibility query — contact support directly using the channel that suits your device.
Every privacy question has a published route here. Use the channel that works for your device and the nature of your request. For simple account corrections, the in-app route is quickest. For a formal data review or a detailed query, written contact gives you a clear record of the exchange. We do not publish response time commitments we cannot verify — use the channel listed, state your account identifier and the specific data topic, and we will handle it from there.
Open the chat widget inside your logged-in account to raise a privacy question directly. Useful for quick clarifications about what data is held or how a specific field is used.
For written data requests — including review, correction or objection — send your query to the support email address published on the Contact page. Include your account ID and the specific data category your question covers.
The Help Centre section of the site contains published articles on account data, payment records and verification steps. Check there first for process questions before raising a direct support ticket.
Knowing how your data is stored and protected is a reasonable thing to want before sharing account details. Here is how we handle each major area — cookies, account security, retention and the process for requesting changes — in plain terms.
We use cookies to keep your session active, remember your login state and understand which parts of the platform you visit most. You can manage cookie preferences through your browser settings; some features may not work correctly if certain cookies are disabled.
Your account is protected by login credentials you set. We do not store payment PIN or wallet passwords — those remain with your bKash, Nagad or Bank Transfer provider. If you suspect unauthorised access, update your password immediately through account settings and contact support.
We retain your account data for as long as your account is active and for the period required after closure to meet any applicable record-keeping obligation. Transaction records linked to bKash, Nagad or Bank Transfer are kept for the duration required by the relevant processing obligation.
To update data that account settings cannot handle directly, or to request deletion of data that is no longer required, use the email support route. State your account ID, the data type and the action you are requesting. We will confirm what is possible under local law and eligible region rules.
These are the questions we actually receive about how your data is collected, what happens to it, and what you can do about it. If yours is not here, the support routes above are the next step.
We collect the information you enter during registration — name, contact details and any payment method you link, such as bKash or Nagad. We also collect in-session activity data to keep the platform working correctly for your device. We do not collect more than what account and transaction functions require.
Game content studios receive only the minimum data needed to deliver game sessions — typically a session identifier, not your full account profile. They do not receive your payment details or personal contact information. Each studio handles session data under its own terms.
Open a support request through live chat or email, state your account ID and specify that you want a data summary. We will review what is held and respond with the relevant details. Some fields can also be reviewed directly inside your logged-in account settings area.
Yes. Contact information and certain profile fields are editable inside account settings. For fields locked after identity verification — or for payment records tied to bKash, Nagad or Bank Transfer — submit a correction request through support with your account ID and the change you need.
Transaction records are retained for as long as operationally necessary and for any period required by applicable record-keeping obligations. After account closure, data is held only for the minimum period required. You can query a specific retention period by contacting support and referencing the transaction type.
Access to and use of bb345 depends on your local law and the eligible regions we serve. If your region restricts use, this policy still applies to any data you have already shared with us. Where a specific data right is unavailable due to regional rules, we will explain that in our response to your request.