Live / Sports
This is the privacy policy that sits behind every sina101 account: what we record when you register, what a bKash, Nagad, Rocket or Bank Transfer deposit leaves on your account wallet, and how you can ask us to change it. Access depends on your local law and eligible regions.
Our privacy policy is written in plain terms, but it is still a policy, and a policy moves with the law where you actually sit. Bangladesh is the market we build for, and we keep account records on that basis. Even so, what we may collect, keep or hand over can differ depending on your local law and eligible regions, and where a local rule is stricter than this page, the local rule leads. In practice, the same framework covers everything from sign-up to a wallet reference. To run your account we need a name, a contact point, a password and the payment reference attached to a transaction. When you send money through bKash, Nagad, Rocket, Upay or a Bank Transfer, the wallet or bank returns a reference so we can match the credit to your account wallet. That match is the reason we ask, and we do not collect more than the match needs. We also keep an activity record on the account side: sign-in events, the settings you change, messages you send our support routes and the pages you open in the lobby. Two reasons. First, so you can see your own history. Second, so we can answer a question about a transaction without guessing. You decide what extra you share. Cookies beyond the ones that keep you signed in can be turned off in your phone or desktop browser settings at any time. No part of this page cancels a legal duty we hold to keep or disclose a record.
Think of the policy as the fence around your account. Inside it sits everything you do while signed in to sina101: opening an account, resetting a password, moving money through bKash, Nagad, Rocket, Upay or a Bank Transfer, and every session in the lobby. Outside it sits anything a different company runs on its own terms. A wallet app you use to fund a deposit, a browser you install, a page we link to but do not operate, those sit under that company's own privacy terms rather than ours. Where a third party hands us a reference to complete a payment, that reference comes inside the fence along with your transaction. So the split is simple to check: your account, your transactions and your lobby activity are ours to explain, and somebody else's product is theirs.
Registration details, sign-in events, password resets and the device sessions attached to them sit inside this policy. Open your account page and read the settings shown there to see what we hold about how you get in and which parts you can change yourself.
Every credit and debit through bKash, Nagad, Rocket, Upay or a Bank Transfer is covered, including the reference the wallet or bank returns to us. Your account wallet shows the transaction record, so you can match what we hold against what you sent.
Time spent in the lobby, the categories you open and the titles you launch sit inside this policy too. That takes in slots and live tables from Pragmatic Play, PG Soft, Spadegaming, PlayStar and Microgaming, plus titles such as Crash Skyward and Roulette LuckWave.
A wallet app, a browser, or a page we link out to is governed by that company's own privacy terms. We cannot change or explain their records on your behalf. Ask them directly, and treat their terms as separate from this policy.
Rights only matter when there is a door to knock on, so here is where each one sits. Want to see what we hold? Sign in, open your account page and read the profile and transaction sections there, because that is the same record our team works from when you write to us. Spotted a misspelled name or an old phone number? Update it in the settings shown on that page. If a field sits locked because a payment reference depends on it, our support route can walk you through the change. Questions about a single transaction move fastest when you quote the wallet reference, since a bKash, Nagad, Rocket or Bank Transfer reference narrows the search quickly. If you would rather not keep the account open, tell us through the published support route and we will set out what closes with it and what we are obliged to retain. Ask for a copy of your details and we will point you to the record or send what that route allows.
Open your account page after signing in and read the profile and transaction sections. That view is the same one our support team opens when you raise a question, so you can check the details yourself before writing to us.
Name, contact point and password can be changed from the settings on that page. If a field sits locked because a payment reference is tied to it, ask through our support route and follow the steps given for that particular case.
Quote the wallet or bank reference from your bKash, Nagad, Rocket, Upay or Bank Transfer and we can trace it against your account wallet. Keep each message to one reference so the record stays easy to follow.
Tell us through the published support route and we will set out what closing removes and what we must keep for legal or accounting reasons. Expect a written reply you can hold on to rather than a verbal answer.
One question, one route, so pick the door that fits. If your question is about a transaction, bring the wallet reference with you. If it is about the account itself, sign in first so the team can see the record you are asking about. Our contact points are the ones published on this site: the support email in the footer, the live chat widget that sits in the lobby, and the help form inside your signed-in account area. Nothing else is ours, so treat any other address claiming to speak for us with care. Messages are read in the order they arrive and answered in English for Bangladesh. If a channel is not published here, we cannot confirm or deny anything through it.
The address in the site footer is the one we publish for written questions. Include your account contact point and, for anything transaction-related, the bKash, Nagad, Rocket or Bank Transfer reference so the record can be found on the first read.
The chat widget you see while signed in connects you to the same support team for short questions about a session, a setting or a page that will not open. Keep your account open in the same browser so the details match what you are describing.
Signed-in help forms carry your account reference automatically, which saves explaining who you are. Use it for privacy requests such as a copy of your details, a correction, or a question about what happens when an account is closed.
Records are only as good as the care behind them. Access to account data inside our operation is tied to the job being done, so a support agent answering a wallet question works from your transaction record and not from anything unrelated to it. Passwords are held in a form that cannot be read back in plain text, and signing in is how the account is matched to you. Cookies are split by purpose: the ones that keep a session alive, and the ones that help us see which pages actually get used. You can refuse the second group in your browser. Retention follows what the record is for, so an open account keeps its history while a closed account keeps only what a legal or accounting duty requires.
Account data is opened by the people who need it for the task in hand, whether that is a payment query, an account change or a support reply. We do not hand your wallet references or contact point to another company for its own use.
Session cookies keep you signed in between pages, while the others help us see how the lobby gets used. Turn the second group off in your phone or desktop browser and the site keeps working, though some saved preferences may reset on your next visit.
Sign-in is the gate to your record, so choose a password you do not reuse anywhere else and change it from your account settings whenever you want to. If you think someone else has reached the account, use the published support route straight away.
An open account keeps its transaction and session history so you can check it yourself. After closure we keep only what a legal, tax or dispute duty requires and remove the rest. The support route can tell you which category your request falls into.
These are the questions that arrive most often about this policy, grouped so you can find yours without reading the whole page again. Each answer points to the route that resolves it, whether that is your account page for records you can change yourself or the published support route for anything that needs the team. If your case is not here, send the question anyway. Quote the wallet reference where a transaction is involved, and say plainly what you want to happen next.
A name, a contact point, a password and the payment reference attached to your first transaction. That is the base record, and everything else builds on activity: sign-in events, the settings you change and the messages you send to our published support routes.
Sign in and open your account page for the profile and transaction sections. For anything stored beyond that view, ask through the published support route and we will point you to the record or send what that route allows.
No. The cookies that keep you signed in are needed for the account to work, but the others only help us see how pages get used. Turn those off in your browser and the lobby still opens, though saved preferences may not stay.
Change whatever the settings allow from your account page. If a field sits locked because a payment reference depends on it, raise it through our support route with the wallet reference and follow the steps given for your case.
Your transaction through bKash, Nagad, Rocket, Upay or a Bank Transfer is covered on our side, while the wallet app itself runs on its own privacy terms. Keep the reference so both records can be matched if a question comes up.
Only as long as a legal, tax or dispute duty needs them, and then the rest goes. Ask through the published support route and we will explain which category your account falls into before any of it is removed.