Sports / App
This page explains what 111111bet collects when you open an account, browse the lobby on your phone, or move money through bKash and Rocket. Read it before you sign in, so you know what stays attached to your account and what you can ask us to change.
Privacy rules are not the same in every country, so take this page as our own statement of practice rather than a legal promise that overrides your national law. Where Bangladesh rules and the rules of the region you sign in from differ, the stricter protection for you is the one we try to follow, and access to the site still depends on your local law and eligible regions. We collect the details you type into the account form, the wallet reference attached to a bKash or Rocket transfer, and basic device data such as browser type and screen size. That device data is what keeps your session consistent when you switch from a phone on mobile data to a computer at home: one account, one wallet balance, no second password entry. We do not ask for more than the account flow needs, and we do not sell what you give us. Cookies do narrow work here. They hold your signed-in state, remember your language, and let the lobby reopen the category you last browsed. You can clear them in your browser whenever you like; the trade-off is a fresh sign-in. Transaction lines stay attached to your account wallet so that you and our support team can trace a bKash deposit or Rocket payment if a query comes up.
Where does this policy start, and where does it stop? It starts the moment you open our account form and it follows you through the lobby, the account wallet and any message you send our support team. It stops at the edge of our own service. Tap a link out to a payment app, a news page or a chat thread and that service answers to its own rules, not to this page; we cannot see or change what it collects. Inside our pages the boundary is easier to follow: your account record, the device details attached to each sign-in and your transaction history sit with us. Cricket and football categories you browse stay under the rules below. A wallet app you open in a second tab does not. If a partner service ever needs something from your account, we say so at the point where you are asked to share it.
Everything tied to your sign-in sits inside this policy: the email address and password you set, the device details we read at each login, and the session that keeps you signed in as you move around. That session is why your phone and your computer can show the same wallet balance.
A bKash deposit or Rocket transfer creates a record that stays attached to your account wallet. We keep the reference, the time and the amount so a mismatch can be traced later and so you can check your own history. We ask the payment app only for what confirms the transfer.
Cookies and local storage on our own pages do narrow work: they keep your language choice, remember the game category you last browsed and hold your signed-in state. Clearing them in your mobile browser is always your call, though you will sign in again on the next visit.
Anything you open outside our pages answers to its own privacy rules. That covers payment apps, social links and any account you hold elsewhere. We cannot read what those services collect, and we cannot delete a record that sits with them, so treat each outward tap as a separate relationship.
Privacy choices are easier to use when you know where they sit. Under this policy you can ask what account details we hold, ask us to correct a name, email or wallet reference that is wrong, and ask why a particular record was kept. You do not need a special form to start: send the question through the support route published on this site and we will tell you what we need to match the request to your account. Device and sign-in records are the one area where we may confirm who you are before anything moves. If you want a copy of your wallet history, your account page already shows the transactions, so ask us only when something there looks incomplete. We answer in the language you write to us in, and we will say plainly if a request falls outside what we can act on.
Ask us for a copy of the account details attached to your profile and we will say what is stored, why it was collected and which part came from your own entries. Sign-in and device records can be summarised the same way, once we have matched the request to your account.
A misspelled name, an old phone number or a wallet reference typed by mistake can be fixed. Some fields you edit yourself in your account area; the rest we change once you ask, and we request proof only where the field decides how a bKash or Rocket transfer is matched.
If a line on your wallet history does not match what you sent, tell us the reference and the time you see in the app. That one message does more than a long description, because it lets support find the same line in the account record.
You can ask us to delete details we no longer need for your account to run. Some records we must keep while an account stays open or while a transfer is being checked, and we will tell you which part we can act on and which part stays.
Questions about data go to the same place as any other account question, so you do not need a separate privacy inbox. Our site publishes its contact route, and the signed-in area carries a help link for anything tied to your profile, a bKash transfer or a Rocket payment. Write from the email address on the account where you can, because that is the shortest way for support to reach the record you are asking about. Tell us the page you were on and what you expected to see. If the question is about a cookie you cleared or a phone that keeps signing you out, mention the browser you use. We reply in the language you wrote in, and we will say plainly if a request needs something more from you. Access to the site itself depends on your local law and eligible regions.
Use the contact route published on this site for anything about your records, a bKash reference or a Rocket payment. Write from the email address on your account where you can, and include the page you were on. That is enough for support to reach the same line in your account.
Signed in already? The help link inside your account area is the shorter path for a profile change, a wallet reference typed wrong or a session that keeps dropping. It reaches the same team, and your account is already matched, so you skip the identity question.
For a browser that forgets your session, or a page that loads oddly on mobile data, tell us your browser and phone model. We look at what the session record shows rather than guessing, and we will say if the fix sits in your own browser settings.
How we hold data matters more than how we describe it. Account records sit behind your sign-in, and only the people handling account support open them. We keep what the account flow creates, meaning your profile, your wallet history and the device details behind each session, for as long as the account is open plus the stretch we need to answer a query about a transfer. Retention is looked over when an account closes, not left open forever. Your bKash and Rocket references live with the transaction line, not in a separate mailing list. Cookies are the smallest part of this and you control them from your browser. What we do not do is sell your details or hand your contact number to unrelated advertisers. If you spot a sign-in you do not recognise, change your password and tell us through the published contact route, because an early message is easier to act on than a late one.
Your profile, wallet history and sign-in records sit behind your sign-in. Support opens a record to answer a specific question, not to browse. We keep the fields the account flow creates and we do not add your contact number to any unrelated mailing list.
Cookies hold your signed-in state and your language choice so the lobby opens where you left it. They are not a tracking profile spread across other sites. You can clear site data from your browser at any time; the only cost is a fresh sign-in.
Records stay while the account is open, plus the period we need to answer a query about a transfer. When an account closes we look over what is still needed and remove the rest, rather than holding everything on the chance it becomes useful.
The device details attached to a sign-in exist for one reason: the same account should behave the same way on your phone and on a computer. If a device you do not recognise turns up in your own checks, message us and we will go through the record with you.
Not every privacy question needs a message to support, because a few answers already sit inside your own account. Before you write, open the wallet history in your account area. It shows the bKash and Rocket references attached to each transfer, and most questions about a missing line end there. Cookie questions usually end in your browser settings, where you can clear site data and sign in fresh. The rest of what reaches us falls into three groups: what we store, who can see it, and how to get a record corrected. The six questions below follow that order. Where an answer depends on your own situation we say so, and where local law or eligible regions change what we can do, we say that too. If your case is not here, the contact route on this site is the next step.
The details you type into the account form, the device and browser details read at each sign-in, and the transaction lines created by a bKash deposit or Rocket payment. We hold what the account flow needs to run and to trace a transfer, not a wider profile built from other sources.
Yes, but only as part of your account wallet. Each transfer leaves a reference, a time and an amount so you and our support team can match it later. We do not keep your payment app password, and we do not move those records into any mailing list.
You sign out and sign in again on the next visit. Cookies here hold your signed-in state and your language choice, so clearing them does not touch your account, your wallet history or a transfer already in progress. If you share a phone, clearing them after each session is a sensible habit.
Send the request through the contact route published on this site, from the email address on the account. Tell us which details you want: profile fields, sign-in records or wallet history. We may ask one confirming question before anything is released, and we reply in the language you wrote in.
It does. Your account, wallet and transaction history follow the sign-in rather than the device, which is why the same balance appears on a phone using mobile data and on a computer at home. Each new device simply adds a fresh sign-in record to the account.
Change your password first, then write to us through the contact route on this site with the time you noticed. We can look at the sign-in and device records attached to the account and tell you what we see. Access always depends on your local law and eligible regions.