Slots / Sports
bee98 keeps one privacy policy for every account holder, and this page sets it out in plain terms: what we record, why we record it, and how you ask us to change or remove something. It covers your signed-in account area, the wallet records behind your bKash, Nagad and Rocket transfers, and the support routes you use from a phone or a desktop.
Privacy here comes down to a few honest questions: what do we hold, why do we hold it, and who gets to see it? For bee98 the answer starts with the account you create. We record the email address and contact number you give us at sign-up, the password you set, and the profile details you add later. When you move money through your wallet, we keep the reference numbers that bKash, Nagad or Rocket return to us, because those references are how a disputed transfer gets checked. We also log basic device and browser data, such as the phone model, the browser you used and the country your connection came from, so a sign-in from an unusual place can be spotted before it turns into a problem. Your data is used to run your account, support wallet verification, answer the questions you send us, and keep the lobby loading properly on your device. We do not sell it, and we do not pass it to another company for its own marketing. Here is the part that depends on where you are. What we may collect, how long we may keep it, and which requests we must honour are set by the law that applies to you, and access to the site depends on your local law and eligible regions. Nothing on this page overrides those rules. When the practice described here changes, we update this page rather than quietly changing it somewhere else, so the version you read today is the version we hold to.
One policy, one account, and a boundary we try to keep clear. Everything you do while signed in to bee98 sits inside this policy: opening your account, moving money through your wallet, and asking us for help. It does not follow you into places we do not run, and that line matters when you decide what to share and where. Take the wallet first. A bKash, Nagad or Rocket transfer happens partly in an app you hold, so the details you enter there are handled by that provider under its own terms. We see the reference that comes back to us. The same idea applies to a studio page you open in a new tab, or to a link a friend sends you. Our rules cover our account area, our lobby and the records behind them. If something is unclear, read the four areas below, then check the matching screen in your own account.
Everything tied to the sign-in you use falls under this page: the email and contact number on file, the password you set, the browser details we note when you open the site, and the preferences saved in your account area. If you can see it after signing in, this policy governs how we hold it.
When you add funds or withdraw, the transfer you make through bKash, Nagad or Rocket leaves a record on our side: the reference number and the status we are shown. We keep that record so a later query can be traced. The app you used holds its own record under its own terms.
Lobby pages, game titles and the policy pages you are reading now sit inside this policy. Slot and table titles from CQ9, JDB, Bigtime Gaming, Joker and Spadegaming load in your browser as part of the lobby, and the cookie choices you set shape what the site remembers between one visit and the next.
Anything we do not run sits outside this policy: the wallet app on your phone, a studio page you open in a new tab, or a link a friend sends you. Those providers publish their own privacy terms, and how they treat your details is their responsibility. Read them before you agree to anything there.
Nobody should have to write an email to find out what a site holds about them. Start where you already have a key: your account area. Sign in and you can open the profile screen, see the contact email and number we hold for you, and change what has gone out of date. That is the quickest correction available, and it takes effect on the record we use to reach you. If you want a copy of what we keep, or you want us to stop using your number for anything beyond account notices, ask us. Send the request through a support route on this page and say clearly what you want changed. We may need to confirm the account is yours before we act, which is the same check that protects you if someone else ever tries to sign in as you. If a request is one we cannot meet under the law that applies to you, we will tell you that plainly instead of leaving you guessing.
Sign in and your profile screen shows the email and mobile number we hold for you, plus the wallet records attached to your account. Read it once and correct anything that has gone stale. Keeping that screen current is the simplest way to make sure account notices reach the right place.
The contact email and number on your account are editable in the account area, so a changed mobile or a new email does not need a support request. If something cannot be edited from your side, send the request through a published support route and name the detail you want changed.
Wording here can be read two ways, and you should not have to guess which reading applies to you. Write out the line you want explained, send it through a contact route published on this site, and keep the reply. Where the answer depends on your local law or eligible regions, we will say so.
If a transfer through bKash, Nagad or Rocket shows a status you do not recognise, raise it from inside your signed-in account so the record is already in front of us. Quote the reference number from your app and the date you sent it. That gives us something concrete to trace.
For anything about this policy, we ask you to use a route you can point back to. The contact options we run are published on the site itself; open them from the page you are on rather than relying on a number someone messages you. That habit protects you, because a channel we do not publish is not a channel we can confirm as ours. If your question is about the account, sign in first and raise it from inside the account area, where the record is already in front of us. If it is about the policy wording itself, the written request route suits better, because you can set out exactly which line you want explained. Include the email on your account so the message matches the right record, and keep the reply in your inbox. We answer what we can see and tell you when we need the account holder to confirm something.
Sign in and raise the query from where the record sits. Your account area is the route where the history is already in front of us, because the email and wallet references are attached to the account you used. Say what you expected to see and what you saw instead.
Every contact route we run is published on this site. Open it from the page you are on rather than through a number or a link someone messages you, because a channel we have not published is not one we can confirm as ours. Keep the reply thread with the query.
For anything about this page itself, a written request works well: name the section you are asking about and what you want done, whether that is a copy of what we hold, a correction or the closure of your account. Include the account email so the request lands against the right record.
Data care is mostly invisible, so here is what you can see from where you sit. Your account area is where we ask you to keep your own side current: check the contact email and mobile number on file, and change the password if you think someone else has seen it. If you lose access, the reset flow on the sign-in screen is the route back in, and we ask you to use it rather than send a password to anyone. On our side, the people who can open an account record are only those who need it to deal with your query. Cookies do a smaller job than most people assume: they keep you signed in between pages and remember the choices you set on the site. Clear them and you simply sign in again. Records stay only while the purpose they were collected for, or the law that applies to you, requires it. Where a longer hold is needed, we explain that in the reply to your request.
We hold the account email and contact number, the wallet references for transfers you make, and the browser and device details that help us spot a sign-in which does not fit your usual pattern. Each has a job: reaching you, tracing a transfer, protecting the account.
Cookies keep you signed in between pages and remember the choices you set on the site. We do not use them to follow you around other websites. You can clear or block them in your browser settings on a phone or a desktop, and the site will still open; you will simply sign in again.
Access to account records inside our operation is limited to the people who need it to answer your query. We will not read your password back to you. If you think someone else has your details, change the password from the account area and tell us, so we can look at the account with you.
Records stay with us only while the purpose they were collected for, or the law that applies to you, requires it. Some wallet references have to be held longer than the account itself. Where that is the case, we explain it in the reply to your request.
Short answers to the points readers raise most often about this policy. If yours is not here, send it through a contact route published on this site and we will answer it directly.
Your account email and contact number, the password you set, the preferences saved in your account area, and the wallet references for transfers you make through bKash, Nagad or Rocket. We also note basic browser and device details so an unusual sign-in can be checked. All of it is tied to your account.
Yes. Send the request through a contact route published on this site and say whether you want the account closed, a copy of what we hold, or a correction. Some records, such as wallet references, may have to be kept for longer under the law that applies to you, and we will tell you which.
No. Studios such as CQ9, JDB, Bigtime Gaming, Joker and Spadegaming supply the slot and table titles that load in our lobby; they do not receive your account email, your wallet records or your password. Your details stay with us for the purposes this page sets out.
From your browser. On a phone or a desktop, the settings menu lets you clear cookies, block them, or allow them only for the site you are on. Blocking them will sign you out more often, because cookies are what keep you logged in between pages. The lobby itself still opens.
Use a contact route published on this site. If your question concerns the account itself, sign in and raise it from your account area; if it concerns the wording here, a written request is easier to answer because you can name the section. Keep the reply with your records.
It can change when the way we handle data changes, or when the rules that apply in your region move. When that happens we update this page, so the version shown here is the one to check before you rely on a particular line.