LEGAL REFERENCE

Privacy Choices For Your ec1 Account

ec1 keeps your Privacy Policy choices close to the account flow: data use, verification checks, payment records and message settings are explained before you join. Open your account...

Pakistan data handlingJazzCash contextEasypaisa contextSadaPay and RaastProfile controls

Browse lobby Read FAQ

How Our Policy Treats Your Data

Our Privacy Policy explains why we collect account data, how we verify identity, and how payment records are linked to your ec1 profile. In Pakistan, cash-in or transfer references from JazzCash, Easypaisa, SadaPay and Raast may be stored so we can match receipts, resolve support cases, and meet record-keeping duties. We do not sell your account data. We share limited details only

with service partners who help process checks, prevent fraud, deliver messages, or run secure hosting. Access to your account remains available in supported regions and where local law permits. When a legal request reaches us, we record the request, keep the reply within the required scope, and retain an audit trail for internal checks. You can contact us for access or correction

requests.

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

CONTACT PATHS

Privacy Help From ec1

Privacy requests are handled through ec1 support so we can confirm the account before changing or sharing any data. Tell us what...

POLICY CHECKS

How We Keep Policy Wording Accountable

We write the Privacy Policy against the way ec1 actually works, not from a generic template. Each update is checked against account screens, verification steps, live casino session records, sportsbook logs, slot...

Operational checks

Each policy change is checked by our operations and support teams before it goes live, so the wording matches how ec1 account screens and payment records actually work.

Payment mapping

We map privacy wording to JazzCash, Easypaisa, SadaPay and Raast records, including transaction references, time stamps, account names, and support messages used to resolve payment queries.

Session records

Live casino tables, slots and sportsbook pages create technical logs. Our policy explains how those logs help protect accounts, diagnose errors, and confirm activity linked to your profile.

Verification scope

Identity checks are described in practical terms: what we may request, why the check is needed, and how verification records connect with withdrawals, security alerts, and account access.

Partner boundaries

When service partners process hosting, messaging, fraud checks or payment support, we keep the shared data tied to that task instead of opening wider account access.

Pakistan wording

We use clear Pakistani English and local payment names, so you can understand how the Privacy Policy applies to JazzCash receipts, Easypaisa messages, SadaPay references and Raast transfers.

Policy Consistency Across ec1 Pages

Our Privacy Policy sits beside other ec1 legal pages, so the same data terms should mean the same thing wherever you read them. We align wording across cookies...

Account identifiers

The Privacy Policy uses the same account identifiers as our Terms page, so your phone, email, username and verification status are described consistently across ec1 legal pages.

Cookie language

Cookie wording connects back to this Privacy Policy, explaining how browser data, device signals and session IDs support login security, saved preferences and page performance.

Payment records

Payment references appear with the same meaning across policy pages: they help match JazzCash, Easypaisa, SadaPay and Raast activity to your account and support cases.

Message preferences

Promotional and service message settings are described consistently, so you can see which messages relate to account security, payment updates, privacy replies, and lobby alerts.

Verification wording

Where another ec1 page asks for verification, this Privacy Policy explains the data side: why we request documents, how checks are recorded, and who may handle them.

Security records

Login alerts, password changes and device checks are handled with the same security meaning across ec1 pages, helping you understand when data is stored for account safety.

Request handling

Access, correction and deletion requests follow the privacy process described here, even when you begin from support, account settings, email, or a payment query.

Privacy Layout You Can Read Quickly

This page is arranged so you can scan privacy topics without losing context. The layout separates collection, use, sharing, retention, rights and contact steps, while keeping...

Plain section labels

Each heading names the privacy topic directly, so you can move from account data to payment records, message settings, security logs and support requests without guessing what applies.

Local context chips

Short chips highlight JazzCash, Easypaisa, SadaPay and Raast where they matter, making it easier to see how local payment references are treated under the Privacy Policy.

Action wording

Where you can request access, correction or deletion, the page uses direct wording and points you to the contact route that can verify your account safely.

Security callouts

Security items are separated from general data use, so login alerts, device records, password resets and unusual activity checks are easier to understand within the policy.

Retention cues

Retention wording explains why some records remain after a transaction or support case, especially when payment matching, legal duties, fraud prevention or account disputes are involved.

Rights summary

Your access and correction options are grouped near support details, so you can see what to send us and how we confirm the account before acting.

Privacy Policy Questions Before Joining

We collect details needed to create, verify and protect your account, such as contact data, login records, payment references, device signals and support messages connected with your ec1 activity.

We use JazzCash and Easypaisa references to match payments to your account, answer support queries, check unusual activity and maintain records required for payment handling in supported regions.

Yes. Send the correction request through email or support with the account detail that needs changing. We verify the profile first, then update records where correction is allowed.

We share data only where a partner supports a defined task, such as hosting, payment processing, fraud checks, messages or verification. The Privacy Policy explains these boundaries.

Some payment records stay after a cash-in or withdrawal because they support receipt matching, dispute handling, fraud prevention and legal record needs. Retention depends on the record type.

Your profile and support channels can help manage message preferences. Security and service messages may still be sent when they relate to account access, payments or privacy requests.