Live / Mobile
This page is the 333bey Privacy Policy: what we store when you sign in from your phone, how wallet details from routes such as Nagad and Upay are handled, and what you can ask us to change. Access depends on your local law and eligible regions.
When you open an account with 333bey, we hold a small, defined set of records: the email you sign in with, the mobile number linked to your wallet, the local payment routes you use such as Nagad or Upay, and the session data your browser leaves behind. That is the material this policy speaks to. We do not ask for anything the account flow does not clearly request, and the fields you see at sign-in are the fields we store. What we do with those records is narrow. We keep them so your sign-in works, so a wallet transfer can be matched to your account, and so our team can answer you when something looks wrong. We do not sell account data, and we do not hand it to third parties for their own marketing. Where a service provider supports the site, whether that is hosting, message delivery or wallet reconciliation, they work on our instruction and only for that purpose. Eligibility and access rules are not the same everywhere. Whether you can register, hold an account or use a particular payment route depends on your local law and eligible regions. If those rules change for your region, the wording that applies to you may change with them, and we say so on this page rather than in a side channel. Requests about your records go through the support route published on this site.
This policy follows you through the parts of 333bey that touch your own account. Signing in, updating your email, checking a wallet transfer record and reading what we store are all inside its scope. Content you can open without signing in, such as the lobby preview, game titles like Jamuna King Slots or Live Cricket Spot, and the general pages, is covered only as far as it relates to data we collect. Some records sit outside this policy. If you follow a link to a payment app on your phone, the privacy terms of that provider apply to what happens inside it, not ours. If you message us from an email client or a phone dialler, that app handles the message before we do. We cannot control what a third-party site does with data you give it directly. Where local rules require different handling for your region, that requirement applies alongside this page. Access depends on your local law and eligible regions, so treat the scope here as the general position and your account area as the final word.
Signing in, resetting a password, updating the mobile number tied to your wallet and reading the details we hold all sit inside this policy. Everything you do while signed in to 333bey is tied to the records described on this page, including the email you registered with.
When you move money through a local route such as Nagad, Upay or bKash, we keep the reference that lets our team match the transfer to your account. The provider keeps its own separate record, and their privacy terms govern what happens inside their app.
Pages you can open without signing in, and the small files your browser stores so the site remembers your session, fall under this policy too. Lobby titles such as Blackjack Club or Jamuna King Slots are shown to everyone, but the account data behind them is not.
Links out to a payment app, a mail client or another site take you outside this policy. What those services do with your data is their call, not ours, so read their terms before you share anything beyond what the payment flow itself asks of you.
Your account is yours to read. Open the account area and you can see the email, mobile number and wallet route attached to your sign-in, along with the payment records tied to it. If a field is out of date, a new number or a different wallet, change it there and the update flows through to how we reach you. When something looks wrong, ask. Write to the published support route and tell us which record you mean. We can confirm what we hold and, where the request is reasonable and the account is yours, correct or remove it. We may ask a question or two to be sure the account belongs to you before anything is changed. You can also ask what we keep, why we keep it, and how long it stays. We answer in plain language rather than sending you a wall of clauses. If a request cannot be actioned under your local rules, we say that directly and name the rule that applies instead of leaving the thread open.
Open the account area and you can read the email, mobile number and wallet route attached to your sign-in, along with the payment records our team has matched to you. Nothing there is hidden behind a request form or a waiting period.
If a number or wallet has changed, update it in the account area so our records match what you use. Where a field cannot be edited directly, write to the published support route and say which part of the record needs changing.
You can ask how long we keep a record, what it was kept for, and when it is due to be cleared. We answer in plain language, and where a rule in your region forces a longer or shorter period, we say which one applies.
Questions about this policy go through the same support route as any account issue. Tell us which part of the policy you are asking about and which account is yours, and keep the thread open so we can confirm the details with you.
Questions about this policy do not need a special address. Use the same routes you would use for any account matter, and start from whichever one you already have open. If you are signed in, support inside your account area is the shortest path, because the account is already identified when your message arrives. If you are writing from outside the account, use the support email published on this site and name the account email you registered with, so the reply lands in the right place. For data requests, say plainly what you want: a copy of a record, a correction, or removal where the rules in your region allow it. Policy pages linked from the footer carry the wording that applies to your account, so it helps to read them before you write and point at the part you want explained. We do not operate unnamed channels, and we do not ask you to send account passwords or payment codes through any message.
Once you are signed in, the support route shown inside your account area is the quickest way to ask about a stored record. Your account is already identified when the message arrives, so you do not have to explain your sign-in details again.
The support email published on this site is the route for policy questions, data requests and anything you would rather put in writing. Include the email you registered with and the part of the policy you are asking about.
This policy page and the account terms linked from the footer carry the wording that applies to your account. Read them together first, so your message can point at the clause you want us to explain back to you.
Handling data well is mostly about keeping it small and keeping it legible. We collect what the account flow asks for and nothing beyond it, we let you see it in the account area, and we answer when you ask about it. Cookies are limited to what keeps a session alive: a small file in your browser so you stay signed in while you move between the lobby and your account. Clear it, and you sign out. We do not use it to trail you across other sites. Security is a shared job. Use a screen lock on the phone you sign in from, keep your details to yourself, and sign out on anything you no longer carry. If you think someone else has your sign-in, write to support and we walk through the steps with you. Retention follows the rule that applies in your region, and you can ask at any point what is held, why, and for how long.
We collect what the account flow asks for: an email, a mobile number used to match your wallet, the local payment route you picked, and basic session data from your device. Anything beyond that only arrives if you send it yourself.
Your browser keeps a small session file so you stay signed in while you move between the lobby and your account. Clearing it signs you out. We do not use it to follow you around other sites, and the account area shows which session is active.
Keep your sign-in details to yourself, use a screen lock on the phone you sign in from, and sign out on a device you no longer carry. If you think someone else has your details, write to support and we go through the steps with you.
Records tied to a wallet transfer are kept while the account is open and for the period your local rules require afterwards. You can ask what is held, ask for a correction, or ask for removal where the law in your region allows it.
Most questions about this policy come down to four things: what we hold, why we hold it, who can see it, and how to change it. The answers below take those in the order they usually come up, from the records attached to your sign-in through to the request route. If your question is about one transfer, have the wallet name, such as Nagad or Upay, and the date to hand, because it makes the reply faster and stops us going back and forth. If it is about access in your region, the answer depends on your local law and eligible regions, and we say so plainly rather than promising something we cannot control. Anything not covered here can go to the support route published on this site, and a person will read it.
An email you sign in with, a mobile number used to match your wallet, the local payment route you picked, and session data from the device you use. We do not collect anything the account flow itself does not ask you for.
Yes. Once signed in, the account area shows the transfers our team has matched to you, including the reference kept for a Nagad, Upay, bKash or Rocket payment. The payment provider keeps its own separate record of the same transfer.
Update what you can in the account area, and write to the published support route for anything that is locked. Tell us which field is wrong, and keep the thread open while we confirm the account is yours before anything changes.
We share only what a transfer needs so the payment can be matched to your account. Providers such as Nagad or Upay then handle that data under their own terms. We do not sell account records or pass them on for someone else to market to you.
It can. Access to the account and to particular payment routes depends on your local law and eligible regions, and where a rule requires different handling, that requirement applies alongside this page. The current wording always sits here.
Records tied to a wallet transfer stay while the account is open and for the period your local rules require afterwards. You can ask what is held and when it is due to be cleared, and we answer in plain language.