LEGAL REFERENCE

Privacy Policy for your ps games account

ps games keeps your account data, device signals, cookie choices and transaction records under one clear Privacy Policy, so you know what we collect before you open an...

Account dataCookie choicesSupport recordsPakistan context
ps games Privacy Policy for your ps games account

How our Privacy Policy works

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

CONTACT PATHS

Privacy questions and account help

When your privacy request needs human handling, we route it through support so the right team can check your account safely. We...

Live chat privacy help Use live chat for quick privacy questions about...
Email data requests Send privacy access, correction or erasure requests by...
Account security checks If you see a login you do not...
POLICY CARE

How we keep policy wording reliable

We write this Privacy Policy from the way ps games operates, not from generic wording. Product, support and security teams feed practical changes into the policy when account...

Service mapping

We map account creation, wallet checks, lobby access and support contact points before updating policy text, so each data category...

Security input

Our security team explains which logs are needed for access protection, suspicious session checks and account recovery. That input shapes...

Local rail context

We separate cardless Pakistani rail references from gameplay records. JazzCash, Easypaisa, SadaPay and Raast transaction IDs are handled as account...

Cookie clarity

Cookie wording is checked against the live site controls, including preference cookies, session cookies and analytics tags. If the control...

Support training

Support agents receive privacy handling scripts for access requests, correction requests and account security questions. They are told when to...

Retention checks

Retention wording is aligned with security, dispute handling and local transaction duties. We keep records only for active purposes, required...

How this policy connects with other pages

Your privacy rights do not sit apart from the rest of ps games. This page works with our terms, cookie wording, account rules and support flows, but it...

Terms linkOur terms describe account rules and service access. This Privacy Policy explains the personal data used to apply those rules, such as identity checks, login records and support messages.
Cookie page alignmentCookie wording describes browser storage in practical terms. This page explains why those cookies matter for sessions, preferences, analytics and security across your ps games account.
Account closure flowWhen you ask to close an account, privacy handling still applies. We assess which records can be erased, which must remain, and which are kept for security or transaction checks.
Wallet record linkLocal rail references are used to trace cash-in and payout requests. The privacy policy explains how those references are stored, limited and shared with processing partners.
Support transcript useSupport pages explain how to reach us. This policy explains how chat logs, email threads and uploaded proof are handled when your request involves privacy or account access.
Security page fitSecurity wording covers password habits and access protection. This page adds the privacy angle by naming login logs, device markers and alerts used to protect your account.
Promo board privacyIf you check the promo board, we may use account eligibility data. This policy explains that eligibility is calculated inside your account and is not turned into public profile data.

Privacy layout cues across ps games

We keep privacy cues visible where they matter: account forms, cookie controls, support prompts and wallet screens. Short labels explain why data is requested before you...

Form labels

Account forms use short prompts beside fields such as mobile number, email and password. These prompts explain why the detail is needed before you continue with ps games.

Cookie panel

The cookie panel separates essential session cookies from preference and analytics choices. You can adjust allowed categories, and this policy explains what each category supports.

Wallet prompts

When a local rail reference is needed, the wallet screen asks only for details tied to reconciliation, account matching or payout checks. Extra personal data is not requested there.

Security alerts

Login alerts may show device, time and location signals. The policy explains that these signals are used for account protection and support checks when you raise a concern.

Help centre wording

Privacy prompts in support ask you not to share passwords or unrelated documents. If proof is needed, we request the narrow record needed to handle your case.

Preference access

Where account settings include communication choices, we describe how those choices affect service messages, promo updates and account alerts without changing required security notices.

Privacy Policy questions for ps games

We collect account details you provide, such as name, mobile number, email, login credentials and verification records. We also collect device, session and security data needed to operate your account safely.

We share only the records needed to process, trace or verify JazzCash, Easypaisa, SadaPay and Raast transactions. Partners receive limited data for that task and cannot use it for unrelated purposes.

Cookies keep your session active, remember preference choices, measure site performance and support fraud checks. You can manage non-essential categories through the cookie panel where controls are available.

Yes. Contact support from your registered email or logged-in chat and tell us what needs correction. We may verify your identity before changing records tied to security or transaction history.

We keep records for as long as needed for account service, security checks, transaction handling, dispute response and legal duties. When records are no longer needed, we delete or anonymise them.

We log your request, confirm account matching details, then route it to the right team. Complex access, correction or erasure requests may take longer because we check eligibility carefully.