LEGAL REFERENCE

Privacy Policy for your ue5 account

Our Privacy Policy sets out what ue5 collects when you open your account, verify access, use the lobby and request payouts where local law permits. Read it before...

Account data explainedJazzCash privacy contextPakistan support routesChange alerts
Explore the lobby Read FAQ
ue5 Privacy Policy for your ue5 account

How ue5 handles your data

Our Privacy Policy explains the data we collect to create and protect your ue5 account, including your name, phone number, email, login records, device signals, transaction references and support messages. We use this data to run account access, payment checks, fraud controls, customer support and legal record keeping in supported regions of Pakistan. When you add funds through JazzCash, Easypaisa, SadaPay or

Raast, we record references needed to match the transaction with your account, not your full wallet password or private app login. We keep records only for operational, security and legal needs, then limit access within our team. You can ask us about access, correction or deletion, subject to verification and any duties we must keep under applicable law.

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

CONTACT ROUTES

Reach us about privacy matters

Privacy questions need a clear path, not scattered replies. Contact us from the same email or phone linked to your ue5 account...

Privacy email Send a privacy request from the email linked...
Logged-in chat Use live chat for privacy questions while you...
Security ticket For account security cases, send a ticket with...
POLICY CARE

How we keep policy wording accurate

This page is maintained by the ue5 team that works with account access, support and payments. We keep the wording practical, so you can connect the policy with actions you take in...

Policy check cycle

We run scheduled policy checks when account flows, verification steps or payment references change. That helps the wording stay connected to the way your ue5 account actually works.

Local wording

We write for Pakistan in clear English, with references to JazzCash, Easypaisa, SadaPay and Raast where they affect privacy records, receipts or identity checks.

Access controls

Private account records are limited to trained team roles. Support can see only what is needed to answer your request, verify ownership or resolve a security case.

Payment records

Wallet and bank references are used to match deposits and withdrawals with your account. We do not ask for your private app password for JazzCash, Easypaisa or SadaPay.

Change alerts

When the Privacy Policy changes in a material way, we aim to place a clear date or notice area so you can read the changed wording before continuing.

Request log

Privacy requests are logged with dates, contact channel and verification status. This helps us track replies while keeping the request tied to the account owner.

One privacy position across every page

Our Privacy Policy is not isolated from the rest of ue5. We keep related legal and account pages aligned, so privacy wording stays consistent when you move between...

Terms page match
Where our terms mention identity checks or account security, this Privacy Policy explains the data angle behind those actions, including why we may need contact and transaction records.
Cookie page match
If a cookie notice refers to device or session signals, this page explains how those signals support login safety, fraud checks and a more stable account session.
Account help match
When account help asks you to verify a phone number or email, the privacy wording clarifies why we ask and how we limit sharing after verification.
Payment page match
Payment pages may show JazzCash, Easypaisa, SadaPay and Raast. This Privacy Policy explains the transaction references kept for matching, support and required record retention.
Security page match
Security wording covers passwords, login checks and device alerts. This policy adds how related records are collected, accessed and kept for account protection.
Promo page match
If a promo board requires eligibility checks, this page explains how account status, region and activity records may be used without exposing private wallet credentials.
Contact page match
Our contact page may route you to chat or email. This policy explains why we verify ownership before discussing account records or sending personal data.
LAYOUT SIGNALS

Policy layout you can scan quickly

We designed this Privacy Policy page so you can find the privacy point you need without reading unrelated lobby copy. Each visible block has a narrow purpose and...

Plain language blocks Each section uses short legal wording in everyday Pakistani English...
Local context chips The chips near the policy notice highlight Pakistan payment references...
Request pathway The contact block shows how to reach us about access...
Policy dates Date areas help you see when wording was changed. If...
Security cues Lock, file and receipt cues mark where privacy overlaps with...
Mobile reading The page is arranged for smaller screens, so you can...

Questions about our Privacy Policy

We collect details needed to create and protect your account, such as name, phone, email, login records, device signals and verification status. Payment references may be added when transactions are made.

No. We record transaction references needed to match your payment with your account. Your private JazzCash, Easypaisa, SadaPay or bank app password should never be sent to our team.

Verification may be needed to confirm account ownership, payment access or withdrawal requests where local law permits. We use those records for checks, fraud controls and legal retention duties.

Yes, you can contact us from your linked email or logged-in account. We verify ownership first, then explain what data can be shared and any legal limits that apply.

Retention depends on the record type. Some data is kept for active account use, while transaction, security and legal records may be retained longer to meet operational duties.

Access is limited to team roles that need the data for support, verification, payments, security or legal handling. We do not make private account records public.