Terms page link
Account rules and privacy handling are connected, but not the same. When the terms mention verification or misuse checks, this policy explains the data involved in those checks.
97pk keeps one privacy policy for account details, login checks, game-session records, support messages, and payment references. Before you open an account, you can see how we collect...
This privacy policy explains how 97pk handles personal data connected with your account, device, session activity, verification steps, and support contact. We may process your name, mobile number, login signals, payment references, and messages you send us so we can run your account, respond to privacy requests, check access where local law permits, and protect the service from misuse. Pakistani payment names
may appear in records only as transaction context, such as a reference tied to JazzCash, Easypaisa, SadaPay, or Raast. We do not sell your personal data. Access to records is limited to staff and service partners who need it for account operation, security, payment tracing, or legal handling. Retention periods depend on account status, dispute needs, technical logs, and duties that apply
in supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy requests work better when you contact us through the same account details you use on 97pk. That lets our team match your request to the correct profile without exposing records to another person. You can ask about access, correction, retention, or deletion, and we may request extra checks before sharing any account-linked data.
Use your registered email when asking for a copy, correction, or deletion of account data. We match the request against existing records before any personal detail is discussed or released.
Chat can receive privacy requests and pass them to the right team. If the request concerns sensitive account records, we move it to a checked channel before sharing a response.
For JazzCash, Easypaisa, SadaPay, or Raast privacy queries, send the reference and date only. Do not share wallet passwords or private banking codes with our support team.
We write this policy from the way our account flow actually works. Privacy wording is checked against registration screens, login tools, payment reference handling, live chat scripts, and back-office access roles. When...
Only staff who need account or payment records for a defined task can access them. Internal permissions are separated across support, verification, finance handling, and technical checks.
We collect device and browser signals to help protect your account, spot unusual access, and keep session records accurate. These checks support account safety without asking for extra documents each time.
Wallet and transfer names such as JazzCash, Easypaisa, SadaPay, and Raast are stored as transaction context. We keep references needed for tracing, disputes, and account balance checks.
Messages you send to support may be kept with your account record. This helps us respond consistently, trace privacy requests, and avoid asking you to repeat sensitive details.
When we change how account data is collected or used, we update the policy wording and date. Material changes are written plainly so you can compare what changed.
Service partners may process limited data for hosting, payments, security, or messaging. We require them to use the data only for the purpose connected with your 97pk account.
Our privacy policy sits beside other legal pages, but it has a separate job. Terms explain account rules, cookie wording explains browser storage, and this page explains personal data handling. We keep...
Account rules and privacy handling are connected, but not the same. When the terms mention verification or misuse checks, this policy explains the data involved in those checks.
Cookie text covers browser storage, analytics tags, and session tools. This privacy policy adds how those signals may connect with your account, device, and security records.
Support scripts are kept in line with the privacy policy. When you ask about account data, the team follows the same categories and verification steps described here.
Payment pages may mention JazzCash, Easypaisa, SadaPay, and Raast for account funding context. This policy explains what reference data may be retained and why.
Security text explains account protection measures, while this policy explains related data processing. Login logs, device checks, and alerts are treated as privacy-relevant records.
Profile screens ask for details needed to run your account. The privacy policy explains how those details are used, corrected, retained, or removed when eligible.
If another legal page changes a data-related process, we check this policy too. That keeps the privacy wording matched to the current account journey.
You should not need to search the whole site to understand privacy handling. We place clear cues near account forms, support routes, verification steps, and legal...
Account forms label required fields so you can see which data is needed to create and maintain your profile. Optional fields are separated from details we need for account operation.
The privacy policy link remains available from the footer so you can return to it before or after opening your account. We keep the label plain and easy to spot.
When extra checks are needed, the prompt explains what we require and why. We avoid asking for unrelated documents and keep request wording tied to the account issue.
If your login pattern changes, we may show an alert or ask for confirmation. These prompts are part of our privacy and security approach for account access.
Support reminders tell you not to share passwords, wallet PINs, or private banking codes. Privacy protection depends on both our controls and careful sharing from your side.
The policy date helps you see whether wording has changed. If you return later, check the date before sending new personal data through the account area.