Data collection
This page describes the kinds of personal details and technical records we may collect when you create, access or manage an account.
LEGAL REFERENCE
How We Handle Your Personal Data
Our Privacy Policy explains how 988win12 collects, uses, stores and protects details connected with your account. We built this page for people in Pakistan who want clear answers...
Clear data purposesAccount security focusPakistan contextYour privacy choices
The Rules Behind Our Data Handling
This policy applies to personal data collected through 988win12 websites, account areas and support channels in supported regions. We may collect contact details, account credentials, verification records, device identifiers, connection logs, preference settings and messages sent to us. We use these details to provide account access, protect the service, process requests, detect unusual activity and meet applicable legal duties where local law
permits. Payment references may include JazzCash, Easypaisa, SadaPay or Raast details needed to match a transaction, but we do not ask for unnecessary credentials for those services. We retain records only for operational, security or legal reasons, then remove or anonymise them when no longer needed. You can ask about access, correction or deletion by contacting our privacy team, subject to lawful
exceptions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CARE PRACTICES
What Our Privacy Process Covers
Our privacy process reflects the practical steps involved in running an account service for Pakistan. We separate account credentials from routine support conversations, limit internal access by role...
Purpose control
We connect each data category with a defined operational purpose, such as account access, security checks, support handling or legal...
Access safeguards
Account details are available only to authorised personnel whose work requires them. Passwords should remain private, while our controls help...
Device signals
Browser, device and connection data can help us recognise suspicious access, maintain sessions and diagnose technical problems. We use these...
Verification records
When account verification is required, submitted details are used to confirm identity, protect access and satisfy applicable duties. We do...
Retention checks
We assess stored records against their purpose and applicable retention duties. Records can be removed, restricted or anonymised when they...
Policy updates
If our data practices change, we may amend this page and show a revised date or notice. Reading the current...
POLICY CONSISTENCY
How This Policy Fits Related Pages
Privacy language should remain consistent wherever you encounter it on 988win12. This page explains personal data handling, while connected legal pages may address account conditions, site access or transaction procedures. The comparison...
Use of data
Our stated purposes cover account operation, support, security checks, transaction matching and duties that may apply in supported regions.
Account conditions
Account terms may explain eligibility, conduct and access conditions, but they do not replace the privacy explanations about collection or retention.
Transaction handling
Payment procedures may describe how a request moves through a selected route, while this policy explains related personal data and reference handling.
Support requests
Support channels can resolve account questions, yet privacy requests may require extra identity confirmation before records are discussed or changed.
Security events
Security wording explains protective action after unusual access, while this page sets out why connection and device records may be used.
Policy changes
The current Privacy Policy controls data handling on this page; a dated update may alter wording when our practices or legal duties change.
Privacy Details Made Easy To Scan
We designed this policy page so you can locate practical answers without reading dense legal blocks from start to finish. The layout separates scope, contact routes...
Scope panel
The opening panel identifies the account, website and support contexts covered by this Privacy Policy, helping you understand where its wording applies.
Contact cards
Dedicated contact cards show how to raise a privacy request, ask an account question or escalate suspected unauthorised access without exposing private credentials.
Safeguard markers
Short markers draw attention to access control, device signals, retention checks and verification handling, keeping key privacy themes visible while you read.
Boundary table
The comparison block clarifies which privacy subjects belong here and which account or transaction subjects may appear on connected legal pages.
Plain questions
The question section translates recurring privacy concerns into direct answers about collection, sharing, retention, requests and local account context.
Update visibility
A clear policy structure makes future wording changes easier to notice, so you can return to the relevant subject whenever our data practices are amended.
Answers About Your Data
We may collect your contact details, login data, verification records, device identifiers, connection logs, account preferences and support messages. The exact categories depend on the account action, security event or request you make.
Device and connection signals help maintain sessions, diagnose access problems, recognise unusual activity and protect accounts from misuse. We use them for operational and security purposes connected with the service.
When you select JazzCash, Easypaisa, SadaPay or Raast, we may retain transaction references needed to match an account request. We do not require ordinary support messages to contain private payment credentials.
We may share limited details with service providers or authorities when needed for account operation, security, legal duties or a specific request. We expect handling to remain connected with the stated purpose.
Retention depends on the record type, its operational purpose, security needs and applicable duties in supported regions. When a record is no longer needed, we may delete, restrict or anonymise it.
Yes. Contact our privacy team with your registered email and describe the request. We may ask for reasonable identity confirmation before providing records, correcting details or assessing a deletion request.
Contact support promptly, avoid sharing your password and describe the unusual sign-in, message or device activity. We can help secure the account and route the matter for privacy and security handling.