Terms page link
The Terms page explains account rules, while this page explains data handling. When both apply to the same action, we keep the privacy part focused on collection and use.
LEGAL REFERENCE
Privacy Policy for your ea99aud account
ea99aud keeps your account data, session records and Pakistan payment details in one clear privacy framework, so you know what we collect before you open your account. This...
Account data usePakistan payment contextDevice and session checksSupport contact paths
How we handle your personal data
This Privacy Policy describes how ea99aud collects, uses, stores and protects data linked to your account in supported regions of Pakistan. We collect details you give us, such as your name, contact number and account credentials, plus technical records such as device type, IP region, browser signals and session activity. When you use local payment rails, we may process payment references, wallet
labels and transaction status so we can match your account request with the correct record. We use this data to run account access, security checks, customer help, fraud prevention and payment reconciliation. We do not sell your personal data. We keep records only for operational, legal and security needs, then reduce or remove them when they are no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
Privacy controls behind each account
We write this policy from our operating view, not as a detached summary. The controls below reflect how we handle account creation, sign-in checks, support messages and payment...
Limited collection
We ask for the account and contact details needed to create access, verify requests and handle local payment records. Extra...
Session records
We record device, browser and IP-region signals to spot unusual access patterns. These records help protect your account and explain...
Payment matching
JazzCash, Easypaisa, SadaPay and Raast references are used to match account wallet activity with the correct payment status. We do...
Access control
Privacy requests are handled by trained support staff with account-level checks. We avoid discussing personal data until the request has...
Retention rules
Some records must stay for fraud prevention, dispute handling and legal needs. When those reasons end, we reduce the record...
Policy edits
When this policy changes, we update the page date or page wording. Material changes are written in clear English so...
POLICY ALIGNMENT
How this page stays consistent
Our privacy wording connects with other legal pages across ea99aud, but it has a narrower job. This page is only about personal data: what we collect, why we use it, who may...
Cookie notice link
Cookie wording covers browser storage and tracking choices. This Privacy Policy connects that browser data with account records only when it helps access, safety or service delivery.
Payment records
Payment pages may describe transaction steps, but this page explains how references, wallet labels and status updates become personal data within your ea99aud account record.
Security wording
Security notices may describe protection tools. This page explains the personal data those tools may create, such as login events, risk flags and account recovery records.
Support transcripts
Help pages explain how to reach us. This page explains how chat text, email messages and attachments are stored, used and limited to your support request.
Regional access
Access wording may refer to supported regions. This Privacy Policy explains how location signals are used to manage availability, security checks and compliance with local requirements.
Account closure
If you close an account, some privacy records may remain for disputes, payment matching or legal duties. We separate closure from immediate deletion when retention is required.
Policy layout you can scan
We shape this Privacy Policy so you can move through it quickly before opening or using an account. The page highlights data types, reasons for use...
Data categories
We separate account details, device signals, payment references and support messages so you can see which data type is involved before reading the reason for collection.
Purpose labels
Each major use is tied to a purpose, such as account access, payment matching, fraud prevention or support. That keeps the policy practical rather than vague.
Pakistan context
Local wallet names appear only where they matter to privacy, such as transaction references and reconciliation. This keeps the policy relevant for your Pakistan account flow.
Retention cues
We explain why some records stay longer than others. Payment disputes, security checks and legal duties can require different timelines from ordinary account messages.
Choice routes
Where you can ask for access, correction or removal, the policy points you toward contact paths. We also explain when retention duties may limit a request.
Plain wording
We avoid legal clutter where simple wording works. The aim is that you understand what happens to your data before you share more details with us.
Privacy questions before you join
We collect account details you provide, such as name, contact number and login credentials. We also create technical records for device type, session activity and IP-region checks.
We use wallet references, status messages and timing details to match your account with the correct payment record. We do not ask for wallet passwords, PINs or private app access.
Device and session records help us recognise unusual access, support account recovery and explain activity if you contact us. They are used for security and service operation.
Yes, you can contact us to request a correction where the record is inaccurate. We may ask for proof before changing details linked to security or payment matching.
We may share limited data with service providers that help operate access, security, support and payments. They are expected to handle it only for the service purpose.
Retention depends on the record type and reason. Some account messages may be shorter lived, while payment, dispute and security records can remain for required operational or legal periods.