Casino / Mobile
f222c is straightforward about what data we collect, why we collect it, and how you can review or correct it. This policy covers every account interaction — from your first login to transaction records tied to Rocket or Upay payments — and applies to all activity on f222c, subject to your local law and eligible regions.
When you open an account on f222c, we collect the details you submit during registration — your contact information, login credentials and any payment identifiers linked to your wallet activity. For transactions processed through Rocket or Upay, we retain a record of the deposit reference, amount and timestamp as part of your account history. We do not store full wallet credentials on our servers; the payment channel handles authentication on its own infrastructure. Cookies and session data are used to keep your lobby state between visits and to recognise your device on return. We do not sell your personal data to third parties. Where we share data with service providers — for example, payment processors or fraud-screening tools — those parties are bound by data-handling obligations consistent with this policy. Your eligibility to use f222c is subject to your local law and the eligible regions we operate in; if you are accessing from a jurisdiction where online account activity of this kind is restricted, this policy still describes how any data we have collected about you is managed. You can raise a data question at any time through the support route listed in this policy.
Not every part of your experience with f222c falls under the same policy scope. The table below draws a clear line between what this policy governs directly and what falls under a separate framework — so you know exactly which rules cover each part of your activity.
Covered by this policy. Any data you provide when creating or updating your f222c account — including contact details and security credentials — is handled under the terms set out here. You can request a review of this data at any time.
Partly covered. We hold transaction references for deposits made via Rocket or Upay, but the payment channel itself operates under its own data terms. We do not access your wallet PIN or full account number on those platforms.
Not personal data. Game lobby interactions — which categories you browse, which titles you open — may be logged in aggregate to improve the experience, but this activity is not tied to personally identifiable records without your account login being active.
Outside this policy. If you follow a link from f222c to an external site or use a third-party authentication flow, that service's own privacy terms apply. We cannot control or be responsible for how external platforms handle your data.
Your account on f222c gives you direct access to several of the records this policy describes. Log in, open the account section and you can see the profile details we hold, including the contact information and payment references tied to your deposit history. If something looks wrong — a misspelled name, an outdated email address, an unfamiliar transaction reference — you can submit a correction request through the support channel. We aim to acknowledge correction requests and act on them within a reasonable period; we will confirm when the change is applied. For records where we cannot make a self-serve edit available — such as archived transaction logs — you can raise a specific request through the support route, and we will respond with what we can share under applicable law. If you want to know exactly what data we hold about your account, you can send a written request; we will respond with a summary of the categories of data stored. All of these actions depend on verifying your identity first, which protects your account from unauthorised access.
Open the account section after logging in to see profile details and transaction references currently held under your account. This is the fastest way to check whether the information we hold is current and correct.
If any stored detail is inaccurate, submit a correction request via our support channel. We will confirm the change once it has been applied and note the updated record in your account history.
Send a written request asking what data categories we hold for your account. We will respond with a summary and, where legally required, provide further detail about how that data has been used.
If any part of this policy is unclear or you have a specific concern about your data, contact our support team directly. We handle policy questions separately from general account queries so they reach the right review path.
If you have a question about your data, a correction to request, or a concern about how your information has been handled, use one of the routes below. We do not publish channels that are not actively monitored — each route listed here connects to a real review path.
Open the chat widget on f222c while logged in to raise a data or privacy question directly. Logging in first means we can verify your identity and connect the query to your account record without asking for additional confirmation steps.
Send your data request or correction query to the support email address published in the site's contact section. Include your registered account email so we can locate your record. Written requests for data summaries should also come through this route.
Use the in-account support form available after login to submit a structured request. This route is suitable for correction requests and data review queries because it automatically attaches your account identifier to the submission.
We apply consistent data handling across every part of f222c. Here is what that looks like in practice — from cookies to retention periods and how we respond when you ask for a change.
We use session cookies to maintain your lobby state and recognise your device on return visits. You can manage cookie preferences through your browser settings. Disabling cookies may affect how the account section and payment flow behave on your device.
We keep your account data for as long as your account remains active and for a period after closure as required by applicable rules. Transaction references linked to Rocket or Upay deposits are retained as part of your financial record during this window.
Access inside f222c is limited to the teams that need it to operate your account and process support requests. Third-party processors — such as payment channel providers — access only the data necessary to complete the transaction or fraud check.
To request a correction or ask about data deletion, use the email or account form route listed in this policy. We will confirm receipt, verify your identity and communicate what action we can take under the applicable rules for your region.
These are the questions we hear most often about how f222c handles account data and what you can do about it.
We collect the details you enter during registration — your name, contact information and login credentials. If you make a deposit through Rocket or Upay, we also retain a transaction reference and timestamp. We do not store your full wallet credentials or PIN on our servers.
Yes. Log in and open the account section to view the profile details and transaction references we currently hold. For a fuller summary of data categories, send a written request through the support email. We will respond once we have verified your identity.
Submit a correction request through live chat, email support or the in-account support form. Include your registered email address so we can locate your record quickly. We will confirm the change once it has been applied and note it in your account history.
We share data only with service providers that need it to operate your account — such as payment processors for Rocket or Upay transactions and fraud-screening tools. Those parties operate under data-handling obligations consistent with this policy. We do not sell your personal data.
We retain your account data while your account is active and for a required period after closure. Transaction records linked to Rocket or Upay deposits are part of this retention window. The exact period depends on applicable rules for your region and eligibility.
Eligibility to use f222c depends on your local law and the eligible regions we operate in. If your access is restricted, this policy still describes how any data already collected about your account is managed, retained and made available for review or deletion on request.