LEGAL REFERENCE

Privacy Policy for your pk3 account

pk3 keeps your account data, identity checks, device records and transaction references under one clear Privacy Policy, so you know what we collect before you open your account...

Pakistan privacy termsJazzCash record contextEasypaisa account checksRaast reference care
pk3 Privacy Policy for your pk3 account

How we handle privacy records

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

PRIVACY HELP

Ways to contact us

Privacy questions need a secure path, not a public comment thread. Use the contact route linked to your pk3 account so we can confirm the request belongs to you. We may ask for extra proof before changing records or sending a copy.

Team online

Email privacy desk

For privacy requests, email us from the address on your pk3 account. We match your message to account records before sharing any data or changing contact details securely.

Account message centre

When you are signed in, use the account message centre for faster matching. It lets us connect your privacy request with your login record and support history.

Document follow-up

If your request involves identity files, wallet references or withdrawal checks, we may ask for a clear document image before we update, correct or release records.

CARE SIGNALS

How this policy stays current

We treat privacy text as an operating commitment, not a page that sits untouched. pk3 checks this policy when account flows, security tools, wallet reconciliation or support channels change. Updates are written...

Plain wording

We avoid vague legal wording where a simple phrase works. Each privacy section names the account record, security reason or service partner purpose behind the collection.

Local payment context

JazzCash, Easypaisa, SadaPay and Raast records are mentioned only as account reference data. We explain why those references may be stored and matched.

Access checks

Login records, device signals and password reset events help us spot account access issues. We use those records to protect your account and investigate reports.

Retention choices

We keep records for as long as account, legal, tax, dispute or security purposes require. When a record is no longer needed, we remove or anonymise it.

Partner limits

Service providers receive only the data needed for their assigned task, such as verification, hosting, fraud checks, analytics safety or customer care handling.

Change tracking

When we update this Privacy Policy, we adjust the date and refresh the relevant section. Material changes are written so you can understand the effect.

POLICY MATCH

How related pages connect

pk3 keeps privacy wording consistent across related legal pages, so your account data is not described one way here and another way elsewhere. This page explains personal data handling, while linked pages...

01

Privacy Policy

This page explains personal data collection, use, sharing, storage and your contact choices. It is the main place to understand how pk3 handles account records.

02

Cookie terms

Cookie text covers browser storage, session tools and analytics signals. It supports this policy by explaining how site activity data is created and managed.

03

Account terms

Account terms explain rules for access, identity checks and account status. The Privacy Policy explains what data those processes may create or require.

04

Security wording

Security sections describe password controls, device checks and suspicious access handling. This page explains the related records we may store while protecting your account.

05

Payment records

Payment wording covers transaction handling through supported Pakistan rails. This policy explains how references, wallet names and reconciliation records may be processed.

06

Support records

Support pages explain how to reach us. This Privacy Policy explains how your messages, attachments and case history may be stored during account assistance.

07

Change statements

When related pages change, we check whether this policy also needs an update. That keeps data handling language aligned across the pk3 site.

VISIBLE CUES

Privacy cues you can see

We place privacy cues where they help you make account decisions. The policy layout highlights what data is collected, why it is used, how long it may stay...

Clear date label The policy date shows when this wording last changed. If...
Data category blocks We separate contact data, identity records, device signals, transaction references...
Purpose labels Each data use is tied to a purpose, such as...
Sharing limits Where partners are involved, we state the kind of task...
Rights contact The contact path is shown near privacy rights wording. That...
Security reminders Account safety cues explain why login records and device checks...

Privacy Policy questions answered

We may collect your name, mobile number, email address, password data, device signals and location region. If checks are needed, we may also request identity documents or wallet references.

We keep transaction references to match your account with payment activity, answer disputes and support withdrawal checks. These records help us confirm that a request belongs to your account.

Yes. Contact us through the email or account message route linked to your pk3 account. We may verify your identity before sending a copy or explaining any limits.

Retention depends on the record type and purpose. We keep data while your account is active, then for legal, tax, dispute, fraud prevention or security needs where required.

We share limited data with partners that help run verification, hosting, analytics safety, security checks, payment reconciliation or support. Each partner receives only what is needed for that task.

Send a request from your registered email or account message centre. We will check the request, ask for proof if needed and update records once ownership is confirmed.