LEGAL REFERENCE

How 4v4 handles your data

4v4 keeps your privacy choices, account records and transaction data in one clear policy for Pakistan access where local law permits. Before you open an account, read how...

Pakistan account dataJazzCash contextEasypaisa contextRaast records
4v4 How 4v4 handles your data

What this Privacy Policy covers

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

CONTACT ROUTES

How to reach us on privacy

If you want to ask about your data, update account details or question how a record is used, contact us through the...

Account chat Use account chat for privacy questions tied to...
Email request Send privacy requests by email when you need...
Verification step Before we correct, export or restrict a record...
DATA CHECKS

How we keep the policy current

We maintain this Privacy Policy as an operating document, not a static page. When 4v4 changes a wallet flow, identity check, support tool or security process, we check...

Local wording

We write privacy wording for Pakistan account flows, including JazzCash, Easypaisa, SadaPay and Raast records, so the policy matches the...

Access logs

Login time, device type, IP signals and session events are recorded to protect your account, investigate suspicious access and keep...

KYC handling

Identity documents are used for verification, withdrawal checks and account safety. We limit internal access to trained staff and keep...

Transaction records

Wallet records help confirm requests through Pakistani rails, reconcile balances and answer account queries. We keep the financial trail separate...

Partner control

Service partners may process hosting, messaging, fraud checks or payments for us. Their access is limited by role, contract and...

Change log

When policy wording changes in a meaningful way, we update the page date and adjust affected sections. You can return...

PAGE ALIGNMENT

How this policy stays consistent

Our Privacy Policy connects with other legal pages without repeating every rule. The account terms explain your service relationship; this page explains the data used to run that relationship. Cookie wording covers...

01

Account terms

Terms set out account rules, while this policy explains the data behind registration, login checks, security actions and support decisions linked to those account rules.

02

Cookie page

Cookie wording focuses on browser storage and analytics signals. This policy expands that view into account records, device activity, wallet checks and identity handling.

03

Wallet rules

Wallet wording explains how requests are processed. This policy explains the related data, including transaction IDs, verification status, rail names and support notes.

04

Promo preferences

Preference settings control how we contact you. This policy explains the contact data used, how choices are recorded and how changes apply to future messages.

05

Security policy

Security wording describes protective measures. This policy explains the personal data connected to those measures, such as login signals, device checks and access history.

06

Support records

Support pages show how to reach us. This policy explains how chat transcripts, emails and verification answers are stored, searched and used to resolve requests.

07

Regional access

Access may depend on supported regions and local law. This policy explains how location signals can be used for availability, security and compliance checks.

POLICY LAYOUT

What you can scan quickly

We designed this Privacy Policy so you can find the parts that matter before sharing data with 4v4. The layout separates collection, use, sharing, retention, security and your...

Clear sections Each policy area has its own block, so you can...
Local chips Pakistan rail chips appear as context markers only. They show...
Plain wording We avoid dense legal phrasing where a simpler sentence works...
Request paths Contact routes are placed near the policy explanation, so you...
Retention cues Retention wording explains that records are kept for operational, legal...
Security markers Security markers identify where encryption, access control and monitoring relate...

Privacy Policy questions for 4v4

We collect account details such as your name, phone number, login credentials, region signals and verification status. We also create records when you access your account, contact support or use wallet features.

Identity data helps us confirm that the account belongs to you, process withdrawal checks, prevent misuse and respond to account disputes. Access is limited to staff who need it for those tasks.

Records linked to JazzCash and Easypaisa are used to reconcile wallet activity, confirm requests and answer support questions. We treat those records as account data and restrict sharing to required processing partners.

Yes. Contact support from your account or email us with the relevant detail. We verify your identity first, then correct records where the change is valid and technically possible.

We share limited data with partners that support hosting, payments, fraud checks, analytics, messaging or customer care. Each partner receives only what is needed for the assigned service.

Retention depends on the record type and the reason it is held. We keep data for account operation, legal duties, fraud prevention and dispute handling, then reduce or delete it when appropriate.

Use account chat for faster routing or email us for a written request. Include your registered phone number and the request topic so we can verify you and respond accurately.