Casino / Slots
This is where 1111bey sets out what account data we keep, why the wallet record matters, and how you ask us to change something. Read it before you open an account, and come back when a detail changes.
Your wallet sits at the centre of what we hold, so most of this page is about keeping that record accurate and readable to you. When you pay in through bKash, Nagad, Rocket or a bank transfer, we keep the reference, the amount and the status our system records — not your wallet PIN, and not your full card number. Those entries exist so you and we can both trace a transaction when something looks wrong. Some of what we collect is simply what a browser sends: device type, session timing, and the pages you opened inside the lobby. We use that to keep the account area loading properly on a phone and to notice sign-in attempts that do not match how you normally use the account. Where you are matters. Rules on data, on what can be collected and on how long it may be held differ between countries, so the handling described here applies where local law permits and where you are in an eligible region. If a rule in your country asks for something different from this page, that rule wins. We do not sell your details, and we do not pass them to studios or game suppliers so they can market to you. Sharing happens where it is needed to run your account, or where a lawful request requires it.
One paragraph of a policy is only useful if you know when it stops applying. Here is our line. Anything you do after signing in with your 1111bey email and password falls inside this page: the wallet you fund, the payment references we store, the session that starts when the lobby loads on your phone. So does the small stuff, the browser details that let a live table open full width on a mobile screen. What sits outside is easier to miss. When you send money through bKash or Nagad, you are dealing with that company's app and that company's rules; we only see what their confirmation passes back. Studio titles loaded into the lobby come from suppliers with their own notices. And a link that takes you off our domain is someone else's page from the moment you click it. If a page on this site links out, check what that page says about data before you enter anything.
Everything behind your sign-in belongs here: the email you registered, your wallet balance, the payment references we hold, and the device records attached to your sessions. If you can see it after logging in, this page covers how we keep it and who inside our operation can open it.
Deposits made through bKash, Nagad, Rocket or a bank transfer create a record on your account, and that record sits inside this policy. What sits outside it is the wallet provider's own handling of your money. bKash and Nagad keep their own terms, and their app shows you what they hold.
Opening the lobby, a live table or a slot room leaves a session trail: which page loaded, when, and on what device. We read that trail to keep the lobby working on mobile browsers and to notice patterns that look unlike your normal sign-in. We do not use it to build a marketing profile.
Some parts of the page are served by other companies, the studio titles loading inside the lobby for example. Their own privacy terms cover what they collect, and we cannot answer for those. We can tell you which parts of the page are ours and point you to the supplier's notice where one is shown.
Nothing on this page should feel like a locked door. What you can do yourself, do yourself: the profile fields sit in your account area, and editing them there is faster than asking. Your email and phone feed into how we reach you about a payment, so keep them current. For everything else, ask. We keep the request simple: tell us which record you mean, which wallet you used if money is involved, and roughly when it happened. That gives us something to search. Vague messages about your data cost a day of back-and-forth that neither side enjoys. If a correction cannot be made because a record backs a completed transaction, we will say so plainly and explain what can change. If your local law adds a right this page does not mention, tell us which one you are relying on and we will work through it with you rather than around it.
Sign in, open the account menu and read the details attached to your profile: the email on file, the payment references and the sessions we have logged. If something there looks wrong or out of date, that same screen is where you start correcting it. Nothing is hidden behind a request form.
Email address, phone number and the name on the account are the fields that go stale fastest. Update them from the account area then check the wallet section to confirm the change landed. If a field is locked after a payment method is attached, message us and we will explain what needs to happen.
If a paragraph on this page does not answer your case, write to us through the contact route published on the site and describe what you are looking at. Tell us the wallet you used and roughly when. We can look up the record and reply about your own account, not about anyone else's.
You can stop using the account at any time, and you can ask us what happens to the stored records if you do. Some payment and transaction history has to be kept for accounting and dispute reasons even after an account is closed, so expect a partial rather than total removal.
A privacy question gets answered faster when it lands in the right place than when it is sent everywhere at once. Signed in? Use the contact option inside your account area, because it carries your account reference and we can pull the exact record you are asking about. Not signed in yet? The contact route published on the site is open to you for questions about data handling and eligible regions. Say what you are looking at. A message naming a bKash deposit that did not show in your wallet is something we can act on; a message saying something is wrong is not. Include the amount and the reference from the wallet app where you have it. We do not publish a callback window or a response clock here, because we would rather not promise a time we cannot hold to. What we can say is that the message reaches a person who can open your account record.
Once you are signed in, the contact option inside your account area is the route that carries your account reference automatically, which saves a round of back-and-forth. Use it for anything tied to your wallet or a specific payment record, so the person reading it can pull the right entry.
If you have not opened an account yet, use the contact route published on the site. Ask about data handling, about which regions the lobby serves, or about the payment rails shown; we would rather answer first than have you guess. You do not need an account to ask.
For a deposit that has not appeared on your wallet, message us with the wallet name, the amount and the reference from the bKash, Nagad or bank app. We can trace what our side recorded and tell you what we see. Your wallet provider's own app remains the place to check the money left.
Data handling is boring work done properly. Three things matter to us: the account stays yours, the record stays readable, and the page does not collect more than the lobby needs to run. That is why the session data we keep is about loading and sign-in, not about building a picture of you for someone else. Cookies are part of that. They hold your signed-in state and a couple of display choices. Clear them and nothing breaks, but you will sign in again, and that is the trade. Payment records are the longest-lived thing we hold, because a transaction can be questioned months later. Profile fields are easier to clear than a completed deposit trail, and we will tell you which is which before you act. If a supplier's title loads inside the lobby, that supplier may set its own storage on your device. We point you at their notice rather than pretend it is ours.
The site drops small files that keep your sign-in alive between page loads and remember basic display settings on your phone. Without them the account area would ask you to sign in again on every tap. You can clear them from your browser settings, though the lobby will then treat you as a new session.
Your password and any code sent to your phone are yours alone; nobody from our side will ask for them in a message. If a sign-in arrives that you did not start, change the password from your account settings and tell us the same day, so the session record can be checked.
Payment records and account history are kept for as long as the account is open, and for a period afterwards where accounting or a dispute needs them. We do not promise a fixed deletion date on this page, because the length depends on the record type and on what local law asks of us.
If you want a copy of what your account holds, or you want a detail corrected, say so through the contact route and name the field. We will tell you what we can change directly, what has to stay for transaction records, and what your local law adds beyond this page.
Six things come up again and again when someone writes to us about their data, so they are answered below in the order they usually arrive. Short answers, plain words, no hedging where we can avoid it. Where the honest answer is that it depends on your local law and the region you are in, we say that rather than offer a promise we cannot hold. Reading these first saves a message. Reading them second, after you have opened your account area and seen the fields we hold, saves two. If your case is not covered here, the contact section above is the next step. Have the wallet reference ready before you write, bKash, Nagad, Rocket or bank transfer, whichever you used, because that reference is what lets us find your record instead of guessing. Send it with the question and the reply gets shorter.
It covers the account you open with us: the email you register, the wallet records created when you pay in through bKash, Nagad, Rocket or a bank transfer, and the device and session details attached to your sign-ins. It does not cover what a wallet provider or a game supplier does with your data.
No. A deposit is confirmed from the reference the wallet sends back, and the amount you see in your own app should match what lands in your account wallet. If anyone contacts you asking for a PIN, a one-time code or a password, treat it as someone outside our operation and do not reply.
You can read this policy and the other public pages without signing in, and you can look through the lobby layout. Opening an account needs an email and a password, because that pair is how the account area, the wallet and the payment records get tied to you. There is no separate anonymous route.
Ask through the contact route inside your signed-in account area and say you want a copy of your account details. We will confirm which fields we hold and how we will pass them to you. Expect the transaction record to be the largest part of what comes back.
It can. Data rules and access rules differ by country, so the handling on this page applies where your local law allows it and where you are in an eligible region. If you travel, sign in and check the notice shown in your account area, because availability is not the same everywhere.
The account stops working, but the transaction and payment records sit for a while after that, because accounting and dispute handling need them. Your profile fields can be cleared sooner than the payment trail. Write to us before you close if a specific record matters to you, and we will say what stays.