Mobile / Sports
fc1111 collects only the account and transaction data needed to run your wallet, process Nagad, Rocket and Upay payments, and keep your session secure. This policy explains what we collect, why we collect it, and the choices available to you — access and eligibility depend on your local law and the eligible regions we serve.
When you open an account with us, we collect the details you enter during registration — your name, contact address, and the credential you use to sign in. When a payment is made through Nagad, Rocket or Upay, our system records the transaction reference, the amount and the wallet identifier your provider supplies. We do not store full card numbers or wallet PINs; those remain with your payment provider. We also collect session data — the device type, browser version and approximate region — so we can serve the account interface correctly on mobile. Cookies are used to keep your session active and remember display preferences; you can manage cookie acceptance through your browser settings at any time. Data we hold is used strictly for account operation, payment reconciliation and support resolution. We do not sell your personal data to third parties. Where we engage a third-party service — such as a fraud-detection layer — that service receives only the minimum data required to perform its function and operates under a data-processing agreement with us. Retention periods are kept to what is operationally necessary; records tied to payment transactions may be held longer where financial regulations applicable to eligible regions require it.
When you transact via Nagad, we log the reference and amount — not your Nagad PIN or credentials.
Rocket payments are reconciled using the wallet identifier supplied by Rocket's system; your full account details stay with Rocket.
Upay transfers generate a session token we use for reconciliation. We do not retain any authentication credential from Upay's side.
Session logs record device type and browser version so the account page renders correctly on your phone or desktop without storing personal device identity.
This policy covers the data fc1111 processes directly through this website and the account system. It does not govern external services you reach by leaving our domain, and it does not apply to payment providers such as Nagad, Rocket or Upay — each of those has its own data terms. The four areas below set out what falls inside and outside our scope so you know exactly where our obligations begin and end.
Data you enter when you create or update your account — name, contact details, login credential — falls fully within this policy. We control how that data is stored, secured and deleted upon a valid request.
Transaction references from Nagad, Rocket and Upay are within scope for reconciliation records. The payment provider's own handling of your wallet credentials is governed by their separate privacy terms, not ours.
Browsing activity on the lobby, game session logs and bet history held in your account record are within scope. We use this data to render your account history — not to share it with studios or third-party advertisers.
Any external link, third-party tool or provider site you navigate to from our platform is outside this policy's scope. We are not responsible for how those services handle your data once you leave our domain.
You have concrete actions available to you regarding the data we hold. You can ask us to confirm what personal data is on your account, request a correction if any detail is wrong, or ask us to delete data where we are not required to keep it for payment reconciliation or compliance with regulations applicable to eligible regions. These rights are not automatic in every jurisdiction — whether a specific right applies to you depends on your local law and the region from which you access fc1111. To exercise any of these rights, reach our support team through the contact route published on this page; we will respond through the same channel once we have verified your account identity. We do not action requests submitted without account verification because we cannot confirm the request comes from the account holder. Where a deletion request conflicts with a financial record we are required to retain, we will explain that conflict clearly and tell you what can and cannot be removed.
Open your signed-in account area to see the profile fields, transaction history and session log we hold. This is the fastest way to check what is stored without contacting support.
If a name, contact address or wallet reference is recorded incorrectly, submit a correction request through our support channel with your account ID. We will update the record and confirm the change.
For questions about data retention, what a specific record contains, or how a third-party processor received your data, write to us through the published support route and we will address your question directly.
You may request removal of personal data we are not legally required to retain. State your account ID and the specific data in question; we will confirm what can be removed and action it within our published handling window.
If you have a question about how your data is handled, want to raise a correction, or need to understand why a specific record exists, these are the routes we publish for policy-related contact. Use the channel that suits your situation; for account-specific requests, always include your account ID so we can verify your identity before acting.
Open the support chat from your signed-in account page. State that your query is a privacy or data request so it is routed to the right team rather than general account help.
Send your data request to the email address published in the contact section of this site. Include your account ID and describe clearly what data action you are requesting.
The account help section in your signed-in dashboard lists the steps for submitting a formal data request. Follow those steps to ensure your request is logged and tracked by our team.
We apply access controls so that only the account functions that require your data — payment reconciliation, session management, support resolution — can read it. Staff access to personal account data is role-restricted and logged. Cookie use is limited to session continuity and display preferences; no advertising or tracking cookies are set by us without your browser-level consent. If you clear cookies or block them, your session will not persist between visits but no personal data is lost. Account passwords and wallet-linked credentials are not stored in plain text. We review data retention schedules periodically and remove records that no longer serve an operational or regulatory purpose. If this policy is updated, the revised version will appear at this URL with the effective date noted at the top of the page.
Internal access to your account data is limited by role. Only teams with a direct operational need — such as support resolving a Rocket or Nagad transaction query — can view relevant records, and those accesses are logged.
Session and preference cookies can be managed or cleared through your browser settings at any time. Doing so will end your current session but will not delete the personal data held in your account record.
Passwords and wallet-linked tokens are not stored in readable form. Payment references from Nagad, Rocket and Upay are stored as reconciliation identifiers only — not as credentials that could be used to access your wallet.
When this policy changes materially, the updated version replaces this page and the effective date is noted at the top. Continued use of your account after an update indicates acceptance of the revised terms where local law permits.
These are the questions we receive most often about how fc1111 handles account data, cookie use, payment records and your rights. If your question is not covered here, use the support contact route listed on this page.
We do not sell your personal data. We share only the minimum data required with third-party services — such as fraud detection — that operate under a data-processing agreement with us. Payment providers like Nagad and Rocket receive only the transaction reference their system needs for reconciliation.
We keep data for as long as it is needed to operate your account or meet financial record requirements applicable to eligible regions. When data is no longer needed for either purpose, we remove it. You can ask us to clarify the retention period for a specific record through our support channel.
Yes, you can request deletion of personal data we are not required to retain. Send the request through our published support route with your account ID. Where a transaction record must be kept for regulatory reasons, we will explain exactly which records cannot be removed and why.
We log the transaction reference, the amount and the wallet identifier supplied by your payment provider. We do not store your wallet PIN, password or any authentication credential. Your payment provider handles their own data under their separate privacy terms.
Open the account profile section in your signed-in dashboard to update standard fields directly. For fields you cannot edit yourself — or if you find a transaction record is incorrect — contact us through the support chat or email route with your account ID and we will correct it.
This policy covers data we process for accounts created through this site. Whether you are eligible to access fc1111 at all depends on your local law and the eligible regions we serve. If access is not available in your jurisdiction, this policy does not create any entitlement to use the service.