Skip to content
ff1 App / Mobile
YOUR DATA AT

ff1 Privacy Policy — How We Handle Your Information

ff1 collects only the account and transaction data needed to run your wallet, process payments through bKash, Rocket and Bank Transfer, and keep your session secure. This policy explains what we collect, why we collect it, and what choices you have — clearly, without legal filler.

  • Account data covered
  • bKash, Rocket, Bank Transfer context
  • Your rights explained
  • Bangladesh-eligible regions
POLICY SCOPE AND BASIS

What This Policy Covers and Why It Applies to You

When you open an account with ff1, we collect the details you enter during registration — your name, contact address and preferred payment method. When you fund your wallet using bKash, Rocket or Bank Transfer, the transaction reference and amount are logged against your account record so you can review them in your account history at any time. We also collect device and browser signals — screen type, session duration, page paths — to keep the site running correctly across mobile and desktop. We do not sell your personal data to third parties for their own marketing. Data we hold is used only to operate your account, process your wallet movements and send you service messages you have opted into. Retention periods depend on the category of data: transaction records are held as required by applicable financial rules; session logs are cleared on a rolling schedule. If your use of ff1 is subject to restrictions under your local law, the availability of certain account features will reflect those restrictions. We apply the same data standards to all accounts regardless of region.

  • bKash

  • Rocket

  • Bank Transfer

  • Account wallet

  • Session data

INSIDE AND OUTSIDE SCOPE

Where This Policy Applies and Where It Does Not

This policy covers all data processed when you use ff1 directly — from account creation through to wallet activity. It does not extend to third-party services you reach by leaving ff1, and it does not override any local legal requirement that applies to your eligible region.

  • Account Access

    Data you submit when logging in, resetting credentials or updating your profile falls fully inside this policy. We process that data only to authenticate your session and maintain your account record.

  • Wallet Transactions

    bKash, Rocket and Bank Transfer movements linked to your account are logged here. Transaction references, amounts and timestamps are covered by this policy and visible to you in your account history.

  • Site Content and Games

    Your browsing path inside ff1 — which game rooms you open, how long a session runs — is covered here as usage data. We use it to keep pages loading correctly, not to build a marketing profile sold elsewhere.

  • Third-Party Services

    If you follow a link away from ff1 to an external payment gateway or support tool, that service operates under its own privacy terms. We do not control or represent those terms, and this policy does not cover them.

ACTIONS AVAILABLE TO YOU

Your Practical Rights Under This Policy

You can review, correct and query the data ff1 holds on your account at any time. The starting point is your signed-in account area, where your profile details, wallet history and communication preferences are all visible. If something looks wrong — a name misspelled, a contact address outdated — you can update it directly in the account settings fields shown there. For data that cannot be edited in the self-service view, such as a historical transaction record, you can raise a query through the support route listed in the section below. We will confirm what we hold, explain why it is retained and, where the applicable rules permit, correct or remove it. If you decide to close your account, we will explain which records we are required to keep and for how long, and which data is deleted on closure. Eligibility to act on these rights may depend on your local law and the region from which you access ff1.

  • Review Your Records

    Open your account page after signing in to see your profile data, wallet transaction history and any communication preferences you have set. Everything we hold about your session is visible there.

  • Correct Account Details

    Update a misspelled name, a changed contact address or an outdated preference directly in your account settings. Fields that cannot be self-edited can be corrected by contacting support with the relevant details.

  • Raise a Data Query

    If you want to know exactly what data category we hold, why we hold it, or how long the retention period runs, send your question through the published support route. We will respond with the specific record detail you ask about.

  • Request Account Closure

    You can request account closure at any time. We will tell you which transaction records must be kept under applicable rules and confirm when the remaining data has been deleted from active systems.

PRIVACY CONTACT PATHS

How to Reach Us About This Policy

If you have a question about the data ff1 holds on your account, the right channel depends on what you need. Routine account queries — wallet history, profile corrections — are handled fastest through the live chat route visible when you are signed in. Formal data requests or correction notices should go through our published email contact so there is a written record. Support availability follows what is published on the contact page of the site; we do not commit to response windows we have not published.

  • Live Chat

    Open the chat widget from your signed-in account page for questions about your wallet history, transaction references or account details. This is the direct route for day-to-day data questions.

  • Email Support

    Send formal data requests — corrections, retention queries, account closure requests — to the email address published on the ff1 contact page. Email gives you a written record of your request and our response.

  • Account Help Page

    The help section inside your signed-in account covers common data and privacy questions with step-by-step instructions. Check there first before raising a support ticket — many answers are already published there.

HOW WE MANAGE DATA

Data Handling, Cookies and Account Security at ff1

We keep the technical and procedural side of data handling straightforward. Account credentials are stored in encrypted form; session cookies are used only to keep your login active and track the page path you follow inside ff1 — not to serve third-party advertising. You can clear session cookies through your browser settings at any time without losing your account. Retention is category-based: wallet transaction records linked to bKash, Rocket or Bank Transfer activity are held as long as applicable financial rules require; usage and session data is cleared on a rolling cycle. If you request a change to your data and we cannot action it in the self-service account view, we will confirm the outcome in writing through the email route.

  • Cookie Use

    Session cookies keep your login active and record your page path inside ff1. We do not use cookies to build a profile for third-party advertisers. Clear them any time through your browser settings; your account stays intact.

  • Credential Security

    Your account password and linked wallet details — whether bKash, Rocket or Bank Transfer — are stored in encrypted form. We do not log or store your payment credentials in plain text at any point in the process.

  • Retention Schedule

    Transaction records are held for the period required by applicable financial rules. Session and usage logs are cleared on a rolling schedule. When you close your account, we confirm in writing which records remain and why.

  • Change Requests

    Submit a data correction or removal request through live chat or the published email address. We confirm what we can action, explain what we are required to retain, and close the request with a written outcome.

PRIVACY QUESTIONS ANSWERED

Common Questions About Your Privacy at ff1

These are the questions we get asked most about this policy — covering what data we hold, how your bKash and Rocket wallet activity is recorded, what you can request and how to contact us.

What personal data does ff1 collect when I open an account?

We collect the details you enter at registration — name, contact information and your chosen payment method. Once your account is active, we also log wallet transactions through bKash, Rocket or Bank Transfer and session data such as device type and pages visited inside ff1.

Can I see all the data ff1 holds on my account?

Yes. Your signed-in account page shows your profile details, wallet transaction history and communication preferences. For data that is not visible in the self-service view, raise a query through live chat or the published email contact and we will confirm what we hold.

How long does ff1 keep my wallet transaction records?

Transaction records — including bKash, Rocket and Bank Transfer references — are held for as long as applicable financial rules require. Session and usage logs are cleared on a shorter rolling cycle. We explain the exact period if you ask through the support route.

Does ff1 share my data with third parties?

We do not sell your personal data to third parties for their own marketing. Data is shared only where it is required to process your wallet activity or comply with a legal obligation. Any third-party service you reach by leaving ff1 operates under its own separate privacy terms.

How do I correct an error in my account details?

Open your account settings page while signed in and update the field directly. If the field is not editable in the self-service view — for example, a historical transaction reference — contact support through live chat or email with the correction you need and we will action it.

Does this policy apply to me if I am accessing ff1 from Bangladesh?

This policy covers all accounts. Whether specific account features are available to you depends on your local law and eligible region. Where local rules impose restrictions, the features visible in your account will reflect those restrictions — we do not override applicable local requirements.