Terms link
Our Terms page explains account use, while this Privacy Policy explains the records connected with that use, including registration details, activity logs and verification checks.
LEGAL REFERENCE
Privacy Policy for your pkr22 account
pkr22 explains what account, device and transaction data we collect, why we use it, and how you can contact us about your privacy choices. Open your account with...
Pakistan privacy contextAccount data explainedJazzCash and Easypaisa recordsSecurity checks included
How we handle your data
This Privacy Policy explains how pkr22 collects and uses details linked to your account where local law permits. We may process your name, contact details, login activity, device signals, transaction references and support messages so your account can be created, secured, verified and maintained. We also use limited technical data to detect unusual access, prevent misuse, respond to privacy requests and keep
records required for account administration. When you use Pakistani rails, payment references may be matched against your pkr22 wallet history, but we do not ask for your banking password or mobile wallet PIN. Access to personal records is limited to staff who need it for account, security or service tasks.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CHECKED WORDING
How this policy stays accurate
We keep this page tied to the way pkr22 actually collects and handles records. Policy text is checked when account flows, payment rails, support routing or security checks change. That helps you...
Account-flow checks
We compare policy wording with registration, login and wallet screens so the data categories described here match the details we actually request from you.
Payment record mapping
JazzCash, Easypaisa, SadaPay and Raast references are described as account records, not banking access. We only need enough detail to reconcile your pkr22 wallet history.
Security language
Login alerts, device signals and verification checks are explained in plain words so you can see why we process them and how they protect account access.
Support alignment
Our support scripts point privacy requests toward secure channels, keeping account records away from public replies, social comments or unverified message threads.
Change tracking
When privacy wording changes, we update the page date and keep the new text focused on account data, service records and your request paths.
Pakistan context
The policy refers to supported regions and local payment rails so your privacy expectations match how pkr22 operates for Pakistan account access.
POLICY MATCH
Policy alignment across pkr22 pages
Privacy wording should connect cleanly with our other legal pages. We keep this page focused on personal records, while account terms explain service rules and cookie text explains browser storage. The split...
Cookie text
Cookie wording covers browser storage and session tools. This page connects those signals to privacy purposes such as login continuity, fraud detection and account security.
Wallet records
Payment references appear here only as personal account records. Wallet rules may explain processing steps, but privacy wording explains how those references are stored and accessed.
Support records
Support pages explain how to contact us. This page explains how messages, attachments and identity checks are handled when the contact involves personal account data.
Security sections
Security content may describe access controls. The Privacy Policy explains which device signals, login records and verification results may be processed for that purpose.
Promo board links
If promotional pages collect preferences or account responses, this policy explains how those records connect to your profile and how you can ask about them.
Regional wording
Where access is described for supported regions, privacy wording stays tied to Pakistan account handling, local rails and requests made through pkr22 channels.
PAGE MARKERS
Visible privacy markers on this page
This page is arranged so you can scan privacy duties before creating or managing your account. The markers below show where we explain collection, use, storage, sharing, security...
Collection marker
This marker identifies the account details we may collect, including...
Purpose marker
Purpose wording explains why each data category is used, such...
Storage marker
Storage wording tells you that records are kept only for...
Sharing marker
Sharing text explains when processors may handle records for hosting...
Security marker
Security wording covers access controls, verification steps and monitoring signals...
Request marker
Request wording shows how to ask about access, correction or...
Privacy questions before you join
We collect details needed to create, secure and manage your account, including contact fields, login records, device signals, payment references and support messages you send to us.
JazzCash, Easypaisa, SadaPay and Raast references help us match wallet activity with your account history. We use transaction IDs, not your banking password or wallet PIN.
Yes. Send a request through the privacy route in your account. We may verify your identity first, then correct eligible records linked to your pkr22 profile.
We may use processors for hosting, analytics, support tools, security checks and payment reconciliation. They receive only the records needed to perform the assigned service.
We use access controls, verification steps, monitored login signals and role-based staff permissions. These controls reduce unauthorised access and keep sensitive records separated.
We keep records for account service, security, dispute handling and legal administration needs. When a record is no longer required, we delete or anonymise it where practical.