Privacy Policy For Your Account
Your pak365 app account, live table activity, sportsbook choices and Pakistan payment references create data we must handle carefully. This Privacy Policy explains what we collect, why we...
How We Handle Your Data
This Privacy Policy applies when you open or use a pak365 app account in supported regions where local law permits. We collect the details needed to create your profile, secure access, process KYC checks, manage withdrawals and answer support requests. Payment references from JazzCash, Easypaisa, SadaPay, NayaPay and Raast help us match transactions to your account without exposing more data than required.
We also record device, session and security signals so we can spot unusual access and protect your balance. We share data only with service partners needed for account checks, payment routing, fraud controls, live casino feeds, sportsbook settlement or legal requests. We keep records for operational and legal periods, then delete or restrict them when they are no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Routes For Privacy Requests
You can reach us about privacy without guessing which team should handle the request. We separate account access questions, document concerns and payment reference checks so your message reaches the right queue. Include your registered mobile number and avoid sending card images unless support specifically asks through a secure channel.
Account data request
Ask support to confirm the account details we hold, the purpose for keeping them and the steps needed if you want a correction to name, mobile number or profile data.
Payment reference query
If a JazzCash, Easypaisa, SadaPay, NayaPay or Raast entry looks unclear, send the reference ID so we can trace the privacy record linked to that transaction.
Security concern
Report unexpected login alerts, changed device patterns or messages asking for private codes. We use the report to secure your account and check related data access logs.
How We Keep Policy Checks Current
Our Privacy Policy is maintained by the same operational teams that handle account access, KYC queues, support scripts and transaction tracing. That keeps the wording close to how the platform works each...
Operational input
Support, security and payments teams feed practical cases into the policy wording, so privacy language reflects real account checks rather than abstract legal phrasing alone.
KYC alignment
Identity document handling is described around collection, verification, storage and removal triggers, giving you a clearer view of how account checks affect your data.
Session controls
We document device IDs, login timestamps and location signals because these records help detect account misuse and explain security decisions if you contact us later.
Payment mapping
Transaction references are linked to your profile only for reconciliation, withdrawal checks and support tracing, with access limited to teams handling those functions.
Partner checks
Service partners that process verification, streaming, sportsbook settlement or messaging receive only the data needed for their role under contractual controls.
Change control
When we adjust the policy, we check the change against account journeys, mobile screens and support responses before publishing the updated wording on this page.
Consistency Across Our Legal Pages
Privacy wording should not conflict with other legal pages you read on pak365 app. We align this page with account rules, cookie use, promotion terms and security explanations...
| Account terms | Account rules explain what you must provide; this Privacy Policy explains how those details are collected, used, stored and limited after your account is active. |
|---|---|
| Cookie page | Cookie wording covers browser storage and measurement tags, while this page connects those signals to privacy purposes such as session security and preference handling. |
| Promotion terms | Promo checks may require account eligibility records. This page explains how those records are handled without repeating the separate conditions for each promotion. |
| Security page | Security wording focuses on access controls. The Privacy Policy adds the data angle, including device logs, login alerts and action histories tied to your account. |
| Payment wording | Transaction pages describe how JazzCash, Easypaisa, SadaPay, NayaPay and Raast flows work. This policy explains how related references are stored and accessed. |
| Support scripts | Support responses are written to match the Privacy Policy, so requests about access, correction or deletion do not receive conflicting explanations from different teams. |
| Regional access | Where local law permits, account access wording and privacy wording use the same supported-region approach, avoiding promises that would not match operational checks. |
Policy Layout You Can Scan
We structure this Privacy Policy so you can see the practical privacy points before opening an account. The page separates data collection, use, sharing, storage, access requests and...