Live / Slots
9a33 handles your information with a clear purpose — we collect only what is needed to run your account, process wallet transactions through bKash, Nagad or Rocket, and keep your session secure. Access to this platform depends on your local law and eligible regions; this policy explains exactly what data is involved at each step.
When you open an account with us, we collect the details you enter during registration — your name, contact information and login credentials. When a transaction moves through a local payment channel such as bKash, Nagad or Rocket, we record the reference data attached to that transfer: the amount, the channel identifier and the timestamp. We do not store your full mobile wallet PIN or password; that stays between you and your payment provider. We use your information to verify your account, process deposits and withdrawals, and respond to support requests you raise. We also collect technical data — device type, browser version and session identifiers — to keep your account accessible across logins. This data is held on secured infrastructure and is not sold or rented to third parties for marketing. Retention periods follow our internal data schedule; we hold transaction records for as long as is operationally necessary and legally required under applicable frameworks. Where local law in Bangladesh governs data handling, we follow the obligations that apply to eligible regions. If you have questions about what data we hold for your account specifically, the support routes at the bottom of this page are the right place to start.
This policy covers data that moves through your 9a33 account directly. It does not extend to third-party services that open in a separate window or operate under their own terms. Understanding the boundary helps you know where to direct a question about your data.
Your login, session history and registered contact details fall fully inside this policy. We control how this data is stored and who can access it internally.
Records of deposits and withdrawals made through bKash, Nagad or Rocket are covered here. The payment provider's own privacy terms also apply to the data on their side of the transfer.
Pages you view, game lobbies you open and search terms you use within the platform are covered. This data shapes your session and helps us fix navigation issues.
External links, game studio interfaces and any service that operates outside our domain are not covered by this policy. Those services have their own data terms that apply independently.
You have practical choices over your data. Start by opening your account settings page — the profile section shows the contact details and preferences we hold for you. If anything is wrong or out of date, you can edit registered fields directly from that screen. For data that cannot be changed through the account interface — such as historical transaction records tied to a bKash or Nagad payment reference — you can raise a correction or access request through our support channel. We will confirm receipt and follow up with the relevant records. If you want to understand what data is attached to a specific account action, including a Rocket deposit log or a login event, name the date and transaction reference when you contact us so the team can locate the record quickly. Deletion requests are handled in line with our retention obligations; we will tell you what can be removed and what must be kept under applicable requirements.
Open account settings to see the contact details, session data and preferences currently stored against your profile.
Edit out-of-date information directly in the profile screen. For locked fields, submit a correction request through support.
If you want to know what a specific transaction record contains, contact support with the date and payment reference for a faster response.
We process deletion requests against our retention schedule and confirm which data can be removed and which must be kept under applicable rules.
If your question is about data held on your account, a transaction record from a bKash or Nagad payment, or a correction you need made, use one of the routes below. We respond through the same channel you use to contact us. Availability and response timing depend on the channel; no specific operating hours are stated here that we cannot stand behind.
Open the chat widget from any page inside your signed-in account. Describe the data question and include a transaction reference where relevant.
Send your privacy or data request to the support email address shown in the contact section of your account area. Include your registered account identifier.
The Help Centre inside your account lists common data and privacy questions with step-by-step paths for account corrections and record requests.
We apply access controls and encryption to the data stored under your account. Cookies and session tokens are used to keep you logged in and to remember your preferences between visits. You can manage cookie preferences through your browser settings; blocking session cookies may affect how the account page loads. Transaction records linked to bKash, Nagad or Rocket deposits are retained for the period required by our operational and applicable legal obligations — we do not hold them longer than necessary. When this policy changes, we update the version date shown at the bottom of the policy page. Continued use of the account after an update means you have seen the revised terms. If a change affects how we handle your personal data in a material way, we will notify you through your registered contact details before the change takes effect.
Login credentials are stored in hashed form. Access to your account data internally is restricted to authorised roles only, and we review those permissions on a set schedule.
Session cookies keep your login active and store your lobby preferences. You can clear or block them from browser settings, though some account functions rely on them.
We keep account and transaction records for as long as required by our internal schedule and any applicable obligations. Records older than the retention window are deleted or anonymised.
Material changes to how we use your data are communicated to your registered contact before they take effect. The version date on this page reflects the most recent revision.
The questions below cover what we hear most from people reading this policy for the first time. If your question is not here, the support routes in the section above are the right next step.
We collect the name, contact details and login credentials you enter during registration. We also record the device type and browser session attached to each login. We do not collect more than is needed to run and secure your account.
No. We record the transaction reference, channel name, amount and timestamp for each wallet payment. Your PIN is entered on the payment provider's own interface and never reaches our servers. That part of the transaction is governed by the provider's own terms.
Yes. Open your account settings page to view the contact details and preferences we hold. For transaction records or login history, contact support with your account identifier and the date range you want reviewed — the team will pull the relevant records.
Edit contact details and preferences directly from the profile screen in your account. For fields that cannot be changed through the interface — such as a transaction record linked to a Rocket payment — submit a correction request through live chat or email support.
We do not sell or rent your personal data to third parties for marketing. We may share data with service providers who operate parts of the platform under data processing agreements that restrict how they use it. Game studios and external link destinations operate under their own privacy terms.
We process a deletion request against our retention schedule. Data that falls outside a mandatory retention window is deleted or anonymised. We will confirm in writing which records have been removed and which must be kept under applicable requirements, and why.