Privacy Policy For Your p99gam Account
This Privacy Policy explains how p99gam collects, uses, stores and protects personal data when you open an account or contact our team from Pakistan. It also sets out...
How p99gam Handles Personal Data
We collect details needed to create and maintain your p99gam account, including your name, contact details, login credentials, location signals, device identifiers and activity connected with account access. When you use JazzCash, Easypaisa, SadaPay or Raast, we receive transaction references and status data required to match account movements, investigate errors and meet applicable legal duties; we do not need your full wallet
password. We use data to provide account access, detect suspicious activity, answer support requests, maintain technical records and improve page performance. Some records may be shared with payment processors, hosting partners, security services or authorities when legally required. We retain information for as long as needed for these purposes, then delete or anonymise it under our retention controls. You may ask about
access, correction or deletion, subject to legal and operational limits. Access is provided only in supported regions and where local law permits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Paths For Data Requests
Our privacy support paths are designed to keep requests focused and traceable. Tell us which account or record your message concerns, use the email connected with your account where possible, and avoid sending wallet passwords or one-time codes. We may request reasonable verification before discussing personal data, helping us protect your account while responding clearly.
Privacy email
Send a data access, correction or deletion request through the privacy contact shown on p99gam. Include your registered email and a short description so we can route the matter correctly.
Account chat
Use the signed-in support chat for account-specific privacy questions. The conversation stays linked to your account record, allowing our team to check the relevant access or security event.
Security escalation
If you suspect unauthorised account access, contact support promptly and change your password through the account controls. Do not send a password, wallet PIN or verification code in chat.
Practical Signals Behind This Policy
This policy reflects the way our account systems operate in practice. We separate identity details from routine technical logs where feasible, restrict staff access by role, and record important account actions for...
Access controls
p99gam limits internal access to personal records according to work needs. Authentication checks, role permissions and activity logging help us identify unusual access and maintain a traceable account history.
Device signals
Browser type, device identifiers, approximate location and session events can help us recognise repeat access, prevent misuse and diagnose display problems. These signals are handled for security and service operation.
Payment references
JazzCash, Easypaisa, SadaPay and Raast activity may produce reference numbers, amounts and status results. We use these records to match account events, while wallet credentials remain outside our request.
Access verification
Before releasing account data or changing sensitive details, our team may compare account identifiers and recent activity. This step reduces the chance that a third party receives your private records.
Retention controls
We keep records for service, security, dispute handling and legal duties only as long as those purposes require. Afterward, data is removed or changed so it no longer identifies you where feasible.
Regional handling
Access depends on supported regions and applicable local rules. Where processing partners operate in another jurisdiction, we use contractual and technical safeguards suited to the data involved.
How This Policy Connects With Account Rules
Privacy terms work alongside the account, payment and security pages, but this page remains focused on personal data. Each related page may explain a different operational subject, while...
| Account terms | Account rules explain access conditions and permitted use. This policy adds the data angle, showing which personal details support account creation, authentication and ongoing account administration. |
|---|---|
| Wallet activity | Payment records can show a reference, value, status and timing. This policy explains why those details may be retained and how they help resolve a disputed or incomplete account movement. |
| Security controls | Security procedures protect the account from misuse. Privacy rules explain how related login events, device signals and verification records are used without expanding collection beyond operational needs. |
| Support contact | Support conversations may contain account details supplied by you. We use the conversation to resolve your request, restrict access internally and retain the record according to our service and legal needs. |
| Regional access | Availability can depend on local law and supported regions. The privacy commitments apply to data handled through p99gam, while access decisions may require location and eligibility checks. |
| Data choices | You can ask about access, correction or removal of personal data. Some requests may be limited where records are needed for security, dispute handling or a legal obligation. |
| Policy changes | If our data practices change, we may update this page and adjust the displayed date. Continued account use after an update means you should read the revised privacy wording carefully. |
Visible Features Of This Privacy Page
We have arranged this page so you can locate the main privacy subjects without searching through general account copy. The opening section states the purpose, the...
Purpose panel
The opening panel identifies this page as p99gam’s privacy policy and signals that its subject is personal data connected with account access from Pakistan.
Scope block
The central policy block brings collection, use, sharing, retention and regional access into one place, making the main handling principles easier to locate.
Contact cards
Dedicated contact cards separate ordinary privacy questions from urgent account security concerns, so you can choose a suitable route without sending sensitive credentials.
Control signals
The safeguard cards describe practical controls such as role access, verification, retention handling and payment reference use rather than relying on broad assurances.
Related rules
The comparison section shows how privacy wording sits beside account, wallet, security and regional rules while keeping personal data as the central subject.
Question set
The final questions cover common data choices, account closure, cookies, payment records and security concerns, giving you a quick path to the relevant explanation.