Account terms link
Our account terms explain eligibility, access and service use. The Privacy Policy matches those terms by showing which personal data is needed to create, secure and maintain your account.
LEGAL REFERENCE
Your Privacy Policy at fh4
fh4 puts privacy controls, account data use, security checks and Pakistani payment records in clear terms before you open an account. Read how we handle your data across...
Account data scopePakistan payment contextSecurity check wordingContact route clarity
How We Handle Account Data
fh4 collects only the data needed to run your account, protect access, process payments and answer privacy requests in supported regions. This can include your name, contact details, device signals, login records, transaction references and support chat history. When you use JazzCash, Easypaisa, SadaPay or Raast, we keep payment references tied to your account so deposits, withdrawals and checks can be matched
without exposing more than we need. We do not sell your personal data. We share limited records with payment processors, fraud checks, hosting partners and service teams when that is needed for account security, legal duties or dispute handling. You can contact us to ask for access, correction or deletion where local law permits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CHECKED PROCESS
How We Keep Policy Accurate
Our Privacy Policy is maintained by the team that handles account access, payment operations and support handling for fh4. We use live process checks rather than generic wording...
Account flow checks
We test the registration journey and list the data fields actually requested. If a field is removed or added, the...
Payment record mapping
Our payment team confirms how JazzCash, Easypaisa, SadaPay and Raast references are stored. The policy describes record matching, not broad...
Security access logs
We describe device signals, login records and session checks because they protect your account. Access to those logs is limited...
Support transcript care
Support conversations may contain privacy questions, payment references or account change requests. We keep transcripts for service and dispute handling...
Policy change tracking
When we change data handling, we adjust the policy date and wording. Material changes are written in plain English so...
Local wording check
We write for Pakistan using local payment names and plain English. Jurisdiction wording stays cautious, with access described only for...
PAGE ALIGNMENT
Where Our Policies Stay Consistent
The Privacy Policy does not stand alone. We align it with account terms, cookie wording, payment records and support handling so your data rights are not described one way on one page...
Cookie wording match
Cookie wording covers browser storage and device signals. The Privacy Policy connects those signals to security, session continuity and fraud checks without expanding them beyond their stated purpose.
Payment page consistency
Payment pages may mention JazzCash, Easypaisa, SadaPay and Raast. The Privacy Policy explains the related record keeping, including references, timing logs and withdrawal check records.
Support policy fit
Support pages explain how to contact us. The Privacy Policy adds how chat transcripts, email messages and identity checks may be stored when privacy or account access is discussed.
Security wording link
Security statements focus on access protection. The Privacy Policy adds what login, device and risk records may be collected to protect your account from unauthorised use.
Promo data limits
If you check a promotion, related account activity may be recorded. The Privacy Policy explains that such records are used for eligibility checks, support and dispute handling.
Retention alignment
Retention wording is kept consistent across legal pages. We keep records only as needed for account operation, legal duties, payment disputes, security checks and privacy request handling.
VISIBLE SAFEGUARDS
Policy Layout Markers You Can See
We design the Privacy Policy page so you can scan the parts that affect your account before you continue. Each section is labelled around data use, payment records...
Clear privacy badges
The hero badges summarise account data, Pakistan payment context, security...
Plain section labels
Each policy section has a short label rather than legal...
Local payment chips
JazzCash, Easypaisa, SadaPay and Raast appear as context chips where...
Rights wording blocks
Access, correction and deletion requests are kept close to contact...
Security callouts
Security callouts explain login records, device signals and session checks...
Change date placement
The policy date sits where you can find it quickly...
Privacy Policy Questions Answered
We may collect your name, contact details, login records, device signals, payment references and support messages. Each category is tied to account access, security checks, payments, service help or legal duties.
We keep transaction references, timing records and account links needed to match JazzCash or Easypaisa activity to your fh4 account. We avoid storing extra payment data when a reference is enough.
Yes, you can contact us to request access where local law permits. We verify account ownership first, then explain what data can be shared and how it will be delivered.
We share limited data only when needed for hosting, payment processing, fraud checks, support handling, legal duties or dispute resolution. We do not sell your personal data to outside advertisers.
Retention depends on the record type. Account, payment, security and support records may be kept while needed for service operation, dispute handling, legal duties and privacy request tracking.
We use access controls, session checks and limited staff permissions around login and device records. Those records help us detect unauthorised access and keep privacy checks linked to your account.