Mobile / Live
33qqq collects only the information needed to run your account, process your Nagad, Upay or Bank Transfer transactions and respond to your support requests — nothing more. Access to this platform and the rights described here depend on your local law and the eligible regions we serve.
This policy sets out how we collect, use, store and protect the personal information you share when you create or use your 33qqq account. The information we hold falls into three broad categories: identity details you submit during account registration, transaction records generated when you move funds through Nagad, Upay or Bank Transfer, and device or session data our systems log automatically when you browse the platform on mobile or desktop. We do not sell your personal data to third parties. We do not share it with advertising networks outside the scope described here. Where we engage a third-party service — for example a payment processor handling your Nagad or Bank Transfer instruction — that processor receives only the data necessary to complete the specific transaction and is bound by its own data-handling obligations. Retention periods vary by data type. Transaction records are kept for the period required by the financial and operational standards applicable to your eligible region. Account profile data is held while your account remains active and for a reasonable period after closure. You may request a summary of what we hold about you at any time through the support route shown in your account settings. This policy applies to the 33qqq platform; it does not extend to third-party sites you may reach via links placed on our pages.
This policy covers data processed directly by 33qqq. Four distinct areas define its boundaries — understanding each one helps you know when our obligations apply and when another party's policy governs your information.
Any data you submit to create, verify or recover your 33qqq account — including your email address, chosen username and any identity confirmation steps shown in the registration flow — falls squarely within this policy. We control how that data is stored and who can view it.
Payment instructions you send through Nagad, Upay or Bank Transfer generate records on both our platform and the respective payment processor. Our policy governs the copy we hold; the processor's own terms govern the copy on their side. We do not override or extend their data-handling rules.
When you navigate the lobby, open a game room or search by category, our servers log session identifiers, device type and page paths. This data is used to keep the session stable and to diagnose technical issues. It is not used to build an advertising profile or shared with ad networks.
Links to external sites — including game studio lobbies hosted outside our domain or third-party support tools — are not covered by this policy once you leave 33qqq. Each external service operates under its own privacy terms. We recommend checking those terms before submitting personal data elsewhere.
Your rights over personal data held by 33qqq are practical and directly actionable through your account. The exact scope of enforceable rights depends on local law and the eligible region under which your account was opened — we do not make blanket legal promises, but the steps below describe what you can do right now through the platform or by contacting support. Reviewing your account record is the first step. Open the account settings area; the profile section lists the name, email and contact details currently associated with your account. If any detail is incorrect — for example a misspelled name that could complicate a Bank Transfer verification — you can submit a correction request through the support channel. Correction requests are handled in the order received; we do not commit to a specific processing window, but the support team will confirm receipt and keep you updated. If you wish to ask what data we hold beyond the profile fields visible in your account, or if you have a question about how a specific Nagad or Upay transaction record was logged, contact the policy support route listed in the Support section of this page.
Open account settings and check the profile section. Your registered name, email and linked contact method are displayed there. If a discrepancy exists — particularly one that affects how your Bank Transfer or Nagad records are matched — raise it with support immediately.
Submit a correction request through the account support channel. Include the field you need changed and the correct value. The support team confirms receipt and processes updates in the order they arrive; you will receive a follow-up once the change is applied to your account record.
If you want to know what personal information we hold beyond what is visible in your account settings, you can send a data inquiry through our support route. Describe the specific records you want to know about — for example, a Upay transaction log or a session record from a particular date.
You may request account closure at any time via support. Closure triggers our standard retention review: transaction records required for financial or compliance purposes in your eligible region are retained for the applicable period; all other personal data is removed from active systems.
Three routes are available if you have a question about this privacy policy, want to submit a data inquiry or need to raise a concern about how your information has been handled. Use the route that suits the urgency of your question.
The live chat widget is accessible from any page on the 33qqq platform while you are signed in. Use this route for account-related privacy questions where you need a response in the same session — for example, confirming that a support agent has located your Nagad transaction record.
For formal data inquiries — such as a written request to review or correct your account record, or a question about how a specific Bank Transfer log was stored — email the support address listed in the Help section of your account. Include your registered email and a clear description of the request.
The Help section inside your signed-in account contains published answers to common privacy and data questions. Check there first for standard queries about data retention, Upay transaction records and account closure steps before opening a new support ticket.
Our approach to data handling is built around limiting what we collect, controlling who can access it and removing it when it is no longer needed. The four practices below describe how we put that into effect across account security, cookies, retention and policy updates.
Access to your account record is protected by the authentication method you set at registration. We do not store passwords in plain text. If our system detects an unusual sign-in pattern — for example, a login attempt from a device or location not previously associated with your account — additional verification steps may appear before access is granted.
We use session cookies to keep you signed in as you move through the lobby and to remember your preferred language and region settings. We do not use cookies to track your activity on third-party sites. You can clear cookies through your mobile or desktop browser settings at any time; doing so will sign you out of the current session.
Transaction records — including Nagad, Upay and Bank Transfer logs — are kept for the period required by the financial standards applicable to your eligible region. Account profile data is removed from active systems after account closure, subject to that retention floor. We do not keep data longer than operationally or legally necessary.
When this policy changes in a material way, we post a notice on the platform and update the effective date at the top of this page. Continued use of your account after a policy update indicates acceptance of the revised terms. If a change affects how we handle your Upay or Bank Transfer records, the notice will describe the specific area affected.
The questions below cover what our members ask most often about data, account records and their rights under this policy. If your question is not answered here, use the support routes described in the Contact section above.
We collect the details you enter in the registration form — typically your name, email address and a contact method for account verification. We also log the device type and approximate region at sign-up. We do not collect information beyond what the registration fields request, and your account settings always show what we currently hold.
Transaction records on our platform are accessible only to the account holder and authorised support staff handling a specific inquiry. When you initiate a Nagad or Upay transfer, the payment processor receives the minimum data needed to complete that instruction; they operate under their own data-handling terms and do not receive your full account profile.
Send a data inquiry to the support email listed in your account's Help section. Include your registered email address and describe the specific records you want to review — for example, Bank Transfer logs from a particular date range or your account profile as currently stored. The support team will confirm receipt and respond in the order requests arrive.
Yes. Open account settings to review your profile fields. If a name or contact detail is incorrect — especially if it could affect how Bank Transfer or Nagad records are matched against your account — submit a correction request through live chat or email support. Include the current incorrect value and the correct replacement.
No. We do not share personal data with advertising networks, data brokers or third-party marketing platforms. Session and browsing data logged while you use the platform is used solely for technical stability and is not used to build a profile for external advertising purposes.
Transaction records — including Nagad, Upay and Bank Transfer logs — are retained for the period required by the financial standards applicable to your eligible region. Account profile data is removed from active systems once that retention floor has passed. We do not hold data longer than necessary for operational or regional compliance purposes.