Privacy Policy For Your py888 Account
py888 Privacy Policy explains what account, device and transaction data we collect before you open an account in supported regions of Pakistan. We set out why each record...
How py888 Handles Personal Data
py888 collects only the personal data needed to create your account, protect access, process transactions and meet record duties in supported regions. This Privacy Policy is written for Pakistan, so references to JazzCash, Easypaisa, SadaPay and Raast describe the payment records we may receive, such as wallet name, masked number, amount, status and time. We do not sell your personal data. We
share limited records with processors that help us run account security, payment checks, fraud screening, hosting, support and message delivery. Access may depend on where local law permits. If a rule requires a longer retention period, we keep the record for that period, restrict internal access and delete or anonymise it when the duty ends.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep The Policy Current
Our Privacy Policy is maintained by the py888 team that works with account access, payments, security logs and support records. When a workflow changes, we check the wording...
Account flow checks
We compare the policy with each account step, from mobile number entry to password reset. This keeps the wording aligned...
Payment record mapping
We map which fields may arrive from JazzCash, Easypaisa, SadaPay and Raast. The policy names the record types we expect...
Security log scope
Device, IP and session logs are described as security records because they help protect account access. We limit their use...
Retention checks
We keep retention wording tied to real record duties, such as transaction logs and support tickets. When a storage period...
Processor controls
Service providers that host systems, deliver messages or process checks receive only the records needed for that task. We require...
Local wording
The policy uses Pakistan payment names and plain English so you can connect each privacy point to your own account...
Consistency Across Our Legal Pages
Privacy statements should not conflict with other py888 legal pages. We align this Privacy Policy with account terms, cookie controls, promotion rules and contact pages so your data...
| Account terms | Where the account terms mention identity checks, this Privacy Policy explains which personal data may be used for those checks and why the record may be retained for compliance tasks. |
|---|---|
| Cookie controls | When our cookie banner asks for a choice, the wording matches this Privacy Policy so you see the same categories for essential access, analytics and security checks across py888. |
| Promotion rules | If a promotion needs eligibility checks, the privacy wording explains the account records involved. We keep that wording separate from marketing copy so data use stays clear. |
| Support scripts | Support replies use the same privacy meanings as this page. Staff may verify your account before discussing personal data, but they should not request wallet passwords or private codes. |
| Payment status pages | Transaction status screens may show masked wallet details and timing. This Privacy Policy explains why those records appear and how they support reconciliation, fraud checks and customer help. |
| Security pages | Where py888 describes login protection, this policy explains related data such as device signals, IP records and session timestamps. The same purpose is used across security wording. |
| Contact page | The contact page points privacy matters back to this policy so your request reaches the right staff. That keeps account access, correction and deletion queries in one track. |
Visible Privacy Cues Across py888
We place privacy cues near the moments where you share data, not only on this page. Account forms, security prompts, wallet screens and support contact areas...
Form labels
Account forms tell you why we ask for key details such as mobile number, name or email. The label stays close to the field so the privacy purpose is visible.
Masked records
Wallet references are shown in masked form where possible. This helps you recognise a JazzCash, Easypaisa, SadaPay or Raast transaction without exposing full account or wallet details.
Session prompts
When we detect a new device or location signal, the prompt explains that the data is used for account protection. It is not treated as public profile content.
Privacy links
Links to this Privacy Policy appear near account, wallet and support areas. You can return to the wording before sharing details or asking us to correct stored records.
Plain timestamps
Transaction and support timestamps are kept in a readable format so you can match our records to your own activity. This also helps us answer privacy requests accurately.
Clear request path
The page explains which channel to use for access, correction or deletion questions. We separate privacy requests from general service chat so the right checks happen first.