LEGAL REFERENCE

Privacy Policy for your pk1 account

Open your pk1 account and we explain, in this Privacy Policy, what data we collect, why we need it, and how we protect it. The policy covers account...

Account dataCookie controlsPayment recordsSupport privacy
pk1 Privacy Policy for your pk1 account

How we handle your account data

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

CONTACT ROUTES

How to contact us on privacy

If you want to ask about your data, correct account details, or raise a privacy concern, contact us through the channel connected to your pk1 account. We may ask for verification before discussing records, so your request is handled by the right team and not exposed to another person.

Team online

Account help desk

Use the support area inside your account for privacy requests tied to your profile, wallet records, device history, or login activity. This lets us confirm ownership before discussing sensitive data.

Email privacy mailbox

Email us from the address linked to your pk1 account and include the request type, such as correction, copy request, cookie query, or deletion question. Avoid sending wallet PINs or passwords.

Chat handover

Live chat can record your privacy concern and pass it to our account team. The chat transcript is stored with your case so we can track the answer and avoid repeating verification.

POLICY CHECKS

How our policy stays accurate

We maintain this Privacy Policy as an operating document, not a static legal page. When payment flows, account checks, cookie tools, or support systems change, our internal teams check whether the policy...

Operations input

Our account, wallet, and support teams provide practical input because they handle verification, transaction references, and case logs every day. That helps the policy describe real pk1 processes rather than abstract wording.

Security checks

We map policy wording against password resets, login alerts, device tracking, and fraud screening. If a control changes, we check whether the privacy explanation still reflects the account flow you experience.

Payment record mapping

JazzCash, Easypaisa, SadaPay, and Raast references are treated as payment records, not marketing labels. We explain why those references are stored and who may need them for reconciliation.

Cookie wording

We check cookie text against the actual browser tools used on pk1. That includes session cookies, preference storage, security cookies, and analytics signals that help us keep the site stable.

Support case audit

Privacy requests are sampled for process quality, response clarity, and secure handling. We look for missed verification steps, unclear answers, or records that need better internal tagging.

Change logging

When we update the policy, we record the reason internally, such as a new support workflow or a change in retention practice. This keeps future edits tied to operational decisions.

How our policy pages stay aligned

Your privacy expectations should not change from one pk1 legal page to another. We align this Privacy Policy with our cookie, account, bonus, and terms pages so wording...

Cookie pageThe cookie page explains browser storage in more detail, while this Privacy Policy explains why cookie data connects to account security, preferences, analytics, and session continuity during your pk1 activity.
Terms pageThe terms page covers account rules, while this policy explains the data behind those rules, including identity checks, login records, wallet references, dispute handling, and communication history.
Promotions pageWhen you check current offers, pk1 may record eligibility signals, redemption status, and related account activity. This policy explains how those records are handled and why they may be retained.
Payments pageThe wallet page describes cash-in and withdrawal flow, while this policy focuses on personal data, transaction references, verification evidence, and support records tied to JazzCash, Easypaisa, SadaPay, and Raast.
Security pageSecurity wording covers controls such as device checks and login alerts. This Privacy Policy explains the personal data those controls generate and how long related records may be kept.
Support pageSupport content explains how to reach us, while this policy explains what happens to chat transcripts, email records, case tags, attachments, and verification steps after you contact pk1.
Account pageAccount wording explains how you manage your profile. This policy explains which profile fields we store, which fields you can update, and when we must keep records for legal or security needs.
LAYOUT MARKERS

Privacy layout you can scan

We structure this Privacy Policy so you can find the data topic you need without reading every clause at once. The layout separates collection, use, sharing, retention, security...

Plain headings Each privacy topic uses direct headings so you can move...
Local examples Pakistan payment examples are included where they explain real data...
Short privacy badges The opening badges summarise the main data areas covered by...
Request cues Contact prompts appear near privacy topics that may lead to...
Security context Security references sit beside the data they protect, including login...
Update visibility When the policy changes, the revised wording appears on this...

Privacy questions before you join

We collect the details needed to create and protect your account, such as contact details, login records, device signals, preference choices, and verification records where required for access in supported regions.

We keep payment references so wallet activity can be reconciled, support can investigate queries, and security checks can spot unusual activity. This may include JazzCash, Easypaisa, SadaPay, or Raast records.

We share data only where needed for hosting, verification, security screening, payment processing, support tools, legal duties, or dispute handling. Partners must handle the data for the assigned service.

Contact us through your account or email from your registered address. We may verify you first, then correct eligible fields or explain why certain records must remain unchanged.

Retention depends on the record type. Support chats, wallet references, verification evidence, security logs, and tax or dispute records may be kept for different periods under operational or legal needs.

You can manage browser settings and any cookie controls we provide. Some cookies are needed for login, security, and session continuity, while others help us measure site performance.