LEGAL REFERENCE

Privacy Policy for your ep999 account

ep999 keeps live casino, slots and sportsbook account data tied to one privacy record, so you can see how we collect, use and protect your details before you...

Pakistan privacy termsAccount dataJazzCash contextSupport access
Explore the lobby Read FAQ
ep999 Privacy Policy for your ep999 account

How our Privacy Policy applies

This Privacy Policy explains how ep999 handles the personal data you provide when you create an account, verify access, contact support, use the cashier, or move through our lobby. We collect details needed to run your account, secure logins, process payment records, answer requests, and meet operational duties in supported regions of Pakistan. We do not sell your personal data. We may

share limited records with service partners that help with account checks, fraud screening, payment reconciliation, hosting, analytics, and support tools. These partners receive only what is needed for the task. When you use JazzCash, Easypaisa, SadaPay, or Raast, we record transaction references so your account balance and support history can be traced accurately.

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

CONTACT ROUTES

Ask us about your privacy choices

If you want to access, correct, or query the data tied to your ep999 account, contact us through the route that fits...

Live chat privacy queue Ask our chat team for the data linked...
Email requests Send privacy questions by email when you need...
Cashier data queries For JazzCash, Easypaisa, SadaPay, or Raast references, contact...
CHECKED WORDING

Privacy checks behind this page

We write this Privacy Policy from the operator side of ep999, using the systems we actually run. The wording is checked against account creation, login logs, cashier records, support handling, and regional...

Policy owner

A dedicated internal owner keeps this Privacy Policy aligned with account flows, support practice, and cashier records, so your rights and our duties are explained in one consistent voice.

Payment record mapping

We map JazzCash, Easypaisa, SadaPay, and Raast references to the data fields our support team can see, reducing guesswork when you ask about payment-related privacy records.

Login security checks

Device, IP, and session records are treated as security data. We use them to protect your account, investigate unusual access, and support privacy requests about login history.

Support access controls

Support staff see only the records needed for the request they handle. More sensitive account actions require extra checks before any personal data is displayed or changed.

Retention checks

We keep personal data only for account operation, legal duties, dispute handling, and security needs. When a record is no longer needed, we schedule it for removal or masking.

Plain English updates

When policy wording changes, we aim to explain the change in clear Pakistani English. You should not need legal training to understand what changed in your privacy terms.

Where this policy fits

This Privacy Policy sits beside our account terms, cookie page, and security wording. Each page has a separate job, but we keep the language aligned so you can...

Account terms
The account terms explain how you use ep999. This Privacy Policy explains what personal data supports that use, including profile records, verification checks, payment references, and support history.
Cookie page
Our cookie wording explains browser signals, while this Privacy Policy explains personal data. We link the two so your consent choices, device records, and session activity are not mixed together.
Security wording
Security wording focuses on protecting accounts. This Privacy Policy explains the data behind that protection, such as login records, device checks, password reset traces, and account change history.
Cashier rules
Cashier wording explains how payment activity moves through ep999. This page explains which payment records are stored, why references are retained, and how support uses them during privacy requests.
Promotion terms
Promotion terms may mention account eligibility. This Privacy Policy explains the data checks behind eligibility decisions, including region, account status, and duplicate-account signals where local law permits.
Support scripts
Support scripts help agents answer you consistently. This policy defines what agents may ask for, what they should avoid collecting, and when a privacy request needs escalation.
Change log
When policy text changes, we keep an internal record of what was adjusted and why. That record helps us answer questions about past wording and current data handling.
PRIVACY LAYOUT

Privacy layout across your screen

We design the Privacy Policy page so you can scan it before you open an account and return to it later from support or cashier pages. The layout...

Short badges The badges under the hero point to the main privacy...
Clear section labels Each section label uses plain wording rather than legal clutter...
Cashier context chips JazzCash, Easypaisa, SadaPay, and Raast chips show where payment references...
Contact cards The contact cards separate chat, email, and cashier data queries...
FAQ placement The FAQ sits after the policy detail so quick answers...
Update visibility When this Privacy Policy changes, we keep update signals close...

Privacy questions about ep999

We collect account details you provide, login and device records, support messages, payment references, and security checks. The data helps us run your account, answer requests, and protect access in supported regions.

Payment references from JazzCash, Easypaisa, SadaPay, and Raast help us match account balances, resolve cashier questions, and trace disputes. We avoid collecting extra documents unless a security or verification step requires them.

Yes. Contact support and describe the data you want to access, correct, or query. We may verify your account first so personal records are not shared with the wrong person.

We share limited data with service partners that help with hosting, payment checks, fraud screening, analytics, and support tools. They receive only the records needed to perform their assigned task.

We keep records for account operation, security, legal duties, payment reconciliation, and dispute handling. When a record is no longer needed for those purposes, we schedule removal, masking, or restricted storage.

Login records help us detect unusual account access, support password recovery, and answer privacy questions about session history. They may include device signals, IP records, time stamps, and account action traces.