LEGAL REFERENCE

Privacy Policy For Your pkr1 Account

pkr1 collects only the account, security and payment details needed to keep your Pakistan account working where local law permits. Read this Privacy Policy before you open an...

Account dataCookie choicesPayment recordsSupport privacy

Browse Lobby Read FAQ

How We Handle Your Data

Our Privacy Policy is written for pkr1 account holders in supported regions of Pakistan. We use your details to create and secure your account, check access, process withdrawals, keep payment records aligned with JazzCash, Easypaisa, SadaPay and Raast references, and answer privacy requests. We do not sell your personal data. We may share limited records with payment partners, security vendors, analytics tools

and legal advisers when needed to run the service, detect misuse, meet lawful requests, or protect your account. Where local law permits, you can ask us to access, correct, restrict or erase certain records, though finance and security logs may need to stay for legal or fraud-prevention reasons. This policy applies whenever you use pkr1 on mobile web, app-style browser access, or

any supported device.

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

PRIVACY HELP

Contact Paths For Privacy Requests

If you need help with your personal data, contact us from the same account you use on pkr1. That helps us confirm...

POLICY CHECKS

How We Keep This Policy Current

We write this policy from the operator side, using the records our team actually handles: account creation, login security, wallet references, withdrawal checks, cookie tools and support transcripts. When those flows change...

Operational Owners

Privacy text is checked by the teams that run account access, payment reconciliation and support. That keeps each clause tied to the records we handle rather than abstract legal wording.

Pakistan Context

We name local rails such as JazzCash, Easypaisa, SadaPay and Raast because these references appear in support and finance logs. The policy explains that context without exposing your wallet credentials.

Security Alignment

Login alerts, device signals and session records are covered because they help protect your account. We keep the policy aligned with these controls so you understand why technical data is collected.

Cookie Checks

Cookie wording is checked against the tools used on pkr1 pages. We separate essential session cookies from analytics tags so your choices are described in plain Pakistani English.

Change Records

Material policy changes are logged internally before they go live. If a change affects how we use personal data, we update the visible date and adjust the related section.

Support Training

Support agents are trained to avoid sharing private account details in open chat. They verify your account first, then handle privacy questions through safer channels when the request is sensitive.

Consistent Privacy Across Legal Pages

This Privacy Policy connects with our terms, cookie wording and account rules. Each page covers a different legal point, but we keep the same voice, definitions and account...

Terms Link

Our terms explain account rules, while this policy explains data use behind those rules. Where both pages mention verification, the privacy wording focuses on records, storage and sharing.

Cookie Page Fit

Cookie wording supports this policy by naming browser storage and tracking choices. The privacy page gives the broader reason for those tools: access security, performance checks and analytics.

KYC References

Identity checks appear across legal pages, but this policy explains what may be collected and why. We keep that wording separate from account conduct rules and promotion terms.

Payment Records

Finance clauses in other pages may mention wallet references. Here we explain the privacy side: matching JazzCash, Easypaisa, SadaPay and Raast records with your account activity.

Security Logs

Account security language stays consistent across pages. This policy adds privacy context for login timestamps, device type, IP checks and alert records used to protect access.

Support Records

Support rules explain how to contact us. This policy explains how chat transcripts, emails and attachments are stored, who can view them, and when they may be retained.

Change Notices

When legal pages change, we check related privacy wording at the same time. That keeps dates, definitions and account references aligned across the pkr1 site.

Policy Layout You Can Scan

We designed this Privacy Policy so you can find the exact data point you care about without reading legal blocks twice. The layout separates account records...

Plain Summary Blocks

Each policy area starts with a short summary before legal detail. That helps you understand the purpose of a data category, then decide whether to read the full clause.

Account Data Labels

Profile, verification, login and payment references are labelled separately. This keeps personal details distinct from technical records, so you know which part of the policy applies.

Local Rail Context

Where wallet names appear, they are used only to explain record matching and support checks. We do not ask for JazzCash, Easypaisa, SadaPay or Raast passwords.

Retention Cues

Retention wording explains why some records are kept after closure requests. Finance, fraud-prevention and legal records can follow different timelines from marketing preferences or simple profile edits.

Choice Markers

Where you have a practical choice, the policy marks it clearly. Cookie settings, communication preferences and correction requests are separated from records needed to run the account.

Request Steps

Privacy request steps are written in the order our support team follows. You can see what to send, how we verify you, and when extra documents may be needed.

Privacy Policy Questions From You

We collect details needed to run your account, such as name, contact details, login records, device signals, wallet references and support messages. Identity documents may be requested when verification is required.

Payment references help us match account activity with JazzCash, Easypaisa, SadaPay and Raast records. They also support withdrawal checks, dispute handling, fraud-prevention work and accounting duties where local law permits.

No, we do not sell your personal data. Limited records may be shared with payment partners, security vendors, analytics providers or advisers when needed to operate, protect or comply with lawful requests.

Contact support from your pkr1 account and describe the detail that needs correction. We may ask for proof before changing records, especially when the request affects identity, phone or payment details.

Cookies help keep you signed in, remember basic preferences, protect sessions and measure page performance. Some cookies are essential for account access, while optional analytics tags depend on your available choices.

You can ask us to erase eligible records. Some finance, security and legal logs may need to remain for required periods, and we will explain the reason if full deletion is not possible.

Support conversations are linked to your account and viewed only by staff who need them for service or privacy handling. Sensitive requests may be moved from chat to email for safer verification.