LEGAL REFERENCE

Privacy Policy For Your ul111 Account

Our Privacy Policy explains what data we collect when you open an account, verify access, use wallet rails, or contact us from Pakistan. Read it before you join...

Pakistan account dataJazzCash and Easypaisa recordsDevice security checksSupport message handling
Explore Lobby Read FAQ
ul111 Privacy Policy For Your ul111 Account

How We Handle Your Privacy

This Privacy Policy applies to ul111 account activity in supported regions, including Pakistan where local law permits access. We collect only the data needed to create your account, protect login sessions, process wallet activity, answer support requests, and meet record duties that apply to online gaming services. That may include your name, contact detail, device identifiers, IP region, account actions, payment references,

and security checks linked to JazzCash, Easypaisa, SadaPay, or Raast. We do not sell your personal data. We may share limited data with service partners that help us run verification, payments, fraud controls, hosting, analytics, and customer care. Each partner receives only what is needed for that purpose. You can contact us about access, correction, deletion, or restriction requests, and we will

respond according to applicable law and account-safety needs.

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

CONTACT ROUTES

Reach Us About Privacy Requests

Privacy questions need a clear route, not a generic inbox loop. Use the contact path that matches your request, include your account email or mobile number, and avoid sending full card images or wallet PINs. We verify identity before changing or releasing account data.

Team online

Privacy email

Write to our privacy desk for access, correction, deletion, or consent questions. Include your account mobile number and the request type so we can match the record without asking for extra data.

Live help handoff

If you start through chat, our team can send the matter to the privacy desk after identity checks. Chat agents will not reveal wallet references until the account match is complete.

Wallet query link

For JazzCash, Easypaisa, SadaPay, or Raast privacy questions, share the transaction time and masked reference. We use those fields to locate records without asking for PINs.

POLICY CARE

Privacy Signals We Maintain

We write this policy from the way ul111 actually handles account data. The controls below reflect common privacy questions we receive around login checks, payment references, device use...

Account matching

Before we discuss personal data, we match your account through controlled fields such as mobile number, email, login region, or...

Payment minimisation

Wallet partners send references needed to reconcile activity, not your PIN or full banking profile. We store only the fields...

Device controls

We use device and IP signals to detect account takeovers, repeated failed logins, and unusual session patterns. These signals support...

Access logging

Our systems record when account data is viewed by authorised staff during support or verification work. Logs help us check...

Policy upkeep

When we change data handling for payments, identity checks, or support routing, we update the policy text to reflect the...

Retention checks

We keep data for account, security, and legal needs, then remove or anonymise it when retention is no longer required...

Consistency Across Our Legal Pages

Our Privacy Policy works alongside other ul111 legal pages, but it stays focused on personal data. We keep the wording aligned so you do not see one rule...

Cookie page link
Cookie choices connect to this policy because cookies can store device and session data. The cookie page explains tool types, while this policy explains how personal data is handled.
Account terms link
Account terms explain your use of ul111 services, while this policy explains data handling behind those account actions. Both pages use the same identity and verification concepts.
Wallet record link
Payment references appear in wallet records and privacy requests. We use the same masked fields across pages so you can identify a transaction without sharing sensitive wallet credentials.
Security wording
Security sections across our legal pages describe similar controls: login checks, session tracking, fraud screening, and limited staff access. This policy adds the personal-data angle to those controls.
Support records
Support pages describe how to contact us, while this policy explains how messages, attachments, and identity checks are stored. Sensitive wallet or identity material is handled through limited queues.
Regional access
Where access depends on supported regions, our legal pages use the same local-law wording. This policy explains how region signals may be used for compliance and account security.
Change alerts
If legal text changes, the relevant page carries the updated wording. For privacy changes, we focus the alert on data types, purposes, sharing, retention, or request rights.

Privacy Layout You Can Scan

This page is arranged so you can find privacy points quickly before opening or using an account. The layout separates collection, use, sharing, retention, rights, and...

Clear section labels

Headings name the privacy issue first, such as data scope, contact routes, or retention. You can move through the page without guessing which part applies to your request.

Local wallet examples

When we mention JazzCash, Easypaisa, SadaPay, or Raast, we do so to explain record handling. The examples show which references may be stored and why.

Plain wording

We avoid legal padding where a direct privacy explanation is clearer. Terms such as device signal, masked reference, and retention are used with context so the meaning is visible.

Request flow

The page shows how to ask for access, correction, deletion, or restriction. It also explains why identity checks happen before we release or change any account data.

Sharing limits

Partner sharing is described by purpose, not vague categories. You can see why hosting, verification, payment processing, analytics, or security partners may receive limited account data.

Change markers

Policy updates are written around what changed and when it applies. This helps you spot changes affecting data collection, use, retention, partner sharing, or privacy request handling.

Privacy Policy Questions For ul111

We collect account data such as name, mobile number, email, login region, device signals, account actions, support messages, and wallet references. We use it for access, security, payments, support, and legal record needs.

Device and IP data help us detect account takeovers, repeated failed logins, unusual regions, and session misuse. These signals support account safety and help us respond when you report suspicious activity.

No. We do not ask for or store wallet PINs. For JazzCash, Easypaisa, SadaPay, and Raast, we keep limited references such as time, amount, masked account fields, and transaction status.

Yes. You can contact our privacy desk to request access to your personal data. We will verify your identity first, then respond according to applicable law and account-security requirements.

You can request deletion, and we will assess it against legal, payment, dispute, and security record needs. Some data may need to stay for a required period before removal or anonymisation.

Support messages are available only to authorised teams handling your request, account checks, or security concerns. If a privacy matter needs escalation, access is limited to staff assigned to that route.

When we make a material privacy change, we update this page with revised wording. If the change affects data collection, sharing, retention, or rights, we make that change visible before it applies.