App / Casino
q2222 collects only the account and transaction data needed to keep your wallet, payment records, and session history working correctly. 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 eligible regions.
When you open an account with us, we collect the details you provide during registration — your name, contact information, and any identity verification documents required to confirm your account. We also record transaction activity linked to your payment methods, including bKash transfers, Rocket payments, and Bank Transfer deposits and withdrawals. These records exist so we can match your wallet activity to the correct account, resolve any payment question you raise, and maintain an accurate history your account page reflects. Beyond registration and payment data, we collect device and session information when you access the lobby from your phone or browser. This includes your IP address, device type, and the pages or game categories you navigate to. We use this data to keep your session continuous across mobile and desktop, so returning to a known game or lobby position works without having to start fresh. We do not sell your personal data to third parties. Sharing only happens where it is necessary to process a transaction you initiated, comply with a legal obligation that applies in your region, or respond to a verified support request you raised. Your use of this platform and the application of this policy depend on applicable local law and the eligible regions we are able to serve.
This policy covers all data processed through q2222 directly — from account registration through to transaction records and in-session activity. It does not extend to third-party services that operate outside our platform, even where a link or integration exists. Understanding the boundary helps you know where to direct any data question.
Login credentials, session tokens and device identifiers collected when you access your account on mobile or browser fall within this policy. We hold this data to maintain account continuity and to protect your session from unauthorised access.
Payment activity processed through bKash, Rocket or Bank Transfer is logged and retained as part of your account history. These records are visible in your account wallet area and are covered fully by the terms of this policy.
Pages you visit, game categories you open, and lobby navigation paths are recorded at session level. This data helps us keep your returning-user experience consistent and is handled under this policy, not shared for advertising purposes.
Game studios such as CQ9, Spadegaming and Joker operate their own data environments for game delivery. Any data passing through those environments is governed by each studio's own policy. Our policy covers your account layer, not the studio's internal systems.
You have real, actionable options under this policy — not just abstract rights. The account area shows your transaction history, including each bKash deposit, Rocket payment, and Bank Transfer record logged against your wallet. If a detail looks wrong, you can raise a correction request directly through the support route shown in your account settings. You do not need to send a formal letter. Use the support contact form or the published account help route, describe the record in question, and our team will check the data held and respond. If you want to know what information we hold about you specifically, submit a data access request through the same support channel. We will confirm what is on file. If you decide you want your account closed and your stored data removed — subject to any legal retention obligations that apply in your region — that request follows the account closure path in settings. Every step is within the account interface; you do not need to contact an outside regulator to exercise these options with us directly.
Open your account wallet to see the full transaction log. Every bKash, Rocket and Bank Transfer entry is listed with date and amount. If a record is missing or incorrect, note the transaction reference before contacting support.
Contact support through the published account help route to request a correction to your registered name, contact details or identity documents. We will verify the request against the data already on file before making any change.
Submit a data access request via the support contact form to receive a summary of the personal information we hold for your account. We respond through the same channel; eligibility may depend on your region and applicable local law.
Account closure requests, including data removal subject to legal retention rules, are handled through the account settings closure path. Reach support if the self-service path is unavailable; the request is processed in line with applicable local obligations.
If you have a question about this policy, want to exercise one of your data rights, or need to flag a concern about how your information is handled, use the contact routes published in your account area. We do not accept privacy requests through social media; please use the routes below.
Submit your privacy question or data request through the support form inside your account. This is the primary route for data access, correction and removal requests. Describe the specific record or concern so we can locate the right data quickly.
The live chat route in your account connects you to the support team for real-time privacy questions. Use it to clarify what data we hold or to start a correction request before submitting a formal form. Availability is shown at the chat entry point.
For written privacy correspondence, use the email address listed in the published contact section of the site. Include your registered account identifier and describe the specific data or record your question relates to. Do not send payment credentials by email.
The steps below describe our operational approach to the data covered by this policy. These are the practices in place for every account, whether you access from a mobile browser or a desktop session.
We use session cookies to keep you signed in across pages and to remember your lobby position when you return on the same device. You can manage cookie preferences through your browser settings. Disabling certain cookies may affect account continuity and session persistence on mobile.
Account access is protected by the login credentials you set. We do not store your bKash PIN, Rocket PIN or Bank Transfer credentials — those are processed through the respective payment channel, not retained in your account profile here.
Transaction records and account registration data are retained for the period required by applicable legal obligations in your region. After the retention period ends, data that is no longer required for a legal or operational purpose is removed from active storage.
If we update this policy in a way that affects your rights or the data we collect, we will post a notice in your account area before the change takes effect. Continuing to use the platform after a notified change means you have seen the updated terms.
These are the questions we see most often about how q2222 handles your data. If your question is not here, use the support form in your account to ask directly.
We share data only where it is necessary to process a payment you initiated, meet a legal obligation in your region, or respond to a support request you raised. We do not sell your personal data. Game studios like CQ9 or Spadegaming receive only the session data needed to load a game, not your account or payment profile.
Yes. Every deposit and withdrawal processed through bKash, Rocket or Bank Transfer is logged in your account wallet as a transaction record. We store these records for the period required by applicable local law. You can view the full list in your account at any time; the record shows date, amount and status.
Submit a data access request through the support form inside your account. Include your registered contact detail so we can locate your file. We will confirm what data we hold for your account. Eligibility for the full response may depend on applicable local law and your region.
Yes. For corrections, contact support through the account help route and describe which detail needs updating. For deletion, use the account closure path in settings. Certain data may be retained for the period required by legal obligations in your region before removal from active storage.
We use session cookies to keep your account active across pages and to restore your lobby position when you return. You can adjust cookie preferences in your browser settings. Turning off functional cookies may interrupt session continuity, especially on mobile, so your lobby position may not be remembered between visits.
We post a notice in your account area before any change that affects your rights or the data we collect. The updated policy takes effect on the date stated in that notice. If you have a question about a specific change, use the support contact form to ask before the change date.