Mobile / Sports
This page sets out what 554h records when you open an account, browse the lobby or move money through a mobile wallet, and what you can ask us to do with it. Everything here sits under the law that applies where you are, so some steps differ by eligible region.
Here is where we stand. We hold only what an account needs to work: the details you enter at registration, your sign-in records, the titles and pages you open, and the wallet movements that reach your account. That data runs the lobby, keeps the wrong people out, and lets us answer you properly when you write in. Anything past that, we ask about first. Your payment context sits inside this policy too. When you use bKash, Nagad or Rocket, the wallet keeps your PIN and its own terms; what reaches us is the confirmation arriving on your account wallet. We do not sell your details on. Cookies behave the same way: the essential ones hold your sign-in steady, and the optional ones you can switch off in the notice shown on your first visit. Because privacy rules travel with the country you are in, this policy is written to sit under the law that applies to you. What we may hold, how long we keep it and which requests we can carry out all depend on your local law and eligible regions. Where a request cannot be completed under your local rules, we say so and give the reason. One last habit of ours: if a clause changes in a way that touches your account, the new wording appears on this page with a fresh date at the top.
Not everything connected to your time here falls under one document, so it helps to see the edges. Your account sits inside this policy from the moment you register until you ask us to close it. Sign-in details, the titles you open, the wallet transfers that land on your account and the messages you send our support team all travel under the same handling rules. Two things sit outside. First, the wallet you pay from, whether that is bKash, Nagad or Rocket, carries its own terms, its own app and its own privacy stance, and you deal with that provider directly for anything about the transfer. Second, the slots and live tables you open in the lobby come from studios such as Pragmatic Play, PlayStar, CQ9, JDB and Joker; those titles load inside our pages, and the terms they arrive with belong to the studio that supplies them. Your account data stays with us either way, and no studio receives your registration details from this side.
Your registration details, sign-in records and the browser or device you use fall inside this policy. Once you open the account page and complete the steps there, everything you enter is held under the same rules written here, from your first sign-in onward and for as long as the account stays open.
Wallet movements tied to your account, whether a bKash deposit, a Nagad transfer or a Rocket payment, are recorded so you can see them in your account wallet. The provider's own rules still govern the transfer itself, and anything about that side sits with the provider.
The slots, live tables and sportsbook sections you browse in the lobby are covered on our side: which titles you open, when you open them and the pages you move through. Cricket markets and other categories register as browsing activity, nothing more than that.
Titles from studios such as Pragmatic Play, PlayStar, CQ9, JDB and Joker load inside our pages, and the game terms they carry belong to those studios. That is a content arrangement. Your registration details and wallet records stay on our side of the line.
Nothing on this page is a dead end. You can see what we hold, ask us to correct it, ask for a copy, or ask us to stop using it for an optional purpose such as marketing messages. Start inside your account: the profile area shows the details we have on file, which usually means your registered mobile number, your email and the wallet name attached to the account. If a field there is wrong, change it yourself and save; the update takes effect on your account straight away. When you want a copy of your records, or you want the account closed, send the request through a published support route and we will tell you what we need to confirm it is really you. That identity step is the one part we cannot skip, because it protects your account wallet as much as ours. If your local law gives you a right that is not listed here, say so in your message and we will look at it under the rules that apply to your region.
Open your account profile to see the registration details, sign-in history and wallet name we hold. If a field looks wrong, correct it there and save, because the change lands on your account immediately. Want the whole set in one document instead? Ask through a support route.
Changed your mobile number, or want a different email on file? Update it in the profile area, then finish the confirmation step shown on screen. Keeping those details current matters, since they are how we recognise you when you ask for a record or a later change.
Send your question through a published support route and keep the reference it returns. Name the field or the period you mean, and say what outcome you are looking for. Plain detail saves a round trip and keeps your request tied to the correct account record.
You can tell us to stop using your data for optional purposes, marketing messages included. Essential handling, meaning the running of your account, the recording of wallet movements and the duties your local law places on us, continues while the account stays open.
Privacy questions do not sit in a general queue if we can help it. They go to the team that handles account records, so a request about your data reaches the right desk the first time rather than being passed along. Three doors are open: the help area inside the signed-in side of the site, the support email published in our footer, and the form on our contact page. Use whichever one you already know. When you write in, say what you need rather than what went wrong. A line like 'I want a copy of my account records' or 'my registered number has changed' gets a cleaner answer than a long description of the day. Include the mobile number or email tied to your account so the request matches the right wallet and profile. One thing we will not do is print a response clock on this page, because how quickly a request closes depends on what you are asking for and on the identity check that comes first. What you can count on is a reply from a person, with a clear next step in it.
Write to the address published in our site footer. That inbox is handled by the team that keeps account records, so a request about your data does not get pushed around. A subject line that names your request, such as record copy or correction, reaches the right place sooner.
Sign in and open the help area from the account menu. It carries the steps for the requests we receive most often, including how to confirm who you are before a record is released. Follow the fields shown there and your request arrives already matched.
The contact page form is the shortest route if you would rather not use email. Pick the topic closest to your request, add the mobile number tied to your account, and send. The same team picks it up and replies through the contact details you leave.
Every request that touches your data passes an identity check before anything moves. That is the spine of how we work this area: we confirm the account is yours, we log what was asked, and we answer in writing so a record exists on both sides. Cookies follow the same logic. The ones that hold your sign-in steady stay on, the optional ones you set in the notice shown on your first visit, and that choice sticks to the browser you made it in. On retention, account records stay while the account is open and for the period your local law requires afterwards. Close the account and the active profile goes quiet; the transaction trail stays for the length the rules demand, then goes. Nothing is kept indefinitely by accident. Want that spelled out for your own case? Ask through a published support route and we will set out which records we hold, why each one stays, and how long it remains. The person answering can also tell you which of your requests your region lets us carry out.
What you enter at registration, the titles you open and the wallet movements on your account are held so the lobby, your records and our replies all work. Inside our team, access is limited to the people who need it to answer you.
Essential cookies keep you signed in and hold your session steady while you move between pages. Optional ones sit behind the notice on your first visit, where you set the side you want. That choice stays with the browser you made it in.
Your sign-in details and the confirmation steps on the account page are the front door to your profile. Keep your email and mobile number current, sign out on devices you share, and expect an identity check before we release any record to you.
Records stay while your account is open, plus the period your local rules set after that. To ask what we hold, request a copy or ask for a change, use a published support route and quote the mobile number on your account so the request matches cleanly.
Most of what reaches us about this policy comes down to three things: what we hold, who can see it, and how to change it. The short version is simple. We hold the details your account needs, we keep them inside the team that runs accounts, and you can ask for a copy or a correction through a support route. The longer answers sit below, written around the requests we actually receive rather than the ones a template would list. If your question is about a wallet transfer instead of your account record, start with the provider, since bKash, Nagad and Rocket each run their own side of that. If it is about something written on this page, ask us and we will answer under the rules that apply to your region. Either way, include the mobile number or email you registered with so your request is matched to the right account before we reply.
The registration details you enter, your sign-in records, the titles and pages you open, and the wallet movements that reach your account. That is the working set. To see it item by item, open your account profile or ask through a support route for a copy of your records.
Yes. Send the request through a published support route and we will confirm it is you before anything is released. Quote the mobile number or email on the account so the request matches the right profile, and we will prepare the record for you to read.
Open your account profile, change the field, and finish the confirmation step shown on screen. Mobile numbers and email addresses are the two worth keeping current, because we use them to recognise you when you ask for a record or a change later on.
Yes, and you set the optional side yourself in the notice shown on your first visit. That choice stays with the browser you made it in. The essential cookies remain switched on, because the sign-in and your session will not hold without them.
The people who need them to run the account, answer your messages, or meet the duties your local law places on us. We do not hand your details to anyone else for their own use, and a wallet provider sees only the transfer it is asked to process.
When a clause changes in a way that matters to your account, the new wording appears on this page with a fresh date at the top. Read it when you open the account and again if you ask us for a copy of your records, so you always hold the current version.