Sports / Live
bb335 keeps this privacy policy short and readable, because it sits behind every session you start, on a phone or on desktop. It sets out what we hold when you open an account, how cookies and wallet references are used, and how you can ask us to change or remove your details.
We wrote this page to explain how bb335 handles personal data for anyone who opens an account with us, and it applies to your use of the site, the account pages and the wallet attached to your login. It is a general statement, not a promise of a particular legal outcome: what we may collect, store and share depends on the law that applies to you and on the regions where access is allowed. In places where a service like this is restricted, this policy does not grant you access that local law withholds. Where we hold a payment reference, a bKash, Upay or Bank Transfer record linked to your wallet for example, we keep it so your own transaction history stays consistent and so our records match. We do not sell that data, and we do not hand it to unrelated parties for their own marketing. Cookies and similar storage help the site remember that you are signed in, keep your session steady when a page reloads, and show which pages load slowly on mobile data. You can clear them from your browser at any time, though doing so may sign you out. Rules differ between markets, so parts of this page may be read differently depending on where you are. Where local requirements are stricter than what is written here, those requirements come first. If you want something explained in plain terms for your own situation, write to us through the published support routes.
The policy follows your account rather than a single page. Anything you hand over while opening or using your login sits inside it: your email address, the details you type on the account page, and the records our systems create when you sign in, browse or move money through your wallet. What you read in the lobby, from game titles and category pages to the help text, is covered as site content, and we treat that side as published copy rather than personal data. Some ground sits outside. If you follow a link to a service we do not run, that service answers for its own handling, and you should read its notice before you share anything. Your own device, browser and network provider sit outside our scope too, along with any records you keep privately. The four parts below show where each item lands. If you are unsure whether something is covered, send the question through support and we will tell you directly. Access to this site always depends on your local law and the regions where access is allowed.
Everything tied to your login sits inside this policy: the email address you register with, the details you add on the account page, and the sign-in records our systems create each time you open a session on your phone or in a browser.
When you move money through bKash, Upay or Bank Transfer, we keep the reference needed to show that transfer in your wallet and to keep your own history accurate. That record stays linked to your account and is not shared for outside marketing.
Lobby pages, game titles, category lists and the help text you read on this site are our content and sit inside this policy. They are not personal data, but we apply the same care to what we publish and how each page behaves on your device.
Payment operators and any external page you reach from a link answer for their own data handling, not ours. Read their notice before you share anything there, and treat everything outside this domain as a separate relationship with its own rules.
You are not locked out of your own data. If you want to know what we hold, ask us and we will show you the records attached to your account: the profile details you entered, your sign-in history and the transaction references kept in your wallet. If something is wrong, you can change most of it yourself from the account page, and you can ask us to correct anything the page does not let you edit. You can also ask us to stop using your details for messages you did not ask for, or to close the account and remove what we are not required to keep. Some records stay with us because local rules expect them to, and we will say so plainly if that applies to your request rather than promising a deletion we cannot carry out. Every request runs through the published support routes, so keep the message clear and tell us which account it concerns. We answer in the order requests arrive.
Ask what we hold and we will show you the profile details, sign-in history and wallet transaction references tied to your login. Anything the account page already displays, you can open yourself before you write to us.
Most fields on the account page are yours to edit, including your email address, contact numbers and profile text. Where a field is locked because it was checked when you registered, ask support to change it and tell us why.
You can ask us to close your account and remove what we are not required to retain. Records that local rules require us to keep stay on file, and we will tell you which ones apply to your case before anything is cleared.
If you are unsure how the policy applies to something you did on the site, write to us with the date and the page involved. Clear detail helps us answer without sending the same question back to you.
Privacy questions need a real route, so keep this page to hand. We publish a contact path inside the account area, where you write from the same login that the request concerns. That link between message and account is what lets us check your records without asking you to prove who you are twice. The email address shown on our contact page is the second route, useful when you cannot sign in or when your question is about the account rather than something inside it. The third path is the support entry linked from the site footer and from the help text inside the lobby. Use it for general questions about this policy, your cookie settings, or what we do with the data tied to bKash, Upay and Bank Transfer references. We do not ask for your password or your wallet code in any message, and a request that arrives that way is not from us, so ignore it and use one of the routes above instead.
Sign in and open the support entry inside your account area. Writing from the same login the request concerns lets us match your message to the right records, so you do not have to explain which wallet or profile you mean.
Our contact page shows the email address for privacy requests. Use it when you cannot sign in, or when your question is about the whole account rather than a single page, cookie setting or wallet transfer you want explained. Tell us the address you registered with.
The site footer and the help text inside the lobby lead to the same support entry. Use it for questions about cookies, what we store, or how we treat the bKash, Upay and Bank Transfer references attached to your wallet. It works whether or not you are signed in.
Handling data well is mostly about consistency, so that is where we put the effort. Access to account records is limited to the people who need it to answer your request or keep the wallet ledger accurate. The same login controls that protect your account also protect the records behind it. Your login details are yours to protect too: on a shared phone, sign out after a session instead of leaving the page open. Cookies are described in this policy because they are part of the service. A session cookie keeps you signed in, a preference cookie remembers your language and layout choices, and measurement cookies show us which pages load slowly on mobile data. You can clear them from your browser, though you will be signed out when you do. Retention follows what the record is for. Transaction references tied to bKash, Upay or Bank Transfer stay while accounting and local requirements need them, while sign-in records are kept only long enough to help us spot misuse. Ask us any time what applies to your account.
Records tied to your account are handled by the team that answers support and keeps the wallet ledger accurate. We do not pass your details to unrelated parties, and we do not use your email for messages you did not ask to receive.
Session cookies keep you signed in while you move between lobby pages. Preference cookies remember your language and layout. Measurement cookies show which pages load slowly on mobile data. Clear them in your browser at any time, and you will need to sign in again.
Your password and your session are the keys to your own records, so sign out on a shared or borrowed phone. If you think someone else has reached your account, write through the published route and we will go through the sign-in history with you.
Transaction references stay while accounting and local rules need them, and sign-in records are held only as long as they help us spot misuse. You can ask what we hold, or request a change, through the support entry in your account.
The email address you register with, the details you type on the account page, and the records our systems create as you sign in and use your wallet. Transaction references from bKash, Upay or Bank Transfer are held with the account so your own history stays accurate.
You can clear cookies in your browser settings and read what is public, but the session cookie is what keeps you signed in, so the account area will not work without it. Preference and measurement cookies can be removed without affecting your login.
It covers your use of the site wherever you open it, but what we may collect and keep depends on the law that applies to you and on the regions where access is allowed. Where local rules are stricter than this page, those rules come first.
Write through the support entry inside your account, or use the email address on our contact page if you cannot sign in. Tell us which account it concerns and what you want to see, and we will answer in the order requests arrive.
We do not sell your details or pass them to unrelated parties for their own marketing. Payment operators handle their own side of a transfer, and any external page you reach from a link answers for its own data handling.
Ask us to close the account and remove what we are not required to keep. Records that local rules expect us to retain stay on file, and we will tell you which ones apply rather than promising a deletion we cannot carry out.