Privacy Policy
This page holds the complete data rules. It names what we collect, why we keep it and how to ask for access, while shorter pages link back instead of restating the wording.
This page explains how pk67 app handles the data you share when you open an account, verify a wallet through JazzCash, Easypaisa, SadaPay or Raast, and move through...
Our privacy commitments follow you wherever pk67 app is used, yet some parts move with local law. Where local law permits, account records sit on secured servers, and wallet references from JazzCash, Easypaisa, SadaPay and Raast stay only as long as a transaction, tax or dispute rule requires. If a supported region sets a stricter retention or consent standard, that standard wins
for accounts opened there. You can ask us to correct your name, contact number or payout wallet at any time. Disagreements about data handling go to the courts and regulators governing your account region, not to one global authority. Any change to this policy appears on this page before it takes effect.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We apply the same data rules whether you sign in from Karachi, Lahore or Peshawar. Identity checks, encryption and staff access controls sit behind every account, and wallet references never rest in...
Traffic between your device and pk67 app travels over encrypted connections. Login sessions expire on their own, and we ask for a fresh sign-in after a password change.
Before your first withdrawal clears, we match the account name with the wallet owner. That step keeps JazzCash, Easypaisa, SadaPay and Raast payouts attached to the right person.
Only staff with a documented reason can open account records, and each lookup writes an audit entry. Sensitive fields stay masked even for teams handling routine queries.
Transaction records stay for the period your region's tax and dispute rules require, then we delete or anonymise them. Long-inactive profiles close under the same schedule.
Saved wallet numbers display partly hidden. The full number is readable only during a payout check and never appears in emails, chat transcripts or exported statements.
Every edit to this policy carries a date and a short summary. You can request the earlier wording at any time to see which version applied when you registered.
Our policy pages share one voice and one set of definitions, so a term carries the same meaning wherever you read it. When a page needs a narrower rule, we state it...
This page holds the complete data rules. It names what we collect, why we keep it and how to ask for access, while shorter pages link back instead of restating the wording.
Account conduct and closure sit on the terms page. Data handling stays here, so the two pages never give you different answers about your records.
Cookie wording borrows the same definitions used here. When a cookie line changes, the date on both pages moves together, so you never read two versions.
Payout wording references the wallet details described here. Both pages treat JazzCash, Easypaisa, SadaPay and Raast references the same way, with identical masking language.
Security explains the safeguards; this page explains the records those safeguards protect. Where the two overlap, one short line points you to the fuller rule.
Verification steps you complete after registering appear on the account rules page. The data collected during that check is described here, with the same retention window.
Our contact channels match the ones named in the support section here. Data requests route to the privacy desk rather than general support, so nothing is misdirected.
This page is built to be read, not skimmed past. Short summaries sit above the longer clauses, the last-updated date sits near the opening, and every rule touching...