Live / App
At um22 we set out plainly what account data we hold, why we hold it, and the choices you keep over it. Read how the records tied to your wallet, your sessions and your support messages are handled — and where your local law shapes what we can offer you.
This policy explains what um22 does with the details you give us when you open and use an account. It is written for readers in Bangladesh, but it is not a promise that every service is open everywhere: access depends on your local law and on the eligible regions we can serve. Where a rule in your area says something different from what is written here, that local rule takes precedence for you. We collect three broad kinds of detail. First, what you hand over when you set up your profile, such as the name and contact details attached to it. Second, what your activity produces — the deposit and withdrawal entries recorded when you move money through bKash, Nagad, Rocket, Upay or a Bank Transfer, plus the games you open. Third, the technical record your browser leaves, like device type and session timestamps, which keeps the signed-in area stable. We use these details to run your account, to show your wallet history correctly, to answer questions you send us, and to meet the record-keeping duties that apply to us. We do not sell your profile to outside advertisers. You stay in control of most of it. You can ask what we hold about you, ask us to correct a detail that is wrong, and close your account when you want to stop using it. Use the published support routes on this site so your request reaches the right desk. Keep your login details to yourself — anything you share with a third party sits outside our control.
One policy, four separate areas. It covers the signed-in half of um22: the details on your profile, the wallet entries behind your deposit and withdrawal history, and the messages you send to our support desk. It also covers the technical layer — the cookies and session records that keep you logged in while you move between Cricket Betsport and a slot room. It does not cover what happens after you leave us. If you tap out to a bank page, a mobile wallet app or any other outside service, that company runs its own rules and its own data handling. We cannot answer for a page we do not operate, and we cannot change what another operator records about you. Third-party game content is a middle case. Titles supplied by Spadegaming, Pragmatic Play, CQ9, Joker and Bigtime Gaming load inside our lobby, yet a studio keeps its own technical records of the session. Where our policy and theirs touch the same event, we explain what we hold; read their notice as well.
Your login details, contact records and profile fields sit inside this policy. When you sign in from a new phone, the session data that shows it was you is covered here too, and you can ask us to put right anything that looks wrong on your profile.
Every deposit and withdrawal entry is recorded against your account, whether you moved money through bKash, Nagad, Rocket, Upay or a Bank Transfer. Those entries stay attached to your wallet history, and you can see them in the signed-in area whenever you want.
Pages you open, games such as Slot Kingdom or Roulette Livestream that you load, and features you use inside the lobby leave a technical trail. We keep it to run the product, spot a broken page and hold the session steady while you switch between markets.
Payment apps, bank portals and any link that takes you off our pages are outside this policy. Those operators set their own terms and record their own data. Read their notice before you share details with them, because we cannot change what they hold.
You do not need to wait for a problem to use the choices in this policy. Start inside your account area, where the profile fields, wallet history and session list live. If a phone number, name or email is out of date, update it there so the record we hold matches what you actually use. Want to know everything tied to your account? Send that request through a published support route and we will point you to the records we hold. The same route handles a correction you cannot make yourself, and a question about how a specific entry was logged. Closing your account is your call too. Tell us you want to stop using it, and we will explain what happens to the records afterwards — what we delete, what we have to keep, and how long the remaining entry stays. Nothing here costs you anything to ask.
Ask for the profile fields attached to your account and the wallet entries behind your history. Send the request from the contact route shown on the site so it reaches the team that handles data, and we will point you to the actual records instead of leaving you to guess.
Phone number, email or name out of date? Change what is editable in your account area first. If a field is locked, tell support which one it is and why it changed, and we will look at whether it can be updated without disturbing checks already on your profile.
Not sure why an entry was logged, or which device created a session? Put it to us through the same route you use for account help. Mention the date you saw it and we can pull the matching record rather than answering in general terms.
Tell us you want to stop using the account and we will walk you through what happens next: what is removed, what stays for record-keeping, and how the remaining entry is handled afterwards. You do not need a reason to ask.
Questions about this policy go through the same support routes published on the rest of the site. There is no separate privacy hotline to hunt for — the contact points you already use for account help also carry data requests, and that keeps one record of your query instead of three. When you write in, say which part of the policy you mean. A wallet entry question, a cookie question and a request to close an account travel different paths inside our team, and a clear subject line gets you a straight answer sooner. Add the email address registered to your account so we can match the request to the right profile. If you are writing about something you saw on screen, a screenshot helps. Jot down the page you were on, roughly when it happened and which device you used — mobile browser or desktop — and we can trace the session. Anything you send us is handled under the same rules described on this page.
The contact form published on um22 is the first place to send a policy question. Write which part of the notice you mean, add the email on your account, and the message reaches the team that handles data requests. Nothing about the route changes because your question is about privacy.
Sign in and use the account help section for anything tied to your profile, wallet history or session record. Requests raised there arrive with your account reference already attached, which saves a round of back-and-forth before we can look at the record you are asking about.
Whether you use the form or the account help section, add the email registered to your account, the part of this policy you mean, and the date of any entry you are asking about. That detail lets us find the right record on the first pass.
Data handling at um22 follows a simple split: what we need to run your account stays, and what we no longer need goes. Profile details and wallet history stay while the account is open, because the deposit and withdrawal entries behind them have to be traceable. Session records live for a shorter window and are then cleared. Security sits around the signed-in area. Your session is tied to the device you logged in from, so signing in on a new phone asks you to confirm again. Keep your password and any code we send to yourself, and log out on a shared device. Cookies do a narrow job: they hold your login and remember basic display settings. They are not there to follow you across other sites, and you can clear them in your browser whenever you like — though you may have to sign in again. To change something we hold, use the support routes published here. We will say what can be changed and what has to stay for record-keeping.
Profile fields, wallet entries and support messages stay linked to your account while it is open, and session records are held for a shorter window. We keep this set to run the account, show your history correctly and meet the record-keeping duties that apply to us.
Cookies keep you signed in and remember basic display settings. They are not used to trail you across other sites. Clear or block them in your browser whenever you want, and expect to sign in again afterwards, because the login cookie goes with them.
A session is tied to the device you signed in from, so a new phone asks you to confirm again. Keep your password and any code we send to yourself, sign out on a shared device, and use the account area to spot a session you do not recognise.
Use the support route published on this site to ask for a change or a removal. We will explain which parts can be updated, which have to stay for record-keeping, and how long the rest remains attached to your account after you send the request.
These are the questions we get most about this policy. Each answer points to the route that resolves it: your account area for your own records, the published contact page for a request, and your browser settings for cookies. If your question is not here, the answer usually depends on a detail we can only see after you sign in — the date an entry was logged, or the device a session came from. So ask through support, and we will look at the actual record rather than guess at one. Two things are worth knowing before you read on. First, this policy is written for readers in Bangladesh, and what we can offer still depends on your local law and on the eligible regions we serve. Second, nothing on this page promises a service level; it explains what we hold, why we hold it, and how you ask us to change it.
Your sign-up fields — name, email address and phone number — plus the wallet entries behind your deposit and withdrawal history and the session records created when you sign in. Anything you send to support is attached to the same account reference. That set is what this policy describes.
Yes. Sign in and the account area shows your profile fields, your wallet history and your recent sessions. For a wider request, send a message through the published contact route and we will point you to the records tied to your account.
Update it yourself in the account area when the field is editable. If it is locked, or the entry came from a step you cannot repeat, ask support to change it and say which field you mean. Include the email on your account so we can match the request quickly.
We use cookies to keep you signed in and to remember basic display settings, not to follow you across other sites. You can clear or block them in your browser settings at any time. Expect to sign in again after you clear them, since the login cookie disappears with the rest.
Only our side of it. When you deposit through bKash, Nagad, Rocket, Upay or a Bank Transfer, the wallet entry is recorded on your account and is covered here. The app or bank you used keeps its own records under its own notice, which we cannot change.
Send a request through the support route published on this site and say you want your account closed. We will explain what gets removed with it and what we have to keep for record-keeping, then confirm once the request has been handled on our side.