Live / Mobile
2222bst keeps this page short on purpose: it sets out what we hold when you open an account and use your wallet, why we hold it, and how you ask us to correct or remove it. Read it once before your first deposit, and again whenever we tell you the wording has moved.
We treat your account details as something we hold on your behalf, not something we own. The policy is built around specific duties: we take in what an account needs to work, we keep it while your account is open plus whatever a record-keeping rule requires, and we give you a route to check it. When you move money through bKash, Nagad, Rocket or a bank transfer, the payment leg sits with the provider you picked; what we hold is the record attached to your wallet, so your deposits and withdrawals line up with your own statement. Sports or casino, the same rule applies, because your wallet is one wallet. Eligibility is not ours to hand out either. Our services are meant for regions where local law allows them, and if yours does not, an account cannot be used there — that is a limit we cannot write around, no matter what this page says. Two more things worth knowing: the wording live on this page is the version that applies if we change something, and your account area is where we point you when a material change lands. Read this before your first deposit, and keep the support route from the section below to hand.
The policy follows your account rather than every page you land on. Sign-in details, wallet balances, the entries behind each deposit and withdrawal, and the history that builds up in your account area all sit inside it. So do the cookies we set so a signed-in session survives a page change, and the device signals we read to flag a login that looks wrong. Support messages you send us are covered too. What sits outside? Your bKash, Nagad, Rocket or Upay account is yours and runs under that provider's own rules — if a transfer goes sideways, their terms govern the wallet side and we can only show you the matching record on ours. Studio titles are served into the lobby rather than installed by you, and any link you follow out of our site leaves this policy behind. Where a duty we carry in a market is stricter than this page, that duty wins — and we say so plainly instead of implying otherwise.
Everything tied to signing in sits inside this policy: the email you registered, the phone number on the account, the password only you set, and the login records that help us flag a session that does not look like yours.
Deposits and withdrawals made with bKash, Nagad, Rocket, Upay or a bank transfer stay inside the policy on our side of the transaction — the wallet reference, the amount and the status we receive. The provider's app and its own terms sit outside.
Pages you open in the lobby, tables you visit and studio titles served into the screen are part of the site we run, so the policy covers the session and preference data that comes with them. Links that take you to another company's site do not.
Anything outside our account and lobby runs on someone else's terms: the wallet provider, your bank, your mobile network and any site you reach from a link on ours. Where a request needs one of them, we tell you which, and their policy applies from that point.
You do not need a special reason to ask what we hold. Your account area is where the details we keep sit: sign-in email, phone number, wallet records and the log of changes. If something there is out of date, that is also where the correction starts — send the field name and the value you want through support, and we match it against the account before anything is written. For a copy of what we hold, use the published support route and say you are making a data request. We will tell you what can be handed over, what has to stay on file, and what local law allows us to hold back. If you would rather stop using the account, ask us to close it and we will set out what closes with it and what stays. If you think we handled something badly, raise it with us first, and we will look at it properly.
Open your account area and look at the profile block. Sign-in email, phone number, wallet history and the log of changes sit there, and you can see what we hold without writing to anyone. If a line looks wrong, that same block is where the correction starts.
Send the field name and the value you want instead through the support route in your account area. We match the request against the account before anything is written, so changes are made from a signed-in session rather than from a message alone.
If something about how we handle your data is unclear, ask in the first line of your message so it is routed as a policy question rather than a general query. Keep it specific — which page, which field, which record — and the answer comes back faster.
Payment questions need the wallet name and the reference number your provider gave you. With that line, we can find the matching record on our side instead of trading messages. The support route published in your account area is the one to use.
Policy questions usually come in two shapes: something you want changed, and something you want explained. Both start in the same place — the support route published in your account area. Sign in first, because most requests need us to see the account you are writing about; a message from an unverified address slows everything down. In your message, say which page or field you are asking about, and keep the wording of the question close to what you want answered. If your question is about a payment, have the wallet name and the reference number from the provider ready — bKash, Nagad, Rocket and bank transfers all give you one. That single line lets us find the matching record on our side instead of trading messages back and forth. If you are asking about data we hold, say so in the first sentence so it is routed as a policy request rather than a general query. We answer through the same route you wrote in on, unless you ask us to use a different one.
Sign in and open the support route from your account area — it is the same contact point used for wallet and lobby questions. Messages sent from a signed-in session are easier to match to the right account, which is why we point you there first.
Ask for a copy, a correction or a closure through that same route and label it as a data request in the first line. We reply on the route you wrote in on, unless you ask us to use a different contact point.
Name the page or field you are asking about and keep the wording close to the question you want answered. If you are asking about a record, the date you saw it and the account email help us find it quickly.
Three things do most of the work here: cookies, sign-in security and how long records stay. Cookies are what keep you signed in between pages and remember small preferences like your last lobby tab; the ones that only measure traffic can be switched off without breaking your account, and the setting lives in your browser. Sign-in security is deliberately plain — your password stays yours, and anything unusual about a login is handled in the account area rather than by email that could be spoofed. Retention follows purpose. Wallet records and transaction history stay while the account is open, because you need them and so does any audit; once an account is closed, most of it ages out under our retention rule, except the parts a legal or accounting duty requires us to keep longer. Payment details themselves are not something we store beyond the record attached to a transfer. If you want to know which category a particular record falls into, ask through support and we will tell you plainly.
A session cookie is what keeps you signed in as you move between pages, and a small preference cookie remembers things like the lobby tab you last opened. Measurement cookies can be switched off in your browser settings without affecting your account.
Your password is yours alone. Questions about an unusual login are handled inside the account area rather than over email that could be spoofed. If a login looks wrong to you, change the password and tell support through the published route.
Wallet records and transaction history stay while the account is open. After closure most of it ages out under our retention rule, while entries a legal or accounting duty covers are kept longer. Ask support which category a specific record falls into.
Policy requests go through the support route published in your account area, the same one used for wallet questions. Say in the first sentence that it is a data request, name the page or field you mean, and the reply comes back on the route you wrote in on.
These are the questions we get most often about how 2222bst holds and uses account data. If yours is not here, the support route in your account area is the place to send it.
What an account needs to run: your sign-in email, the phone number you gave us, your wallet balance and the record of each deposit and withdrawal. Payment names like bKash, Nagad, Rocket or a bank transfer appear only as part of that transaction record.
Yes. Write through the support route published in your account area and say you are making a data request. We will set out what can be handed over, what has to stay on file for record-keeping, and what local law allows us to hold back.
Only where it is needed to run the account. Your payment provider sees what a transfer requires, and lobby content is served into the page by the studios whose titles appear there. We do not sell your details, and anything beyond that has to follow local law.
Cookies are what keep you signed in when you move between pages in the same browser, so a refresh does not throw you back to the login screen. Measurement cookies can be turned off in your browser settings without closing your account.
Start the change from your account area rather than by message alone, then send the field name and the new value through support. We match the request against the account before anything is written, which is why it has to come from a signed-in session.
Ask us to close it and we will explain what goes with it and what stays. Transaction records generally age out under our retention rule, but a legal or accounting duty can require us to keep some entries longer. Support will tell you which category applies.