Sports / Slots
2999brt holds your account, wallet and device details in one place so you can see what we store and ask us to change it. This page sets out that policy in plain terms, and what you can access still depends on your local law and eligible regions.
This policy is written by 2999brt for people who open an account with us, and it applies from the moment you start the sign-up form. We treat your account details, wallet records and device data as one connected set, because that is how our lobby actually works: a bKash or Nagad deposit lands in your account wallet, a Rocket or Upay transfer shows the same way, and each entry is tied to the mobile number or email you used at sign-up. What we can do with that data depends on where you are. Rules in Bangladesh and in other regions differ, and eligibility is set by your local law rather than by anything we publish here. Where local law gives you a specific right, we follow it; where it does not, we still apply the same internal limits on who inside the company can open a wallet record. We do not sell your account data. We share it only where a payment rail, a game studio integration or a legal request makes it necessary to complete something you started, and we keep the shared set as small as the task allows. Your password stays with you — we never ask for it through a message, a call or a chat window. If any part of this page reads differently from the law that applies to you, that law wins. The rest of the page explains the choices you have and how to reach us about them.
Scope matters more than most people expect, so here is the line we draw. The policy follows your account from the sign-up form through every session you open, including the lobby pages you browse, the game tables you load and the wallet entries you create. It covers what we collect ourselves and what our own systems record. It does not cover a studio's own game client once you leave our pages, and it does not cover a payment app you open separately. Picture it this way: if a screen sits inside our brand and you reached it by signing in, this policy applies; if you tapped out to another company's app or site, their terms take over. Third-party links we publish are there for convenience, and we cannot set the rules on pages we do not run. Your local law still governs what you are allowed to access in the first place.
Signing in, resetting your password, keeping your session open on a phone or a shared browser — all of that sits inside this policy. We record the device and the sign-in time so a new entry can be checked against your usual pattern. Nothing here changes your right to ask what we hold.
Every deposit you make through bKash, Nagad, Rocket, Upay or Bank Transfer leaves a record tied to your account, and that record is covered here. We keep the amount, the rail and the reference so you and our support team can trace a payment that looks wrong. Your wallet history is yours to open.
Cookie settings decide what loads when you open our lobby — page language, session state, and the count of visits that helps us see which pages stall. We set the ones needed to keep you signed in; the rest you can switch off in your browser without losing account access.
Game studios and payment apps run on their own systems. When you launch a title, the studio may read a session token so it recognises you. When you open bKash or Nagad in a separate app, that app applies its own privacy terms. We choose which details we pass along; the rest is outside our control.
You are not stuck waiting on us to notice something. Most of what this policy promises turns into an action you can start from your signed-in account. Open your profile to check the mobile number, email and name we hold; if a spelling is wrong or a number changed, correct it there and confirm the change took. For a bKash, Nagad, Rocket, Upay or Bank Transfer record you do not recognise, open the wallet section and keep the reference before you contact support — that reference is what lets us trace the entry. If you want to know what else we hold, ask us and we will tell you what we can under the law that applies to you. And if you would rather we paused the use of your data for a particular purpose, say so; we will explain whether the policy allows it and what changes on your side.
Your profile screen shows the name, mobile number and email attached to your account, and your wallet screen shows every deposit and withdrawal reference. Start there before you ask us anything — most questions about stored data are answered by those two screens. If something is missing, that is when a support message helps.
A wrong digit in your mobile number can block a wallet confirmation later, so fix it as soon as you see it. Open your profile, change the field, save, then sign in once to make sure the new value stuck. For a name change we may need to check the request before it goes through.
If a paragraph here does not match what you see in your account, tell us which part. Quote the section name and what you expected instead. We answer questions about stored data, cookie behaviour and wallet records, and we will tell you plainly if a request sits outside what the policy lets us do.
You can ask us to delete data we no longer need for the account, or to pause its use for a purpose you did not expect. Some records — a completed wallet entry, for example — have to stay because a payment rail or local law requires a trail. We will say which is which.
Questions about this policy travel through the same support routes you already use for your account. Start inside your signed-in area: the account help entry sits alongside your wallet and profile screens, and a message sent from there arrives with your account attached, which saves a round of questions. Off the site, the contact route published on this site is the one to use — write from the email address on your account so we can match the request. Tell us what you want to change or check, and paste the wallet reference if a payment is involved. If you are not signed in, you can still write to us; just include the mobile number you registered with. Keep the message specific — a section name, a wallet reference or the device you were using helps us find the right record. One rule holds whatever route you pick: we never ask you to type your password into a message.
Signed in, the account help entry sits with your wallet and profile screens. A message sent from there carries your account and recent wallet activity, so we can answer without asking you to repeat the basics. Use it for anything touching stored data, a cookie question or a record you want changed.
Not signed in, or writing from a different device? Use the contact link published on this site and write from the email address attached to your account. Include the mobile number you registered with and, for a payment question, the wallet reference. That set is usually enough for us to find the right record.
If a clause is unclear, quote it and we will explain how it applies to your account rather than repeat the wording back at you. Please do not send passwords, card numbers or wallet screenshots that show a balance — we do not need them to answer a privacy question.
Data handling on a casino lobby is less mysterious than it sounds. We keep what your account needs to work: the details you type at sign-up, the wallet entries your deposits create, the games you open, and the device and browser strings that show up each time you sign in. We limit who inside the company can open those records. Cookies do the narrow work of keeping a session alive and remembering your language choice; you can clear them in your browser, though a cleared cookie usually means signing in again. Retention follows need — a completed wallet entry stays while a payment rail or local law requires a trail, and routine device data is kept for shorter stretches than your account record. Security sits with you as much as with us: keep your password to yourself, sign out on a shared phone, and check your profile if you notice a session you do not remember. Where a request can be met, we will tell you what changes and confirm it once it is done.
Sign-up details, wallet entries, game sessions and device strings make up the bulk of it. We do not ask for anything the account does not need, and we do not build a profile of you outside this lobby. If a field is optional, leaving it blank will not block your account.
One cookie keeps you signed in; another remembers the language you picked. Clearing cookies signs you out and may reset a preference, which is why the lobby can look different after a browser clean-up. Blocking everything still lets the pages load, but you will sign in more often.
Your password is the one key we never hold in readable form. Sign out after a session on a shared phone, and treat any message asking for your password as not from us. If you spot a sign-in you do not recognise, change the password first, then tell support so the session can be checked.
Records stay as long as the account is open and, for completed wallet entries, as long as a payment rail or local law needs a trail. Ask us to correct or remove what no longer has a purpose and we will set out what can change, what must stay, and what happens next.
Most of what reaches our support desk about this policy comes down to four worries: what we store, who sees it, how long it stays and how to get it changed. We would rather answer each one directly than hand you a paragraph to decode. The answers below take them in turn, using the same wording we would use in a reply to you. Each one points at the screen or route you can use, so you can act on it straight away rather than come back to us. If your situation is not covered, message us with the section name from this page and we will pick it up from there. Nothing in these answers overrides the law where you live — where a rule gives you a stronger right than this page does, that rule applies and we will follow it.
Your sign-up details, wallet entries from bKash, Nagad, Rocket, Upay or Bank Transfer, the games you open and the device and browser strings recorded at each sign-in. We keep it so the account, the wallet and any payment question can be traced later.
Yes. Your profile screen shows the name, mobile number and email on the account, and the wallet screen lists every deposit and withdrawal reference. That covers most of what people ask us about. Anything beyond those screens, message support and we will tell you what we can.
Open your profile, change the field and save, then sign in again to confirm the new value took. A mobile number matters most, because a wallet confirmation goes to it. If a name change is refused, message support and we will explain what the check needs from you.
We pass what a studio needs to launch the title you picked and what a payment app needs to move money from your wallet. Beyond that, they run their own systems and set their own terms. Legal requests are handled one at a time, and we keep the shared set as small as possible.
An open account keeps its record. Completed wallet entries stay while a payment rail or local law requires a trail, and routine device data is held for shorter stretches. Ask us about a specific record and we will say which rule applies to it and what can be removed.
Use the account help entry when you are signed in, so your account travels with the message. Signed out, use the contact link published on this site and write from your registered email. Quote the section of this page that prompted the question.