Privacy Policy
This page explains personal data collection, use, storage, sharing and request handling. It is the main source for how fh3 treats account and support data.
fh3 keeps your account privacy controls, JazzCash and Easypaisa transaction records, device signals and support contact handling in one clear policy for Pakistan. Read how we collect, use...
This Privacy Policy explains how fh3 handles personal data when you create an account, access the lobby where local law permits, contact support, use device security checks or connect Pakistani payment rails. We collect only the details needed to run your account, confirm access, process transactions, answer your requests and protect the service from misuse. Payment references from JazzCash, Easypaisa, SadaPay and
Raast may be stored with time stamps, account identifiers and status updates so your balance history can be checked. We do not sell your personal data. Where service partners help with hosting, security, payments or support tools, we require them to handle data only for the task assigned to them and to keep it protected.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you want to ask about this Privacy Policy, correct account details or request a copy of stored data, contact us through the routes below. We may ask for account verification before sharing privacy-related replies so your data is not released to another person.
Email [email protected] with your account email, mobile number and the privacy request you want us to handle. We reply after checking account ownership and the records connected to your request.
Use chat while signed in if your privacy question concerns a recent session, device alert or support transcript. Our team can tag the request for a privacy response after verification.
Open the account centre to update contact details, check security settings and see recent login activity. These tools help you keep privacy records accurate before you contact us.
We write this Privacy Policy from the systems we operate: account access, support handling, device checks and Pakistani payment references. When a process changes, the policy is checked against our live account...
We map each account field to a purpose, such as login, support, verification or transaction history. That mapping keeps the Privacy Policy tied to real fh3 account screens.
JazzCash, Easypaisa, SadaPay and Raast references are described by the data we receive, such as status, time and account link, not by unrelated payment claims.
Login times, device type and security flags are used to protect your account and investigate unusual access. The policy explains this without hiding it in broad wording.
When you contact us, conversation records may be kept so we can follow up, verify past answers and handle disputes. The policy states why those records exist.
Where hosting, security or payment partners process data for us, we limit their role to the service task. They are not allowed to reuse account data for separate aims.
Before policy wording changes, we compare it with current account flows, support tools and payment status handling. That reduces mismatch between the page and actual practice.
This Privacy Policy is written to work beside our terms, cookie policy and account notices without repeating them. Each page has a separate job, so you can see which rule explains data...
This page explains personal data collection, use, storage, sharing and request handling. It is the main source for how fh3 treats account and support data.
Our terms describe account rules and service use, while this Privacy Policy explains the data created by those account actions and how we handle it.
The cookie policy covers browser storage and device signals in more detail. This page connects those signals to account privacy and security purposes.
Support replies follow this page when handling data access, correction or deletion questions. That keeps privacy answers consistent across email and chat.
Payment-related privacy wording stays focused on references, status updates and verification records from Pakistani rails, instead of explaining unrelated cashier features.
Security sections explain why login records, device checks and suspicious activity flags may be kept. The same wording is reflected in account-centre prompts.
When we change privacy wording, we keep the page structure steady so you can compare sections more easily and spot where a data practice changed.
The Privacy Policy page is arranged so you can scan the data journey from account creation to support contact and transaction records. We keep headings direct...
The page starts with the data we collect, then explains use, sharing, storage and your request routes. That order follows the way your account data moves.
Pakistan-specific references appear where they matter, including JazzCash, Easypaisa, SadaPay and Raast records. This keeps the policy relevant to your account context.
Headings use direct language such as account data, support records and security logs. You should not need legal training to find the privacy answer you need.
Where a section mentions access, correction or deletion, we point you toward the right contact path. That helps you act on the policy, not just read it.
Device and login signals are grouped under security so you can see why we collect them. The policy separates these records from payment and support data.
When policy wording is updated, we keep the format familiar and adjust the affected sections. This makes future changes easier for you to read and compare.