Account terms
Our account terms explain eligibility, login duties and service use. This Privacy Policy explains the personal records created by those actions, including contact details, session logs and verification evidence.
LEGAL REFERENCE
Privacy Policy for your earn111 account
earn111 brings your casino lobby, sportsbook access and Pakistan wallet flow under one Privacy Policy, so you can see how account data is collected, used and kept. Before...
Account dataWallet contextSecurity logsSupport records
How we treat your data
This Privacy Policy applies when you use earn111 in supported regions of Pakistan, where local law permits access to our services. We collect only the account, contact, device, wallet and activity records needed to run your account, protect access, process requests and respond to support queries. JazzCash, Easypaisa, SadaPay and Raast references may appear in our records when you choose those rails,
but we do not publish your wallet identity on public areas. Verification checks may require matching your name, transaction reference and account status. We keep records for operational, legal and security reasons, then limit access inside our team to staff who need them for account care, fraud checks or privacy response work.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How our policy stays accurate
We write this Privacy Policy from the way earn111 actually handles accounts, wallet references and support records. Policy text is checked against product changes before it is updated...
Data map checks
We map account sign-in, wallet reference, support and security logs into clear categories. That helps us explain why a record...
Access controls
Internal access is limited by role, so support, finance and security staff see only the record set needed for their...
Verification handling
When withdrawals or account changes need checks, we compare submitted details with existing account records. The aim is to confirm...
Device signals
We may record browser type, approximate region, session timing and security events. These signals help us spot unusual access attempts...
Support training
Our support team is trained to avoid collecting full wallet passwords or personal secrets. If a request needs proof, we...
Change control
Policy edits are checked before release, including references to JazzCash, Easypaisa, SadaPay and Raast flows. We keep the wording tied...
PAGE ALIGNMENT
Where this policy connects
This page focuses on privacy, but it works beside other earn111 legal pages. Each page has its own job: account rules explain use, cookie terms explain browser storage and this Privacy Policy...
Cookie page
The cookie page deals with browser storage and preference tools. This Privacy Policy connects that storage to wider account data, such as sign-in records and security monitoring events.
Promotions rules
Promotion rules may describe campaign participation, while this Privacy Policy explains the data trail behind account eligibility checks, reward records and support queries linked to a campaign entry.
Security statement
Security wording covers account protection practices. This Privacy Policy adds the privacy angle by naming the logs, access controls and verification records used to keep your account safer.
Wallet procedures
Wallet procedures explain transaction steps. This Privacy Policy explains how related references, timestamps and account matching checks are handled when JazzCash, Easypaisa, SadaPay or Raast appear in records.
Support policy
Support pages explain how to contact us. This Privacy Policy explains what happens to the messages, attachments and identity checks you provide while our team responds to your request.
Region wording
Regional wording clarifies that access depends on supported areas and local law. This Privacy Policy explains how we handle the account data connected to that access check.
VISIBLE CUES
Privacy layout you can read quickly
We have shaped this Privacy Policy so you can scan it without losing the legal meaning. Headings show the data theme first, then cards explain the action behind...
Plain headings
Each heading uses direct privacy wording, so you can tell...
Short badges
Badge rows summarise common record types such as account data...
Action cards
Card sections explain what we do in practice, such as...
Local naming
Where wallet context matters, we name Pakistan rails clearly, including...
Contact prompts
Contact areas explain when to use email, chat or the...
Update marker
When the Privacy Policy changes, we adjust wording on the...
Privacy Policy questions, answered
We collect the account details you submit, contact records, login signals, device data and wallet references needed to run your account. If verification is needed, we may also keep proof linked to your identity check.
No. We do not ask for wallet passwords or private access codes. We may keep transaction references, account matching data and timestamps so support and finance checks can trace a request.
Device and session records help us protect account access, investigate unusual logins and respond when you report activity you do not recognise. These records may include browser type, timing and approximate region.
Yes. Contact support if your name, phone number or email needs correction. We may ask for proof before making changes, and earlier records may remain restricted where audit or security needs apply.
Retention depends on the record type, legal need and account activity. Support chats, verification evidence and wallet references may be kept for different periods, then restricted or removed when no longer needed.
Access is limited by role. Support may see contact history, finance may see wallet references and security may see login signals. Staff access is tied to the task they are handling.
Use the privacy email or ask live chat to route you to a privacy ticket. Include your account name, contact detail and the concern, but do not send full wallet credentials.