Sports / Mobile
fg6662 is clear about what data we collect, why we collect it, and how you can review or correct it at any time. Access to this platform and the protections described here 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 verification documents we are required to request. We also record activity linked to your account wallet, including deposits made through bKash, Nagad or Upay, and any withdrawals you initiate. This data lets us maintain your account, process your transactions correctly, and respond when you contact support. We do not sell your personal information to third parties. We may share data with payment processors — including the local wallet rails you use — strictly to complete the transaction you requested. Where required by law or a regulatory body with jurisdiction over our operations, we may disclose account records; we will do this only to the extent required and will not go further than necessary. Cookies and session data are collected when you browse the site. You can adjust cookie preferences through your browser settings, though some account functions depend on session cookies to work correctly. Retention periods for your account data are reviewed periodically; we keep records only as long as they are operationally necessary or legally required. Your use of this platform and the protections described in this policy depend on your local law and the eligible regions in which access is permitted.
This policy covers the data we collect and process across every part of the fg6662 platform — from your account login to your transaction history. Understanding its boundaries helps you know exactly what protections apply to you and where to look for additional terms.
Any data collected when you log in, update your profile or change your account settings falls within this policy. This includes login records, device identifiers and any identity information you submit for verification purposes.
Deposit and withdrawal records processed through bKash, Nagad or Upay are covered here. We retain transaction logs to resolve disputes, answer your queries and meet any reporting obligations that apply under relevant jurisdiction.
Pages you visit, games you open and session duration are recorded to help us improve the platform and personalise your account view. This browsing data is held in aggregate form except where it links directly to your account.
Payment processors, game studios and external links operate under their own privacy terms. Once you leave the fg6662 environment — or interact with a third-party wallet interface — this policy no longer governs how that service handles your data.
Your account gives you direct access to much of the information we hold about you. From your account settings page you can review the personal details we have on record and update contact information if something has changed. If you believe any stored data is incorrect — for example, a name that does not match your verification document — you can raise a correction request through our support route and we will address it without unnecessary delay. For records that are not directly editable in your account, such as historical transaction logs or older verification submissions, a written request to our support team is the correct path. We will confirm what we hold, explain how long we retain it, and tell you what options are available to you. Eligibility for specific rights may vary depending on your local law and the region in which you access this platform. Where local law grants a right we are technically and legally able to honour, we aim to respond promptly and clearly.
Open the account settings page to see the personal and contact details we currently hold. Transaction history is visible in your wallet section and covers bKash, Nagad and Upay activity linked to your account.
If your stored name, contact number or email address is wrong, update it directly in your profile or raise a request through support. We will verify the change against your account before applying it.
Any question about what we hold, why we hold it, or how long we keep it can be sent to our support team. We will reply with a plain explanation rather than a template response.
If you want to understand how a specific piece of information — a bKash deposit record or a verification document — is stored or processed, our support routes are the fastest way to get a direct, account-level answer.
If this policy raises questions you cannot resolve through your account settings, these are the published routes to reach us. We do not publish support hours or response-time commitments we cannot verify — contact us through any of the routes below and we will respond as promptly as our published capacity allows.
Open the chat widget visible on the site when you are logged in. Use this route for account-level questions about data, wallet records or verification status.
Send a written request to the support address published in your account help section. Email is the recommended route for correction requests or detailed data enquiries.
The help section inside your account lists published policy articles and step-by-step guides for common requests, including how to update personal details or query a transaction record.
We apply access controls to limit who within our organisation can view your account data. Stored records — including wallet transaction logs for bKash, Nagad and Upay — are held in secured environments with access restricted to authorised processes only. Cookies used on this platform serve session management and account functionality; you can review cookie settings in your browser at any time.
We keep your account data only as long as it is needed for account operations or required under applicable law. When data is no longer necessary, we remove or anonymise it. The specific retention period depends on the type of record and the jurisdiction applicable to your account.
Session cookies let your account stay active while you browse. Analytics cookies help us understand which account pages are used most. You can control non-essential cookies through your browser settings without losing core account access.
Access to your account data is protected by your login credentials. We do not share your account password with any third party. If you suspect unauthorised access, update your password immediately and notify support through the live chat or email route.
When we update this policy, we publish the revised version on this page. We may also send a notification to the contact details held in your account. Continued use of the platform after an update means you have had the opportunity to review the changes.
These are the questions we receive most often about how fg6662 handles account data, what rights you have, and how to reach us if something needs correcting. If your question is not covered here, the support routes listed on this page are the right next step.
We collect the details you submit during registration — name, contact number, email address and any verification documents we request. We also record your login activity, device type and the transaction history linked to your account wallet, including bKash, Nagad and Upay records.
We share data only with the payment processors needed to complete your transactions — for example, when you deposit via Nagad or withdraw to bKash. We do not sell your information. Disclosure to a regulatory or legal authority happens only when required by applicable law and only to the extent required.
Your account settings page shows the personal details we currently hold. You can edit contact information there directly. For records you cannot edit yourself — such as older verification submissions — send a correction request through live chat or email support and we will handle it from there.
Retention periods depend on the type of record and what local law requires. Active account data is held while your account remains open. Transaction logs may be kept longer if a legal retention obligation applies. When records are no longer necessary, we remove or anonymise them.
You can submit a data deletion request through our email support route. Whether we can action it fully depends on your local law and any retention obligations that apply to your account records. We will explain what is possible and what must remain on record when we respond to your request.
This policy describes how we handle data across the platform. Whether you can access fg6662 and which specific protections apply depend on your local law and the eligible regions permitted at the time of access. We recommend reviewing local regulations before opening or using an account.