Slots / Mobile
33bmq collects only the account and transaction data needed to run your wallet, process payments through Nagad and Upay, and keep your session secure. This policy tells you exactly what we hold, why we hold it, and what you can do about it. Access and eligibility depend on your local law and the eligible regions we serve.
We collect information you submit directly — your registration details, the payment method you link (such as Nagad or Upay), and activity records tied to your account session. We also collect technical data your device sends automatically: browser type, operating system version, screen resolution and the IP address your mobile connection uses at login. We do not sell this data to third parties. We do not share it with advertisers. We share it only where an operational process requires it — for example, passing a transaction reference to Nagad or Upay to complete a wallet transfer, or responding to a verified legal request. Retention periods vary by data type: session logs are held for a shorter period than account-identity records, which we keep for as long as your account remains active and for a reasonable period after closure. You may request a summary of the personal data we hold on you at any time by using the contact route listed in the support section below. Availability of specific account features depends on your local law and the eligible regions we operate in.
Not every interaction on or around 33bmq falls under this policy. Use this section to understand the boundary clearly before raising a data question.
This policy fully covers the data generated when you log in, update your profile, or change your linked wallet. Every field you fill in on the account page is within scope, and you can request a copy of that record.
Payment records tied to your Nagad or Upay transfers are within scope. We hold the transaction reference, amount and timestamp. The payment provider holds its own record under its own privacy terms, which sit outside ours.
Pages you browse, game titles you open and the lobby sections you visit generate session data within scope. We use this only to maintain your session state and to detect unusual access patterns — not for advertising profiling.
External links, game studios supplying content to the lobby, and any app store you use to reach this platform each operate under their own privacy terms. We cannot control or respond on behalf of those parties.
You have four concrete actions available at any time. First, you can request a readable summary of the personal data we hold against your account — this covers registration details, linked wallet references and session history we retain. Second, if any record is inaccurate — a wrong name, a mobile number entered incorrectly during registration — you can ask us to correct it; we will confirm the correction in writing via the channel you used to raise it. Third, you can ask what category of data we hold and why, without requesting the full record. Fourth, if you want to close your account and request deletion of data we are not legally required to retain, you can submit that request through our support route and we will walk you through the process. Response time is not something we can guarantee in this document, but we aim to acknowledge every data request promptly and resolve straightforward corrections quickly. Where your local law grants additional rights, those apply alongside the steps above.
Request a summary of the personal data tied to your account at any point. We will send it through the same channel you used to ask.
If a name, mobile number or wallet reference on your account is wrong, raise it with support. We will confirm the correction once it is applied.
You can ask which categories of data we hold and the reason we hold each one, without needing to request the full account record.
To close your account and request deletion of non-essential data, contact support directly. We will explain what data must be kept under applicable rules and what can be removed.
If you have a question about your data, a correction to request, or a concern about how your information has been handled, use one of the routes below. We only list channels that are actually live on the platform — no invented addresses or hours.
Open the chat icon from any page on 33bmq while you are signed in. State that your query relates to your personal data and the agent will route it to the right team.
Navigate to the Help section inside your account dashboard. Submit a written request there with your registered mobile number so we can verify your identity before acting.
Send your data request by email using the address published in the Contact page of the site. Include your account username and the specific action you are requesting.
We take straightforward technical steps to protect the data we hold. Your account session uses an encrypted connection. Payment references passed to Nagad or Upay are transmitted over secured channels. We do not store full wallet credentials on our servers.
We use session cookies to keep you logged in and functional cookies to remember your lobby preferences. We do not use third-party advertising cookies. You can clear cookies through your mobile browser settings at any point without losing your account data.
Account identity records are held while your account is active. Session and activity logs have a shorter retention window. After account closure, we retain only what applicable rules require us to keep, and we remove the rest on a documented schedule.
Your password is stored in a hashed form — we cannot read it, and neither can support staff. If you suspect unauthorised access, change your password immediately from the account settings page and contact support through live chat.
When this policy is updated, the revised version replaces the previous one on this page. We will note the change in your account notification area. Continued use of the platform after a posted update means you have seen the revised terms.
These are the questions we receive most often about how your data is handled. If yours is not here, use the support routes listed above.
We collect the name, mobile number and credentials you enter at registration, plus the wallet identifier you link — such as a Nagad or Upay number. We also collect the device and browser data your connection sends automatically at login.
We pass only the transaction reference and amount needed to process your wallet transfer. We do not send your full account profile to Nagad or Upay. Each payment provider holds its own record under its own privacy terms.
Send a request through live chat or the Help Centre inside your account dashboard. Include your registered mobile number so we can verify your identity. We will prepare and deliver a summary through the same channel.
Yes. Submit a deletion request via support. We will confirm which data can be removed immediately and which records we are required to retain under applicable rules. We will carry out the deletion and confirm it to you in writing.
Retention periods depend on the data type and applicable rules. Identity records may be kept for a period after closure as required. Session and activity logs are removed on a shorter schedule. We can tell you the specific period that applies when you request it.
This policy governs data we collect from your account wherever you connect from. However, access to the platform itself depends on your local law and the eligible regions we serve. Availability is not the same as data coverage under this policy.