How ec99 game Handles Your Account Data
Every time you open your ec99 game account we collect only what we need: your registration details, sign-in records and the reference numbers behind your JazzCash, Easypaisa, SadaPay...
Our Position In Supported Regions
Here is how we handle privacy at ec99 game. We serve supported regions only, and where local law permits we treat your personal data the way that law expects: collected for a stated reason, kept no longer than the work needs, and shared with third parties only when a payment rail or identity check requires it. If you register from Pakistan, your
account records, device identifiers and JazzCash, Easypaisa, SadaPay or Raast references sit on our systems, processed by the providers that clear those transfers. Some markets ask for more than others, so the rights described here apply wherever they are recognised, and where a local rule gives you a stronger right, that rule wins.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Drafts And Checks This Page
This page is written by the team that runs ec99 game day to day, not by an outside agency. The people who handle your withdrawals, your support tickets...
Operator Written
Every paragraph here is drafted by our own operations staff, so the wording matches the steps you actually take when...
Change Dates
Each edit carries a date and a short reason. When we shorten how long we keep closed-account records, you will...
Plain Language
We avoid legal padding wherever a normal sentence will do. If a clause takes you two reads, tell our support...
Access Control
Login checks, device prompts and encrypted connections protect the data we hold. Access to your records inside our team is...
Regional Awareness
We track how Pakistani data expectations differ from other supported markets and apply the stricter reading whenever two sets of...
No Data Selling
We do not sell your personal details to outside brokers. Sharing happens with payment and identity partners only, and only...
How This Page Matches Our Others
Our legal pages share one voice and one set of definitions. The same words for account data appear here, on our terms page and on our cookie page...
| Terms Page | Account definitions used here come from the same wording as our terms page, so a phrase like account holder means the same thing in both places. |
|---|---|
| Cookie Page | Cookies that keep your session open are described on our cookie page, while this policy explains why we keep those records and how long they survive. |
| Payments Page | JazzCash, Easypaisa, SadaPay and Raast flows are set out on our payments page. Here we only explain which transaction details we retain and why. |
| Support Page | Response windows quoted on our support page match the promise made here, so one address reaches the same privacy desk either way. |
| Security Page | Password and device rules sit on our security page. This policy covers the logs those rules create and who inside our team can open them. |
| Region Lists | Where a market page lists supported regions, this policy inherits that same list. If your region is not on it, we do not open an account. |
| Shared Dates | Every page carries the same update date when a shared definition moves, so you can compare two documents and see they were revised together. |
What You Will Find On This Page
The layout follows the order your questions usually arrive in. A short opening tells you what the page covers, a posture block states where our rules...
Collection List
The first block names the data we ask for at registration, from your email address to the device you sign in with on match nights. Nothing is gathered without a stated reason.
Retention Window
A second block explains how long each record type stays with us. Closed accounts keep fewer traces than active ones, and transfer references outlive gameplay logs.
Access Rights
You can ask for a copy of your records, request a correction, or object to a use you did not expect. Each route is listed with the details we need to verify you.
Sharing Rules
We name the categories of partner who may see your data, such as payment processors and identity checks, and the limit placed on what each of them receives.
Security Layer
Encryption in transit, restricted internal access and login alerts are described together so you can see how one layer backs the next. We log who opens a record.
Contact Routes
Email, live chat and transfer-reference queries are grouped at the end, each with a response window, so you never have to hunt for the right address. One desk handles all three.