LEGAL REFERENCE

Privacy Policy for your u123 account

u123 keeps your Privacy Policy clear: we explain what account, device and payment data we collect, why we use it, and how you can ask us about it...

Account dataPayment privacyDevice recordsSupport access
u123 Privacy Policy for your u123 account

How we handle your personal data

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

CONTACT ROUTES

Ask us about privacy choices

Your privacy questions should reach the team that can trace account records safely. Use the channel linked to your logged-in account where possible, because it lets us confirm identity before discussing personal data. We may ask for limited proof before changing, deleting, or releasing records.

Team online

Live chat

Use in-account chat for privacy questions tied to your profile, device sessions, or payment references. We check account ownership first, then route the request to the team handling data access or correction.

Email request

Send privacy requests from the email linked to your u123 account. Include the issue, affected date range, and any JazzCash, Easypaisa, SadaPay or Raast reference you want us to locate.

Security alert

If you think your account data was accessed without permission, contact us quickly. We can lock sessions, check login records, and explain which personal details may need extra protection.

POLICY CHECKS

How we keep this policy accurate

We update this Privacy Policy when our account flow, payment handling, security controls, or support process changes. Our checks focus on what we actually collect and how long...

Data mapping

We map each account field to a purpose, such as login, verification, payment matching, security checks, or support. If a...

Payment alignment

Privacy wording is checked against how JazzCash, Easypaisa, SadaPay and Raast references appear in our records. That helps us explain...

Security logging

We record login attempts, device changes, failed access events, and password actions to protect your account. These records help us...

Support training

Support staff receive privacy handling rules for identity checks, account discussions, and record requests. They are told not to disclose...

Retention checks

We keep personal data only for account operation, dispute handling, legal duties, fraud prevention, and security needs. When retention is...

Change log

When we adjust this Privacy Policy, we update the page text so you can see the current position. Major changes...

Consistency across our policy pages

Privacy sits beside other u123 legal pages, but it has a separate purpose. This page covers personal data, account records, payment references, device logs, and your privacy requests...

Account termsOur account terms explain access rules and platform use, while this Privacy Policy explains the personal data behind those steps. We keep both aligned so your login journey is described consistently.
Cookie wordingCookie details focus on browser storage, analytics tags, and session recognition. This Privacy Policy connects those records to broader account privacy, device security, and your choices around stored data.
Payment recordsPayment pages may describe transaction flow, but this page explains privacy treatment for references, matching data, verification trails, and support evidence linked to Pakistan payment rails.
Security rulesSecurity wording describes account protection steps. The Privacy Policy explains which logs support those steps, including session events, password changes, unusual device access, and staff access controls.
Support recordsSupport pages tell you how to reach us. This page explains what we may record during that contact, including chat content, email headers, request history, and verification checks.
Regional accessWhere access depends on supported regions, our legal wording stays consistent. This Privacy Policy adds how region signals, IP data, and payment context may be used for compliance checks.
Policy updatesWhen one legal page changes, we check connected privacy wording as well. That reduces confusion if an account feature, payment partner, or support process affects personal data.

Visible cues inside this privacy page

We built this privacy page so you can scan the parts that matter before opening or using your account. The layout separates collection, use, sharing, storage...

Clear sections

Each block deals with one privacy question, such as what we collect, why we keep it, who helps process it, and how you can contact us about account records.

Local examples

We mention JazzCash, Easypaisa, SadaPay and Raast only where payment privacy is relevant. That keeps the policy grounded in Pakistan account flows rather than abstract legal wording.

Plain language

We use clear English for Pakistan rather than dense legal phrasing. When a technical record appears, such as an IP address or device log, we explain its purpose.

Action paths

Privacy choices are linked to support routes, not hidden in long paragraphs. You can ask about access, correction, deletion, or security concerns through the account channel.

Purpose labels

Data uses are tied to reasons such as verification, fraud checks, payment matching, support history, legal duties, and account protection. We avoid collecting details without a working purpose.

Update signals

If this Privacy Policy changes, the page text is refreshed to reflect the current account flow. Important changes may also appear inside your account area.

Common privacy questions at u123

We collect account details you provide, verification records, contact data, payment references, device signals, session activity, and support messages. We use these records to run your account, protect access, and answer privacy requests.

Payment references help us match your account with JazzCash, Easypaisa, SadaPay or Raast activity. They also support dispute checks, fraud prevention, settlement records, and privacy requests about a specific transaction.

We share personal data only with service partners needed for account operation, hosting, security, verification, analytics, support, payment processing, or legal requests. We do not sell your personal data to advertisers.

Contact us from your registered email or logged-in account and describe the records you want. We may verify your identity before releasing data, correcting details, or explaining retention for your account.

Retention depends on the record type and purpose. Account, payment, security, and support records may be kept while needed for operations, disputes, fraud checks, legal duties, or account protection.

We use access controls, security logging, verification steps, and staff handling rules to reduce unauthorised viewing. Sensitive requests are checked before support discusses account data or changes privacy-related records.