How pk997 protects your data
pk997 keeps your account, device, payment and support data under a clear Privacy Policy for Pakistan access where local law permits. Read this page before you open your...
Privacy terms for Pakistan accounts
This Privacy Policy explains how pk997 handles personal data when you create an account, enter the lobby, contact support, or use Pakistan payment rails in supported regions. We collect only the data needed to run your account flow, verify access, secure sessions, process payment references, answer privacy requests, and keep required transaction records. We may hold account identifiers, contact details, device signals,
IP logs, support messages, payment references and verification records. We do not sell your personal data. Where we use service partners, we share only what is needed for hosting, fraud checks, payment routing, support handling, analytics and legal record keeping. You can contact us to ask about access, correction or deletion where applicable.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep the policy reliable
Our Privacy Policy is written around how pk997 actually handles account and session data. We align the wording with our account screens, payment checks, support workflow and security...
Account mapping
We connect each privacy clause to a real account step, such as email setup, phone checks, sign-in records and profile...
Security logging
We explain device, IP and session logs because those signals help us detect account misuse. Access to those logs is...
Payment references
We describe JazzCash, Easypaisa, SadaPay and Raast references as transaction records, not wallet access. pk997 records confirmation details needed for...
Support records
Messages to support may be stored with your account so we can answer follow-ups. We avoid asking for secret codes...
Partner checks
Hosting, analytics, payment routing and fraud screening partners may process limited data for pk997. We choose the minimum data route...
Policy updates
When our data handling changes, we update this page and keep the current version visible. Material privacy changes may also...
How this policy fits our terms
The Privacy Policy works beside other pk997 legal pages, but it has its own job: explaining personal data handling. If another page sets account rules or cookie choices...
Privacy layout you can scan
We designed this Privacy Policy so you can move from plain meanings to specific rights without digging through legal clutter. Each block focuses on one data...
Plain purpose labels
Every major data use is labelled by purpose, such as account access, payment matching or security checks. That helps you see why pk997 asks for each detail.
Local rail context
Pakistan payment names appear only where they affect privacy, such as transaction references and support checks. The policy does not ask for wallet secrets or private PINs.
Account request path
The page shows how to ask about access, correction or deletion where applicable. We may need identity confirmation before changing or sharing account-linked personal data.
Retention cues
We explain why some records must remain for security, dispute handling or legal reasons. Other data may be removed or anonymised when it is no longer needed.
Sharing boundaries
Partner sharing is described by function, not hidden behind vague wording. Hosting, analytics, payment routing and fraud checks receive only data needed for that task.
Update signals
The policy date and change language help you spot updates. If a privacy change matters to your account, we may also flag it after sign-in.