Mobile / Casino
hu99 holds a small, defined set of records about you - your account profile, the wallet reference behind each bKash, Nagad, Rocket or Upay transfer, and the browser logs your device leaves - and this page sets out what we keep, why we keep it and how you ask us to change or remove it. Access to the service depends on your local law and eligible regions.
We treat this policy as a working document, not a one-time notice. When you open an account with hu99, you hand over a small set of records: the email address or phone number you register with, the display details you choose, the wallet reference you use for a bKash, Nagad, Rocket or Upay transfer, and the technical logs your browser leaves behind. We keep those records so you can sign in, so a wallet transfer can be matched to your account, and so a question you raise can be answered without you explaining it twice. What we can offer is not the same in every country. Whether you may hold an account at all depends on your local law and eligible regions, and our handling of your data sits inside that same line. If the service is not open where you live, this page still explains how we treat records we already hold and how you can ask us to delete them. We do not sell your account details. They move only when a transfer has to be confirmed through the wallet you picked, when our own team needs the record to settle a ticket you opened, or when a lawful request obliges us to hand it over. Nothing else leaves our systems, and nothing is attached to a public profile. Cookie control stays with you too. Clear or block them in your phone or desktop browser and the lobby still loads; only the small conveniences that remember your last screen may no longer follow you between sessions.
Some parts of your relationship with us are covered here; others live on separate pages. This policy follows the data itself - the profile you build at registration, the wallet reference left by a bKash, Nagad, Rocket or Upay transfer, and the browser logs written while you move between the lobby, the live rooms and the slot pages. It does not set how a game settles, and it does not govern a wallet company's own application. If a transfer looks wrong on the wallet side, that record sits with them; the reference we hold is the one we can look at with you. Check the four blocks below before you write to us, because starting in the right place saves a round trip. Your own device settings belong in that last block, since cookies are stored on your phone or desktop, not on our side alone. Anything outside those lines is someone else's to answer, and we will point you there rather than guess.
The email address or phone number you register with, your chosen display name, and the sign-in history attached to your account all sit inside this policy. If you change any of those details, the update lands in the same record we would quote back to you.
Each bKash, Nagad, Rocket or Upay transfer leaves a reference that we match to your account wallet. The reference, the amount state you see and the linked ticket are covered here. What the wallet company does with the same transaction in its own app is outside our reach.
Pages you open, such as a live room like Baccarat Jungle, and the cookie set written by your browser fall under this policy too. We read those signals as a group to keep the lobby loading cleanly and to see which screens deserve a second look.
Your wallet app, your mobile operator and your browser vendor each publish their own privacy terms. We cannot change what they collect, and a question about their records goes to their support. We will still tell you which reference of ours to quote.
You have four practical moves under this policy, and none of them needs a special request form invented here. Sign in and check your profile if a display name, email address or phone number has drifted; correct it yourself where the field allows an edit. If a field is locked, write to the support route published on this site and tell us what should change. To see what we hold, ask for a copy of your account record and we will confirm the route and any identity step we need from you before handing it over. And if something looks wrong - a wallet reference from a bKash or Nagad transfer that never landed on your account - send the reference with your question so the first reply can be useful rather than a request for more detail.
Ask for a copy of your account record and we will reply with the route to follow and the identity step required before any file is handed across. Keep the request to your own account, since we cannot discuss a record that is not yours.
A wrong display name or an old phone number is usually editable from your profile once you sign in. Where a field is locked, the support route on this site is the place to raise it, and the change is logged against your account.
If a bKash, Nagad, Rocket or Upay reference is missing from your wallet history, send the reference number and the date you made it. That single message lets us look at the right record instead of asking you for it later.
You can ask us to remove your account record, and we will explain what has to be kept for a completed transfer and what can go. Cookies you clear in your own browser; we cannot reach into your phone to delete a file for you.
Questions about this policy go through the same published channels you already use for account help, so you are not hunting for a separate privacy desk. Use the contact route listed on this site and put the words 'privacy request' in your first line; that phrasing gets your message routed without a back-and-forth. Include the email address or phone number tied to your account so we can find you, and never send a wallet PIN or a one-time code through any channel - we will not ask for one. If your question is about a transfer, add the reference and the amount state you see on your account wallet. If it is about cookies, tell us the device and browser you were using. Nothing in that message needs to be formal; plain words are easier for us to act on than a long explanation.
The contact route published on this site reaches the team that handles account and policy questions. Mention privacy in the subject line, quote the email address or phone number on your account, and you will not have to repeat yourself when the reply comes back.
Once you sign in, your account area is where a record question starts, because the team can see the same profile you are looking at. Raise it there when the issue concerns a detail that is already on screen.
For anything tied to a bKash, Nagad, Rocket or Upay transfer, the reference number is the most useful thing you can give us. Add the date and the state you see on your wallet, and the first reply can be about the record itself.
Records stay with us only as long as they do a job. Your profile sits there while the account is open; transfer references are kept so a dispute can be traced later; browser logs roll off once they no longer help us keep the lobby stable. We will never ask for your wallet PIN or a one-time code in a message, and we ask you to keep your sign-in details off shared phones. Cookies get a plain explanation rather than a wall of switches: the ones that keep you signed in are separate from the ones that tell us which pages load slowly. If you want the reasoning behind a retention choice, ask and we will say which record is being kept and for what purpose. That explanation belongs to you, so it comes in the same plain words as this page, not in legal shorthand. Short version: we keep little, we explain it, and you can ask us to drop what is not needed.
The email address or phone number you registered with, your display name and your account state. This is the set we would hand over if you ask for a copy, and the set you can partly edit yourself once you are signed in.
Session cookies keep you signed in between pages; measurement cookies tell us where the lobby stalls. You can block either group in your browser settings, and the site will still open, though you may sign in again more often than usual.
Nothing is kept without a reason. A closed account's profile is scheduled for removal, while a transfer reference may be held longer so a question about that payment can still be answered. Ask and we will say which case applies to you.
One published route handles both account and policy questions, so use the contact page on this site. Put privacy in your first line and quote your account email or phone number. A request for a change comes back with the step we need next.
The six questions below come up most often when someone writes to us about their record, and short answers are better than a long page. Each one points at a route you can actually use: the contact page for a request, your profile for an edit, the wallet reference for a transfer that looks wrong. We have kept them in plain words on purpose, because a policy you cannot follow is not much use. If your question is not here, send it anyway - the team that answers these is the same team that reads the contact page, and a new question usually means a gap worth filling on this page later. Read the third answer first if you are only after a copy of what we hold about you. That answer explains the identity step, which is the part most people ask about twice.
It covers the records we hold about your account: your profile, the wallet references from your transfers, and the browser logs your device leaves. It also explains how you ask for a copy, a correction or a removal, and where to send the question.
We store the reference produced by a transfer so the payment can be matched to your account wallet, not your wallet PIN or your login for that app. Those credentials stay with you and with the wallet company, and we will never ask you to send them.
Yes. Send the request through the contact route on this site, quoting the email address or phone number on your account. We will reply with the route to follow and any identity step needed first, because the record is yours and should not go to anyone else.
Sign in and open your profile; a display name, email address or phone number can often be changed there directly. Where a field will not accept an edit, raise it through support and tell us what should change, and the update is logged against your record.
A closed profile is scheduled for removal, while a transfer reference may be kept longer so a later question about that payment can still be traced. Ask us which record is being held and why, and we will answer in plain words.
Access depends on your local law and eligible regions, and that boundary applies to the data we hold as much as to the lobby itself. If the service is not open where you are, this page still explains how to ask about records we already have.