LEGAL REFERENCE

Privacy Policy For Your link02 Account

link02 puts account access, transaction records and device data under one clear Privacy Policy before you open your account in Pakistan. Read how we collect, use, store and...

Account dataDevice securityJazzCash contextRaast records
link02 Privacy Policy For Your link02 Account

How Our Privacy Policy Applies

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

CONTACT ROUTES

Privacy Questions Reach Our Team

If you want to ask about your personal data, request correction, or query a privacy-related transaction record, contact us through the same...

Live chat privacy queue Use live chat for quick privacy questions about...
Email data request Send email when your request needs a written...
Account message centre Your account message area is used for privacy...
CARE CONTROLS

How We Keep Policy Checks

We write this Privacy Policy from our own operating flow, not from a generic template. The wording reflects the data we see when you log in, browse games, create payment requests, contact...

Account access checks

We describe login data because it helps protect your account from unauthorised access. This can include device type, IP region, session timing and security prompts tied to your account activity.

Payment record clarity

We explain how JazzCash, Easypaisa, SadaPay and Raast references are handled. Transaction IDs and status replies help reconcile requests without requiring private wallet credentials from you.

Withdrawal verification trail

Withdrawal checks may involve account name matching, payment rail status and support confirmations. The Privacy Policy sets out why these records exist and how they support accurate processing.

Support transcript handling

Support conversations can contain account and transaction details, so our policy explains retention and access controls. We use transcripts to resolve your case and maintain a clear request history.

Cookie and device signals

The policy explains cookies, device identifiers and preference storage in plain language. These signals help keep your session stable, remember settings and flag unusual access patterns.

Policy change checks

When our account flow or payment handling changes, we check whether this Privacy Policy needs new wording. Updates are written to help you understand the data impact before continuing.

Consistency Across Legal Pages

Our Privacy Policy sits beside other legal pages, so the wording has to stay consistent with how link02 explains accounts, cookies, payments, withdrawals and support. Each page has...

Terms pageWhere the Terms describe account rules, this Privacy Policy explains the personal data used to apply those rules. The two pages are kept aligned so account decisions are easier to understand.
Cookie pageCookie wording covers browser storage in detail, while this page explains how those signals connect to privacy. Together they show why session, preference and security cookies may appear.
Payments pagePayment content explains the account flow, while this policy explains the data trail behind it. JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction records.
Withdrawal pageWithdrawal wording explains processing steps, and this policy covers identity checks, status updates and related retention. That link helps you see why verification records may be kept.
Support pageSupport content tells you how to reach us, while the Privacy Policy explains what happens to your messages. We connect each case to verified account access before discussing details.
Security pageSecurity wording focuses on protection measures, while privacy wording explains the data behind them. Device checks, login records and alerts are described here from a data-handling angle.
Promotions pagePromotional terms may use account activity to decide eligibility, while this Privacy Policy explains how such activity records are handled. We separate offer rules from privacy handling.
PAGE SIGNALS

What This Policy Shows Clearly

This page is designed so you can scan the privacy points that matter before opening an account. We separate data categories, purposes, sharing, retention and your request routes...

Plain data categories We separate account details, device signals, transaction records and support...
Purpose-first wording Each privacy point explains why we use data, not just...
Local Pakistan context The policy names Pakistan payment rails where they affect records...
Sharing boundaries We explain when data may be shared with service providers...
Retention cues The page explains why some records are kept for disputes...
Request routes You can see where to ask for access, correction or...

Privacy Policy Questions Answered

We collect account details, login records, device signals, transaction references, support messages and preference data. The exact data depends on how you use your account and which services you access where local law permits.

Those rails can create transaction references, status replies and reconciliation records tied to your account. We use that data to confirm requests and resolve payment queries without asking for wallet PINs.

No. Our Privacy Policy states that wallet credentials, banking passwords and PINs should not be sent to us. We only need transaction references and account verification details relevant to your request.

Support messages may be stored with your account case so we can answer follow-up questions and resolve disputes. Access is limited to teams who need the record for support or compliance work.

Yes. Contact us through chat, email or the account message area and explain what needs correction. We may ask for verification before changing records to protect your account from unauthorised edits.

Cookies and device signals help keep your session active, remember preferences and detect unusual access. The Privacy Policy explains these uses so you know how browser and device records support account safety.

When we change the Privacy Policy, we update the page wording and date. Major changes affecting account data or transaction handling may also be flagged through account messages or site notices.