LEGAL REFERENCE

Privacy Policy for fc 24

fc 24 puts your account data, Pakistan payment references and support conversations into one clear Privacy Policy before you open your account. Read how we collect, use, protect...

Account data usePakistan payment contextSupport privacySecurity checks

Explore lobby Read FAQ

How We Handle Your Data

This Privacy Policy explains what fc 24 collects when you create or manage an account, verify access, contact us, or use Pakistan payment references such as JazzCash, Easypaisa, SadaPay and Raast. We collect only the data needed to run account security, identity checks, transaction matching, fraud screening, customer care and legal record keeping where local law permits. We do not sell your

personal data. When service partners help us with hosting, analytics, messaging, verification or payment processing, we require them to handle data only for the agreed purpose. You can ask us to update, correct or remove eligible account data, subject to security logs, settlement records and legal retention duties.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT PATHS

Privacy Help Through Our Team

Privacy questions should reach the team that can actually trace the account record. Send your account mobile number, registered email and a...

POLICY CHECKS

Checks Behind This Policy

We keep the policy useful by connecting it to real account workflows: login protection, wallet matching, withdrawal verification, support transcripts and device security. Each update is checked against...

Account creation mapping

We map each sign-up field to a reason before keeping it. Your name, mobile number, email and location signals are...

Verification records

When we verify an account or withdrawal request, we keep decision records separate from casual support chat. That split reduces...

Local payment matching

JazzCash, Easypaisa, SadaPay and Raast references are used to match your transaction to your fc 24 account. We record the...

Device security signals

We may process device, browser, IP and session signals to detect unusual access. These signals help us flag account takeovers...

Support transcript handling

Support conversations are retained so we can follow privacy requests, resolve disputes and train staff on safer replies. We restrict...

Scheduled policy checks

We check this Privacy Policy when account flows, payment processors, analytics tools or support systems change. If a change affects...

Consistent Across Legal Pages

Our Privacy Policy works alongside related legal pages, but it has its own job. It explains personal data handling, while terms explain account rules and promotional pages explain...

Terms alignment

Our terms may describe account access, but this page explains the personal data behind that access. If we ask for verification, the privacy reason is recorded here rather than hidden in general wording.

Cookie alignment

Cookie wording connects to this policy by explaining browser storage, analytics tags and preference tools. This page then describes how those signals may connect to account security and service measurement.

Promotion alignment

When a promotion needs eligibility checks, this policy explains the data categories used for matching. We avoid asking for extra personal data when account records already confirm the required condition.

Payment alignment

Payment pages may show wallet names and transaction steps. This policy explains the privacy side: reference storage, settlement checks, fraud screening and retention for JazzCash, Easypaisa, SadaPay and Raast records.

Security alignment

Security wording covers account protection, while this page identifies related data such as login time, device signals and failed attempts. Keeping those pages aligned makes privacy choices easier to understand.

Support alignment

Support pages tell you how to contact us. This policy explains how we store those conversations, who may access them, and why we may keep them after a ticket is closed.

Regional alignment

Access wording refers to supported regions where local law permits. This policy applies that same regional approach to account checks, language support and payment records connected with Pakistan service paths.

Privacy Layout You Can Read

The page is arranged so you can find the privacy point that matters without digging through legal noise. We label data uses, partner access, retention, security...

Plain section labels

Each privacy area is labelled by action, such as account creation, verification, wallet matching or support. That makes it easier to see why data is collected before you decide what to share.

Short retention wording

Retention language explains why some records stay after an account change. Security logs, settlement references and dispute records may remain longer than marketing preferences because they protect account integrity.

Partner access markers

Where outside service providers help with hosting, analytics, messaging or verification, we mark the purpose. They are not given permission to use your data for unrelated activity.

Choice language

We explain choices around correction, deletion, contact preferences and access requests. Some choices may be limited by settlement records or legal duties, and we state that limitation in direct wording.

Mobile readable blocks

Privacy text is split into short blocks so you can check it on a phone before opening your account. Long clauses are avoided where a direct sentence explains the same point.

Local reference examples

Examples use Pakistan context such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast. These examples help you understand payment privacy without sharing extra wallet data with support.

Questions About Your Privacy

We collect account details, contact data, login signals, verification records, support messages and payment references needed to run your account. We avoid collecting wallet PINs, full private credentials or unrelated personal files.

We use JazzCash, Easypaisa, SadaPay, NayaPay and Raast references to match transactions to your account, confirm settlement status and investigate disputes. The reference helps us process the record without needing wallet login details.

Yes. Send a correction request through chat or email with your account email, mobile number and the field that needs fixing. We may verify ownership before changing sensitive details such as phone number or identity records.

We share data only when service partners need it for hosting, analytics, messaging, verification, payment processing, security or legal support. Partners must handle the data for the agreed service, not unrelated use.

Retention depends on the record type. Support tickets may be kept for service history, payment references for settlement checks, and security logs for account protection. We remove eligible data when it is no longer needed.

Contact us by chat or email and state the privacy action you want: access, correction, deletion, restriction or preference change. Include account identifiers only, never wallet passwords, PINs or private banking credentials.