Mobile / Sports
qq880 is clear about what data we collect, why we collect it, and how it stays protected while your account is active. This policy applies to every interaction you have with us — from your first login through to wallet transactions using bKash, Nagad or Rocket — and your rights under it depend on your local law and eligible region.
When you open an account, we collect the details you provide during registration — your name, contact information and any verification records needed to keep the account secure. When you make a deposit or withdrawal using bKash, Nagad or Rocket, our system logs the transaction reference and wallet identifier associated with that movement. We do not store your full mobile wallet PIN or password; what we retain is the reference number and the status record that confirms the transaction completed. We also collect device and session data — browser type, screen size, session duration and the pages you visit — so we can keep the mobile experience consistent each time you return. This includes cookie data, which is explained further in the trust section below. All data we hold is used for account operation, security monitoring and, where you have given consent, to send you relevant account notices. We do not sell your personal data to third parties for advertising purposes. Retention periods apply per category, and you may request details of what we hold at any time through the support route shown on this page. Access to this policy and its protections depends on your local law and the eligible regions we serve.
When you transact via bKash, we log the wallet reference and completion status only. Your full bKash PIN is never captured or stored by qq880 at any point in the process.
Nagad deposits and withdrawals generate a reference entry in your account ledger. We retain this for account reconciliation and to help you trace any transaction query through our support channel.
Rocket transactions are recorded with the same reference-only approach. No full account credentials from your Rocket wallet are held on our side beyond what your transaction receipt already shows.
Session data helps us maintain account continuity across devices. If you switch from your phone browser to a different device, the logged session state helps restore your account position accurately.
Not every part of your digital experience falls under this single policy document. Understanding what is inside and outside its scope helps you know where to go when you have a specific question. Our policy governs data collected directly through qq880 — your account creation, session activity, wallet transactions and communications you send us. It does not govern how third-party service providers handle data on their own systems, and it does not override the terms of external payment networks like bKash, Nagad or Rocket, which have their own published policies. If you follow a link away from qq880 to an external site, their data practices are their own responsibility. Availability of these protections depends on your local law and the eligible regions we operate in.
Login events, session duration and device identifiers collected when you access your qq880 account fall fully within this policy. You may request a record of these events through the support route listed below.
Transaction references from bKash, Nagad and Rocket deposits and withdrawals processed through qq880 are covered here. The payment network's own data handling is governed separately by their respective policies.
Data generated by browsing the qq880 lobby, including cookies and clickstream data, is within scope. We use this to maintain page state and improve mobile navigation continuity for your return visits.
Game studios such as Spadegaming, Habanero, Joker and CQ9 supply game content to our lobby. Their internal data systems operate under their own policies and are outside the scope of this document.
Your account data is not locked away. We have built specific paths so you can review, correct or question what we hold without having to navigate a complex process. Log in to your account and open the account settings section — from there you can review the personal details currently on record and submit a correction request if any information is wrong. If you want to know what data categories we hold against your account, you can send a request through our support channel and we will respond with a summary of the record categories associated with your account identifier. For wallet-related records, the transaction history screen in your account shows every bKash, Nagad and Rocket movement logged against your wallet. If a transaction entry appears incorrect, raise it directly with support and quote the reference number shown on screen. Data deletion requests are handled case by case; some records must be retained for account security and legal compliance depending on your jurisdiction, so we will explain what can and cannot be removed when you contact us.
Open account settings after login to see the personal information currently held. The fields shown are the same ones used for account verification and wallet-related correspondence.
If your name, contact number or any registered detail is incorrect, submit a correction through the support channel. Bring your account identifier and the correct information to speed up the process.
Questions about specific data categories, retention periods or how a particular record was generated can be submitted via the support route. We aim to respond with a clear category-level summary.
For wallet transaction queries tied to bKash, Nagad or Rocket, open the transaction history screen, locate the reference number and contact support with that reference quoted directly in your message.
If you have a question about this Privacy Policy — including how a specific data record was created, how long it is retained, or how to exercise your access rights — the routes below are how you reach the team. Use the channel that works best for your device and query type. We do not publish response-time commitments here, but every query submitted through a published channel is received and tracked. Availability of support depends on the operational schedule shown in your account area.
Open the live chat widget from your account dashboard. Quote your account identifier and the specific data topic you are asking about so the agent can pull the right record category.
Send your data or privacy query to the support email address listed in the Help section of your account. Include your registered contact number and a clear description of the record or right you are asking about.
The Help Centre linked from your logged-in account area contains published articles on data access, correction requests and wallet transaction records. Check there first for common policy questions before raising a direct query.
Security around your account data is built into every layer of how qq880 operates. Session tokens expire after a period of inactivity, so an unattended browser on your phone does not stay open indefinitely. Wallet transaction records — whether from bKash, Nagad or Rocket — are stored with access controls limiting which internal systems can query them. Cookie data collected during your session is used to hold lobby state and keep your mobile navigation consistent; it is not shared with advertising networks. You can manage cookie preferences through your browser settings, and clearing cookies will reset your session state on the next visit. Data retention periods differ by record type: account registration data is held while your account is active; transaction references are kept for the period required by our operating terms; session logs are cycled on a rolling basis. To request a change to any retained record, or to ask about a specific retention period, use the support contact routes shown above.
Inactive sessions on your phone or browser are automatically expired. This keeps your account protected if you step away without logging out, and it applies consistently across mobile and desktop access.
Cookies on qq880 maintain your lobby state and session continuity. They are not used to track you across unrelated sites. Browser-level cookie controls let you clear or restrict them at any point.
bKash, Nagad and Rocket transaction references are stored with restricted internal access. Only account-operation systems that need the record for reconciliation or dispute resolution can query it.
Submit a data change or deletion request through the support channel. We will confirm which record categories can be amended or removed and which must be retained under our operating terms and applicable local requirements.
These are the questions we receive most often about this Privacy Policy. If your question is not covered here, use the support contact routes listed in the section above.
We collect the name, contact details and verification information you provide during registration. We also log device and session data when you access the account. We do not collect payment credentials like your bKash or Nagad PIN — only transaction reference numbers are stored.
Yes. Log in and open account settings to review your registered details. For a full category-level summary of what we hold, send a request through the support channel with your account identifier. We will respond with the record categories linked to your account.
We store the transaction reference number and completion status for each wallet movement. This appears in your transaction history screen. Full wallet credentials are never captured. The payment network's own data practices are governed by their separate policies, not ours.
We do not sell your personal data to third parties for advertising. Data is shared only where necessary for account operation — for example, with payment processing systems. Game studios such as Spadegaming, Habanero, Joker and CQ9 supply game content but do not receive your personal account data through us.
Open the account settings section after logging in and check the fields shown there. If any detail is wrong, contact support with your account identifier and the correct information. The support team will confirm the steps needed to update the record.
Retention periods differ by record type. Account registration data is held while the account is active. Transaction references are kept for the period set out in our operating terms. To ask about a specific record or request deletion, contact us through the support routes listed on this page.