LEGAL REFERENCE

ec99 Privacy Policy for Pakistan

ec99 keeps your account privacy plain: what we collect, why we need it, and how it connects to access where local law permits. Open your account knowing the...

Pakistan privacy wordingAccount data useWallet record contextRequest contact paths
Explore Lobby Read FAQ
ec99 ec99 Privacy Policy for Pakistan

How ec99 handles your data

Our Privacy Policy is written for your ec99 account in Pakistan and supported regions. We collect only the details needed to create access, check sign-in activity, process wallet requests, keep records required by law, and protect the service from misuse. That can include your name, mobile number, email, device signals, session logs, IP address, and transaction references from local rails. We do

not sell your personal data. We share limited fields only with processors that help with identity checks, payment routing, fraud controls, hosting, analytics, or customer care, and require written handling instructions. When you ask us about a record, we match the request to your registered contact before giving any account-specific reply.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP PATHS

Contact us about your data

Privacy requests need a clear path, so we separate them from general account messages. Use the channel that matches your situation: signed-in chat for account-linked questions, email when you cannot access the account, and security contact for access concerns. We answer in Pakistani English and may ask for limited checks before discussing private records.

Team online

Signed-in chat

Message us from your signed-in ec99 account and choose privacy as the reason. We can link the request to your account without asking you to repeat sensitive details.

Email route

Email us from the address on your ec99 profile if you cannot sign in. Include your mobile number, preferred contact time, and the privacy request you want handled.

Access concern

For account access concerns, we first confirm control of your registered phone or email. That check helps us discuss privacy records without exposing them to another person online.

POLICY CHECKS

How we keep this policy current

This page is maintained as an operating document, not a static legal block. We check it against the account form, sign-in logs, payment references, device security, support scripts...

Policy owner

An ec99 operations owner keeps this page tied to live account flows, including sign-in, identity checks, wallet references and contact...

Local rail mapping

We map privacy terms to Pakistan rails such as JazzCash, Easypaisa, SadaPay and Raast, because transaction references and wallet names...

Access logging

We log key sign-in events, device signals and session changes to help secure your account. The policy explains these records...

Vendor checks

Processors that help with hosting, analytics, verification or payment routing receive only the fields needed for their task, and our...

Plain wording

We keep legal terms short where possible, then add account examples so you can connect the policy to forms, wallet...

Change record

When privacy wording changes, we keep a dated page update so you can see that the policy has moved with...

Aligned with related policy pages

Privacy does not sit alone on ec99. This page connects with related account, cookie, terms, and security pages so the same data use is described consistently. If another...

Cookie page
Our cookie page covers browser storage, while this Privacy Policy explains how those signals may connect to account security, session continuity and local access where law permits.
Terms page
The terms set account conditions; this policy explains the data required to operate those conditions, such as registration details, login checks, wallet references and contact records.
Security page
Security wording covers protection steps, while the privacy page explains which records support those steps, including device signals, failed logins and verified contact changes.
Wallet help
Wallet help may describe JazzCash, Easypaisa, SadaPay or Raast references; this policy explains how those references are stored, matched and protected in your account.
Account profile
Your profile collects contact and identity fields. This policy explains why each field is needed, how it supports access, and when we may ask for confirmation.
Support scripts
Customer care scripts ask only for details needed to locate your account or request. This policy explains why those checks happen before private records are discussed.
Promo board
If a promotion requires account matching, this policy explains how eligibility records, contact choices and wallet references may be used without adding unrelated data collection.
SCAN FRIENDLY

Privacy layout you can scan

We structure this Privacy Policy for quick reading on mobile and full reading on a larger screen. The page uses short sections, local context chips, request paths, retention...

Purpose labels Each main section states the purpose before the detail, helping...
Local context chips Short chips name Pakistan rails and access context without turning...
Request prompts We place contact prompts near data rights language so you...
Retention markers Retention wording is grouped with the data type it affects...
Security cues Security cues show where device signals, sign-in logs and contact...
Update block The policy layout includes an update area for material wording...

Privacy questions before you join

We collect account details you provide, such as name, mobile number and email, plus sign-in records, device signals, session activity and wallet references needed for access, security and transaction matching.

No. We do not sell your personal data. Limited fields may be shared with processors for hosting, verification, payment routing, fraud controls, analytics or customer care under written handling instructions.

Wallet references help us match your request to the correct ec99 account and transaction record. We use them for reconciliation, support checks, fraud controls and records required by law.

Device and login signals help us recognise account access patterns, investigate unusual activity and protect private records. They are used for security purposes, not for selling your personal data.

Yes. Contact us from your signed-in account or registered email and explain what needs correction. We may verify your phone or email before changing account-linked personal data.

We keep records for as long as needed for account operation, legal duties, transaction matching, dispute handling and security. Some records may remain after closure where retention is required.