Sports / App
zs880 collects only the account and transaction data needed to run your wallet, process bKash or Upay deposits, and keep your session secure across devices. What we collect, why we collect it, and how you can request changes — it is all set out here, and your access to this platform depends on your local law and eligible region.
This policy describes how zs880 processes personal information you provide when creating an account, verifying your wallet, or using any feature on zs880. Personal information includes your name, contact details, device identifiers and transaction records linked to payment methods such as bKash, Upay, Nagad or Rocket. We collect this information to authenticate your account, process wallet deposits and withdrawals, detect unusual activity and respond to your support requests. We do not sell your personal data to third parties for their own marketing. Data shared with payment processors — such as the mobile wallet services you connect — is limited to what those processors need to complete your transaction. Technical data, including your IP address, browser type and session cookies, is collected automatically when you visit the site. You can review the cookie settings available in your browser at any time. Retention periods vary by data type: account-level records are held for as long as your account remains active and for a further period required by applicable law in your eligible region. Where local law or regional eligibility restricts access to zs880, this policy applies to the extent permitted in that jurisdiction.
Transaction data passed to bKash is limited to the fields required to process your deposit or withdrawal request. We do not store your bKash PIN or full wallet credentials on our servers.
When you link an Upay wallet, only the reference data needed to match your transaction is retained. Upay handles its own authentication steps within their environment.
Nagad transaction references are logged against your account to support dispute resolution and withdrawal reconciliation. These records follow the same retention schedule as other wallet data.
Rocket payment records held by zs880 are processed identically to other wallet types — retained for account integrity, not shared for unrelated commercial purposes.
Not every service you encounter through zs880 falls under this policy. Our account flow, wallet management and on-site game sessions are covered. Anything that happens inside a third-party payment app — such as your bKash or Nagad history screen — is governed by that provider's own privacy terms, not ours. Understanding the boundary helps you know where to direct a data question.
All data collected during login, registration and account verification on zs880 falls within this policy. This includes email, phone number and the device identifiers your session generates.
Deposit and withdrawal records processed through our platform are covered here. However, the mobile wallet side of a bKash or Upay transfer is governed by that wallet provider's own policy.
Game session data — which titles you opened, session length, in-game events — is collected by zs880 to support account history and personalise your lobby view where that feature is active.
External links, embedded provider game frames from studios such as Microgaming or CQ9, and payment gateway pages operate under their own privacy terms. zs880 is not responsible for those third-party practices.
You have several concrete options when it comes to the personal data zs880 holds on your account. First, you can review the information attached to your account by visiting the account settings area once you are logged in — your contact details, linked wallet references and session history are visible there. If any detail is incorrect, you can update it directly in the relevant field or raise a correction request through our support channel. Second, you can ask us to clarify what data we hold and why. Send the question through the support route published on the site, and we will respond with the category of data and its retention basis. Third, where local law grants a deletion right and your account is not subject to an active legal hold, you can request that we remove personal data that is no longer necessary. Eligibility for this depends on your region and the applicable legal framework. Each of these paths is open to you without needing to justify the request beyond identifying your account.
Log in and open the account settings page to see the contact, wallet and session data currently linked to your profile.
Edit your name, phone number or email directly in account settings. For wallet reference corrections, raise a support ticket with the transaction detail.
Use the published support channel to ask what specific data we hold, why we hold it and how long the retention period lasts for your account type.
Where your local law allows and no legal hold applies, submit a removal request via support. We will confirm eligibility and the next steps in writing.
If you have a question about this privacy policy — a data correction, a retention query or a request to understand what we hold — use one of the contact paths published on zs880. We do not publish support hours or response time commitments here because those details are shown in the live support area of the site and may change. Always use the route that matches your query type: live chat for fast account questions, email for formal written requests.
Open the chat widget on zs880 while logged in. Use this route for account-linked data queries where you need to verify your identity in real time before we can share records.
Send a written data request to the support email address shown in the contact section of the site. Include your registered account email so we can match the request to your profile.
The help section inside your logged-in account lists the current support routes and any region-specific contact options for Bangladesh. Check there first if you are unsure which path applies.
zs880 applies standard access controls to the databases that hold account and transaction records. Staff access to personal data is restricted by role: only the team members who need a data set to resolve your support request or process your withdrawal can view it. We do not share your data with unrelated commercial third parties. Cookie use on zs880 covers session authentication, preference storage and site performance measurement — you can adjust cookie permissions through your browser settings at any time. Account security relies on the login credentials you set; we recommend keeping those credentials distinct from other services. If you switch devices mid-session — moving from mobile to desktop, which is a common pattern among Bangladesh account holders — your session token is re-verified at login rather than carried over automatically, reducing the risk of stale session exposure.
Personal data access inside zs880 is restricted by staff role. Account records, wallet references and session logs are not available to teams without a direct operational reason to view them.
Cookies on zs880 serve session, preference and performance functions. Your browser's privacy or cookie settings let you review and adjust these at any point without contacting support.
We keep account-level data for as long as your account is active. After closure, data is retained only for the period required by the law of your eligible region, then deleted or anonymised.
When this policy changes in a material way, we update the version date at the top of this page and, where practical, notify you through your registered contact method before the change takes effect.
These questions come up regularly from Bangladesh account holders who want to understand exactly what data zs880 holds and what options they have. Each answer reflects our current policy position — if your situation is more specific, the support routes listed on this page are the right place to follow up.
We pass only the transaction reference data that bKash needs to process your deposit or withdrawal. We do not share your wallet history, balance or PIN with any unrelated third party. The bKash side of any transfer is governed by bKash's own privacy terms.
Yes. Log in and open your account settings to view the contact details, linked wallet references and session records attached to your profile. For a fuller data summary, send a written request through the email support route shown on the site.
After account closure, we retain data only for the period required by the law of your eligible region — typically to support dispute resolution or comply with financial record obligations. Once that period ends, records are deleted or anonymised.
Switching devices does not create a separate data record. Your account profile stays the same. Each new session on a different device triggers a fresh login verification rather than carrying over an old session token, which limits stale credential exposure.
Open account settings while logged in and edit the field directly. If the detail is tied to a wallet reference — such as a registered Nagad or Rocket number — raise a correction ticket through live chat or email support, and include the transaction reference for faster matching.
Yes, zs880 uses cookies for session authentication, preference storage and performance measurement. You can review and adjust cookie permissions through your browser's privacy or cookie settings at any time without needing to contact our support team.