LEGAL REFERENCE

Privacy Policy for Your Account

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...

Account data scopePakistan access contextPayment reference careSupport record handling
97pk Privacy Policy for Your Account

How Our Policy Applies Locally

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

CONTACT PATHS

Reach Us About Privacy

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.

Team online

Account email

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.

Live chat handoff

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.

Payment query route

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.

POLICY CHECKS

How We Keep This Policy Clear

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...

Role-based access

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.

Device signals

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.

Payment references

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.

Support transcripts

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.

Policy updates

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.

Partner controls

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.

PAGE ALIGNMENT

How This Policy Stays Aligned

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...

01

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.

02

Cookie wording

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.

03

Support wording

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.

04

Payment wording

Payment pages may mention JazzCash, Easypaisa, SadaPay, and Raast for account funding context. This policy explains what reference data may be retained and why.

05

Security wording

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.

06

Profile wording

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.

07

Change wording

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.

Visible Privacy Cues Across 97pk

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...

Form labels

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.

Legal footer

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.

Verification prompts

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.

Session alerts

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.

Chat reminders

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.

Policy date

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.

Privacy Questions Before You Join

We may collect your name, mobile number, email, login signals, device data, support messages, and account activity. Payment references may also be stored when linked to JazzCash, Easypaisa, SadaPay, or Raast.

Device data helps us recognise your login, maintain session security, and detect unusual account access. It can include browser type, IP signals, device identifiers, and timing records connected with your account.

No. We do not sell your personal data. Limited sharing may occur with service partners for hosting, security, support handling, payment tracing, or legal duties linked to your account.

We store payment names and references only as account transaction context. We do not need your wallet password, private PIN, or banking login, and our support team should never ask for them.

Yes. Contact us from your registered channel and tell us which detail appears wrong. We may verify your identity before changing personal data tied to account access or payment records.

Retention depends on account status, support history, dispute needs, security logs, and applicable duties in supported regions. We keep data only for purposes connected with your account and service operation.

You can request deletion through support. Some records may need to stay for security, payment tracing, dispute handling, or legal reasons, and we will explain the outcome after checking your account.