Sports / Casino
ff1111 keeps your account data, wallet activity and transaction records under a clear, documented policy. What we collect, why we collect it and how you can review or correct it — this page covers all of that, and access to this platform depends on your local law and eligible regions.
When you open an account with ff1111 and use payment routes such as Rocket, Upay or Bank Transfer, we collect the information needed to process your transactions, verify your wallet and maintain your account record. This includes your registration details, deposit and withdrawal history, device identifiers and the session data generated when you browse the lobby or navigate between game sections. We do not sell your personal data to third parties for their own marketing purposes. Data shared with payment processors — for example, when a Rocket or Upay transaction is confirmed — is limited to what those processors need to complete the transfer. Your account records are retained for as long as your account remains active and for a period after closure as required under applicable policy and legal obligations. The scope of those obligations depends on the jurisdiction in which you access this platform, so your rights under this policy may vary based on your local law and eligible regions. We use standard technical measures to protect stored data, and we review those measures periodically. If you have questions about a specific data point in your account, the support contact route described further down this page is the right place to start.
Transaction data from Rocket deposits and withdrawals is shared only with the Rocket payment processor to complete and verify the transfer. We do not retain payment credentials beyond what account record-keeping requires under applicable policy.
When you use Upay to fund your account, the wallet confirmation data is logged against your account record. This lets you verify the transaction in your account history and raise a query if a record looks incorrect.
Bank Transfer deposits create a traceable record in your account. Reference numbers and transfer confirmations are stored so you can match them against your own bank statement and contact support if a discrepancy appears.
We collect session identifiers, device type and browser data each time you log in. This helps us detect unusual access patterns and keep your account accessible only to you across mobile and desktop sessions.
This policy governs the personal data ff1111 collects and processes directly. It does not extend to third-party services you reach from our platform — including external payment processors or game studio environments — which operate under their own data practices. Understanding the boundary helps you know where to direct a data query.
Login credentials, session tokens and device records created when you sign in to ff1111 fall fully within this policy. You can review your active sessions and request a correction through the account settings page.
Deposit and withdrawal records tied to Rocket, Upay or Bank Transfer sit within this policy's scope. These records appear in your account history and are the reference point for any payment query you raise with support.
How you navigate the lobby — which game sections you open, how long a session runs — generates usage data that this policy covers. We use it to keep the site functional, not to build advertising profiles.
External payment gateways, game content studios and any linked service outside ff1111's own domain operate under their own privacy terms. We are not responsible for their data practices, and this policy does not extend to them.
You have a set of practical actions available when it comes to the data ff1111 holds on your account. If you want to see what information we hold, start by logging in — your account history page shows transaction records, including Rocket and Upay deposits, withdrawal timestamps and wallet confirmation references. For registration details like your name, contact number or email address, the account settings section shows what is stored and lets you submit a correction request directly. If a record looks wrong — a Bank Transfer that does not match your bank statement, or a session entry you do not recognise — raise a query through the support route shown on the contact page. We will investigate and respond. You may also ask us to close your account and explain what happens to your data afterward; the timeline and scope of that process depends on applicable legal obligations in your eligible region. Every request is handled through the same contact route: the support channel published on this site.
Log in and open the account history section to see transaction records, session entries and wallet activity tied to your profile.
Account settings let you update registration details. For corrections that require verification, submit a request through the published support contact route.
If a transaction record, session entry or stored detail looks incorrect, contact support with the specific record reference. We will review and respond.
Ask support to explain what happens to your data when your account is closed. The retention period depends on applicable obligations in your eligible region.
If you have a question about how your data is handled, the routes below are the ones published on this site. Use the contact method that matches your query type — account record questions are usually resolved faster when you include the relevant transaction reference or session date.
Open the support chat from your signed-in account page. Include your account reference and the specific record you are asking about to help the team locate your data quickly.
Send your data query to the email address published on the contact page. State your account details and describe the data point clearly so we can locate and review the relevant record.
The help centre on this site covers common data and account questions. Check there first — many queries about transaction records and account details are answered without needing to contact support directly.
applies documented technical measures to protect the data stored on your account. These cover the storage of transaction records, session identifiers and wallet confirmation data from payment routes including Rocket and Upay. We use cookies to keep your session active and to remember your lobby preferences between visits; you can manage cookie settings through your browser. Account security depends on both our technical controls and the steps you take — keeping your login credentials private and logging out on shared devices are the most effective actions on your side. If you believe your account has been accessed without your permission, contact support immediately using the route published on this site. Data retention periods depend on applicable legal obligations in your eligible region, and we do not keep data longer than those obligations require. To request a change to stored data or to ask how long a specific record is kept, use the support contact route described on the contact page.
We use session cookies to keep you logged in and functional cookies to remember lobby preferences. Manage or clear these through your browser settings at any time without affecting your account data.
Technical controls protect your login session and stored records. Keep your credentials private and log out on shared mobile devices to reduce the risk of unauthorised access to your account.
We retain your account and transaction data for as long as your account is active and for a period after closure as required by applicable obligations in your eligible region.
To correct, query or request information about stored data, use the published support contact route. Include your account reference and the specific record so we can respond accurately.
These questions cover what we typically hear from account holders about data handling, wallet records and how to act on a data concern. If your question is not here, the support contact route is the right next step.
We collect your registration details — name, contact information and login credentials — along with device identifiers and session data. Once you make a deposit via Rocket, Upay or Bank Transfer, the transaction reference and wallet confirmation are added to your account record.
Yes. Log in and open your account history page to view transaction records, session entries and wallet activity. For registration details, check the account settings section. If you need a broader data summary, contact support with your account reference.
Update basic details through the account settings page. For corrections that require verification — such as a mismatched name on a Bank Transfer record — submit a request through the support contact route published on this site and include the relevant record reference.
Data is shared with payment processors like Rocket and Upay only to complete and verify your transactions. We do not sell your personal data to third parties for marketing. Third-party game studios and external services operate under their own data practices.
Retention periods depend on applicable legal obligations in your eligible region. We do not keep data longer than those obligations require. Contact support to ask about the specific retention period that applies to your account closure.
Contact support immediately using the chat or email route published on the site. Include your account reference and any session or transaction details that look unfamiliar. We will investigate and take steps to secure your account.