Sports / App
fa880 collects only the account data needed to run your sessions, process wallet transactions through bKash and Upay, and keep your account secure across devices. This policy sets out exactly what we collect, why we collect it, and what choices you have — with access depending on your local law and eligible region.
When you open an account with us, we collect the details you enter during registration — your name, contact address, and the wallet identifiers you use for bKash or Upay transactions. We also collect session data: which device you logged in from, browser type, IP address, and the pages you visited during that session. This device-continuity record lets us flag unusual access patterns and alert you before a problem reaches your account balance. Transaction context is kept separately. When you move funds through a local payment rail like bKash, we record the reference number, amount and timestamp — not the full wallet credentials. This record exists so you can raise a dispute, and so our support team can verify it without asking you to repeat details you already submitted. We do not sell your personal data to third parties for marketing purposes. Data is retained for the period required by the applicable rules of the eligible region where your account is registered. You can ask us to review what we hold at any time through the contact route listed in this policy. Access to your account and these services depends on your local law and the eligible region shown during account setup.
bKash transaction references tied to your account
Upay session context stored for dispute and verification use
Login device, browser and IP stored for account security alerts
Name and contact details held for account identity and support queries
Not every piece of data on or near your account falls under this same policy. Understanding the boundaries helps you know exactly where to look when you have a question about a specific record or data point.
All data generated when you log in, switch devices or reset your credentials falls inside this policy. That includes session tokens, device identifiers and the login timestamps we store for your security review.
Transaction references from bKash and Upay deposits and withdrawals are covered here. We hold the reference number and timestamp only — full wallet credentials are never stored on our side.
General browsing of game pages, lobby sections and published policy pages is logged at an aggregate level. Individual game session history within your account is covered by the account data clause, not a separate data regime.
Links leaving our platform — including payment provider interfaces and game studio environments — are governed by their own privacy policies. We cannot make commitments on their behalf and recommend you review those policies directly.
Your account record is not a locked file. There are specific, practical steps you can take right now to review, correct or question any data we hold about you. Start by opening your account settings page — the data summary section shows the registration details we have on file, including the contact address and wallet reference history linked to your profile. If anything looks wrong, you can submit a correction request directly from that page or through the support contact route below. Want to know what session records we hold? Your account activity log shows login timestamps, device types and the approximate location derived from IP — useful if you want to confirm no unexpected access has happened. For a full data export or a formal deletion request, reach out through the published support route with your account identifier ready. We aim to respond to these requests within the timeframe applicable to your eligible region. Eligibility for certain actions depends on local law.
Open account settings and check the data summary section. Your registration details and wallet reference history are visible there without needing to contact support first.
Submit a correction request from the settings page or through the support contact route. Have your account identifier ready so we can locate the right record quickly.
Use the published support route with a written request specifying your account. We process these according to the applicable rules for your eligible region and local law.
Any specific question about how a particular data point is used can be directed to us through the support route. Name the data type you are asking about for a faster, more useful response.
If you have a question that goes beyond what is covered in this policy document, or if you want to take a formal data action, these are the contact routes we publish. Use the one that fits your situation and have your account identifier ready when you get in touch.
Open the chat widget from any logged-in page to reach our support team about account or data questions. Available through the support icon in your account dashboard.
For written data requests — corrections, export requests or deletion queries — use the email contact address published in the support section of your account area.
The help centre inside your account contains published articles on data handling, session records and how to submit a formal request. Check there first for step-by-step guidance.
We keep data handling straightforward and document the key practices below so you know what is in place before you need to ask about it.
We use session cookies to keep you logged in across page visits and preference cookies to remember your account settings. No third-party advertising cookies are set by us. You can review and clear cookies through your browser settings at any time.
Access to your stored account data is restricted to authenticated team members handling your support or verification request. We do not grant open internal access to personal records — queries are logged and tied to a support ticket.
We keep account and transaction records for the period required by the rules of your eligible region. After that period, records are removed from active systems. Retention details for your specific region are available on request through the support route.
When this policy changes in a material way, we post a notice inside your account dashboard before the new version takes effect. You can also find the current version of this policy at any time from the footer link on every page.
These are the questions we receive most often about how your data is handled, what rights you have, and how to act on them.
We do not sell your data to third parties for marketing. Data may be passed to payment processors like bKash or Upay strictly to complete your transaction. Third-party game environments operate under their own privacy policies, which we recommend you review directly.
Open account settings and go to the data summary section — your registration details and wallet reference history are listed there. For a full data export, submit a written request through the support email route with your account identifier included.
Yes. Submit a deletion request through the support email contact with your account identifier. We process it according to the rules applicable to your eligible region. Note that some records may need to be retained for the minimum period required by local law.
We store the reference number, amount and timestamp for each bKash transaction linked to your account. Full wallet credentials are never stored on our side. These records are kept for the retention period applicable to your eligible region and are available to you on request.
General lobby browsing is logged at an aggregate level only. Your individual game session history inside your account is covered under the account data clause of this policy. Game studio environments outside our platform are governed by their own separate policies.
We post a notice inside your account dashboard before any material change takes effect. The current version of this policy is always accessible from the footer link on every page. We do not make retroactive changes that reduce your existing rights without prior notice.