Sports / Slots
33f333 keeps your account details, wallet records and cookie choices under one published privacy policy, so you can see what we hold before you move money through bKash, Nagad or a Bank Transfer. What we can offer you, and how we treat your data, depends on your local law and your eligible region — this page sets that out plainly instead of promising a fixed outcome everywhere.
Here is the plain version of our privacy posture. When you open an account with 33f333, we collect what we need to run that account: your registration details, your sign-in activity, the payment records created when you move money through bKash, Nagad or a Bank Transfer, and basic device data from the browser you use. We keep that data to operate the lobby, to show you your own transaction history, and to answer you when you raise a question. We do not sell your personal details. Two things you should know. First, what we can offer you depends on local law and your eligible region, and some features may not be available where you are. Second, our policy follows the rules that apply to the regions we serve, so the wording here describes how we treat your data rather than promising the same outcome in every country. Cookies do some of the work. They keep you signed in between pages, remember simple display choices, and help us see which parts of the site load slowly on mobile. You can clear or block them in your browser, though parts of the account area may stop working properly if you do. We hold account and payment records for as long as your account stays open and for the period afterwards that local rules require. When you want to know what we hold, ask us through a published support route and we will explain the data linked to your account.
One policy governs one brand. Everything you do while signed in to your account — your sign-in activity, the wallet records created by bKash, Nagad or Bank Transfer payments, and the pages you open in the lobby — sits inside this policy. So does the cookie data our pages set on your phone or laptop. It stops at our own doorstep. When you tap through to a studio's game frame, a payment wallet's own app or a third-party page we link to, that provider runs its own rules and we cannot answer for them. Read their terms before you share anything there. Availability is another edge worth knowing. Access depends on your local law and your eligible region, and some features may not be open where you are. If a route is not shown in your account, treat it as unavailable rather than blocked by this policy.
Registration details, sign-in activity and everything you change in your profile sit inside this policy. So do the devices and browsers you use to reach the site. If you want to know which details we hold against your name, ask us through a published support route and we will walk you through it.
Each bKash, Nagad or Bank Transfer step you complete creates a record attached to your account wallet. That record is covered here, from the reference you copy to the status you see afterwards. Your payment provider also keeps its own copy of the transfer, and its own privacy terms apply to that.
Slots, live tables and cricket markets shown in the lobby are part of the service this policy covers. Session data from those pages — how a live table loads, which Cricket Betting Inplay screens open on mobile data — helps us keep the site steady. It is not used to build a public profile of you.
Game frames served by studios, wallet apps on your phone and any page we link out to sit outside this policy. Those providers set their own cookies and answer their own data questions. Check their terms before you hand over details, and come back to us for anything tied to your 33f333 account.
You have practical choices here, and none of them need a legal letter. Open your account area and you can read your own transaction records, check which payment route you used and see the details stored on your profile. If something is wrong — a misspelled name, an old mobile number, a wallet reference that does not match — update it there or ask us to help. Want to know what we hold? Ask. Send the question through a published support route and tell us which account and which period you mean. We will explain the data linked to your account and, where local rules allow, give you a copy or correct it. Two limits are worth stating. We cannot delete records that local rules require us to keep, and we cannot act on a request we cannot verify as coming from the account holder. Everything else, ask and we will tell you honestly what we can do.
Your account area lists the payments you have made and the references that go with them. Read through the wallet history first, note the date and the payment name, and then ask us only about the entries that look wrong or missing. It keeps the conversation short.
Names, mobile numbers and wallet references sit on your profile where you can update them. If the field you need is locked, send the change through a published support route and explain what should read differently. We may ask a question or two to confirm the account is yours before we act.
Not every question is a formal request, and you do not need to frame it like one. Ask how a record was created, why a page set a cookie, or what happens to your data after you close the account. Write it in your own words through a support route and we will answer in the same thread.
Say plainly that you want the data linked to your account, and give the period you mean. Where local rules allow it, we will send what we hold. Where they do not, we will tell you which part we cannot pass on and why, rather than leaving you guessing.
Questions about your data should not be hard to send. The routes we publish are the ones we answer: the support channel shown inside your signed-in account area, the contact address listed on the site, and the help pages that explain account and wallet steps. Use the one that fits what you need. Sign-in trouble, a wallet reference that looks wrong, a deposit you cannot see in your records — start with the support route inside the account. It lets us match your message to the right account without you sending personal details by hand. Keep the message short: what you did, when, and which payment name was involved. For a privacy request, say so in the first line. Tell us whether you want to see the data linked to your account, correct it, or ask how long we keep it. We will reply through the same route you used. We do not promise a fixed response time, so keep that thread open rather than opening a second one.
The support entry point shown in your signed-in account area is the fastest way to reach the right desk, because your account is already attached to the message. Use it for sign-in trouble, wallet records that do not match and any request about the data we hold on you.
The contact address published on this site works when you cannot sign in, when you are writing on behalf of the account holder, or when you simply prefer email. Include the account, the payment name and the rough date involved. Do not send passwords or wallet PINs through any contact route.
The help pages that explain account and wallet steps answer most access questions before you write to us: where records are shown, how profile fields are edited, and which payment names the lobby supports. Read them first, then follow the same route to our support team if the page does not cover your case.
We keep our data habits simple enough to describe in a paragraph. Account details, wallet records and cookie data are held to run the lobby, show you your own history and keep the site working on the phone in your hand. Only the people who need that access see the full picture. Cookies do specific jobs rather than everything: keeping you signed in, remembering display choices, and showing which pages load slowly on mobile data. Clear them in your browser and some account screens will stop behaving properly — that is expected, not a fault. Account security is mostly in your hands. Your password and any verification step shown at sign-in are yours to keep private, and your wallet PIN stays inside your payment provider's own app. If you think someone else has reached your account, change your password and tell us through a support route straight away. Retention follows local rules. We hold account and payment records while your account is open and for the period afterwards that the rules require, then remove what we no longer need.
Registration details, sign-in activity, wallet records from your payments, and the device and browser data your session sends. We use it to run your account, show you your own history and keep the lobby stable. You can ask which records are linked to your account through a published support route.
Cookies keep you signed in between pages, remember display choices and tell us which screens load slowly on mobile data. They are set by our pages, not by every studio frame you open. You can clear or block them in your browser settings, though parts of the account area may then stop working.
Your password and any verification step shown at sign-in belong to you alone, and your wallet PIN stays in your payment provider's app, not with us. If sign-in activity looks unfamiliar, change your password first, then tell us through a support route so we can look at the record together.
We hold account and payment records while your account is open, and for the period afterwards that local rules require. After that we remove what we no longer need. Ask through a published support route if you want to know which records are still held and what they relate to.
These are the questions our support routes see most often about this policy. The short answers sit below, and each one points back to the route where you can act on it — your account area, the contact address on the site, or the support channel you used before. A word on what this page is not. It is not a promise that every feature is open to you: access depends on your local law and your eligible region, and some routes may not be shown on your account. When something is not visible, treat it as unavailable rather than blocked. If your question is about a payment you already made, have the reference ready before you write. It saves a round of messages and lets us match your request to the right wallet record the first time.
Your registration details, sign-in activity, the wallet records created by your payments, device and browser data, and the cookie settings your browser sends. Part of that is visible in your account area. For the full list linked to your account, ask us through a published support route and we will explain it.
We do not sell it. Some sharing is simply part of running the site: your payment provider sees the reference and amount of a transfer you make, and studio game frames load from their own servers. Anything beyond that happens only where local rules allow it, or where you ask us to.
Yes. Open your account area and the wallet history shows the payments you have made through bKash, Nagad or Bank Transfer, with the references that go with them. If an entry looks missing, send us the reference and the date so we can check which record you mean.
Write through a published support route, say you want the data linked to your account, and give the period you mean. We may need to confirm the request comes from the account holder before we act. Where local rules allow, we will send what we hold.
We stop using it to run your lobby access, and we keep the account and payment records for the period afterwards that local rules require. After that we remove what we no longer need. Tell us through a support route if you want to know which records still sit with us.
Change your password first, then contact us through the support route inside your account area so we can look at the sign-in activity together. Your wallet PIN stays with your payment provider, so speak to them as well if money moved through bKash, Nagad or Bank Transfer.