LEGAL REFERENCE

Privacy Policy for your y04 account

Your y04 account data, device signals and Pakistan rail references are handled through this Privacy Policy before you open the lobby. We explain what we collect, why it...

Account data scopeJazzCash and Easypaisa contextSadaPay and Raast referencesSupport contact paths
y04 Privacy Policy for your y04 account

How we handle personal data

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

PRIVACY CONTACTS

Reach us about privacy requests

If you want to ask about data we hold, correct account details, or raise a privacy concern, use the contact path that matches your issue. We keep privacy requests separate from routine lobby questions so your case reaches the team handling account records and verification trails.

Team online

Live chat privacy queue

Open chat from your y04 account and ask for the privacy queue. We may verify your session first, then route the request to the team that can check account records securely.

Email request channel

Send your privacy question from the email linked to your account. Include the account name and request type, but do not place card images or identity files in the first message.

Account correction help

If your contact number, name spelling, or rail reference needs correction, support will ask for matching account signals before editing records. This reduces changes made from the wrong session.

DATA CARE

Checks behind this privacy page

We write this page from the operator side, using the data flows we actually rely on to run y04 accounts. The policy is checked against account creation, login security, support handling and...

Account flow mapping

We map each privacy point against the account journey, from registration fields to login sessions. This helps us explain collection and retention without adding vague wording that does not match the product.

Rail reference handling

JazzCash, Easypaisa, SadaPay and Raast references are used to match account activity and reconcile requests. The policy separates those references from broader profile data so the purpose remains clear.

Access security checks

Device, IP and session signals help us detect unusual account access. We describe these checks because privacy needs to include the security layer that protects your account records.

Support desk controls

Support agents see only the details needed for the case in front of them. More sensitive account changes require extra checks before records are opened or edited.

Retention discipline

We keep account and transaction records for operational, legal and dispute handling needs, then reduce or remove data when it is no longer required for those purposes.

Plain English updates

When we change this Privacy Policy, we aim to explain the change in clear Pakistani English. The goal is for you to understand the effect before you continue using y04.

Consistency across legal pages

Our Privacy Policy sits beside account terms, cookie wording and support procedures. Each page covers a different duty, but the privacy meaning stays aligned: what data we collect...

Account terms link
Account terms explain what you agree to when using y04, while this Privacy Policy explains the data used to operate that agreement and protect account access.
Cookie wording link
Cookie wording deals with browser storage and tracking choices. This page connects those signals to account security, session continuity and service measurement where they involve personal data.
Support procedure link
Support procedures explain how requests are handled, while this page explains why support may ask for verification before discussing account history, rail references or profile changes.
Security wording link
Security wording describes controls around login and account access. This policy states which personal signals help those controls work and how we use them during investigations.
Rail processing link
Rail processing language explains account reconciliation through JazzCash, Easypaisa, SadaPay and Raast. This policy explains the related data purpose, access controls and retention approach.
Promotion records link
If a promotion appears in your account, related records may be stored to confirm eligibility and settlement. This policy explains that data use without turning promo rules into privacy terms.
Dispute file link
Dispute wording explains how a case is raised. This policy explains which account logs, messages and transaction references may be checked to answer that privacy-sensitive case.

Visible privacy layout elements

This page is arranged so you can scan the privacy points before creating or using your y04 account. The layout separates collection, purpose, sharing, retention, rights...

Clear policy headings

Headings show where account data, security signals, rail references and support records are discussed. You can move to the topic you need without reading unrelated service copy first.

Local rail chips

The rail chips name JazzCash, Easypaisa, SadaPay and Raast because those references may appear in account checks. Naming them makes the policy clearer for Pakistan account flows.

Request pathways

Contact cards show how to ask about access, correction or privacy concerns. Each pathway explains what we may verify before discussing records linked to your y04 account.

Purpose wording

Purpose wording tells you why a data category is used, such as account setup, security, support, reconciliation or legal handling. This reduces broad wording that can feel unclear.

Retention framing

Retention framing explains that records are not kept for one single period. Different account logs, support cases and transaction references may need different timeframes based on their purpose.

Update markers

When we adjust privacy wording, update markers help you see what changed. We avoid hiding important data handling changes inside unrelated page edits.

Common privacy questions answered

We collect account details, contact data, login activity, device signals and transaction references needed to run your account. We may also store support messages and verification outcomes when they relate to access or account changes.

JazzCash, Easypaisa, SadaPay and Raast references help us match account activity, answer reconciliation questions and investigate disputes. We use these references for account operations, not for selling your personal data.

We share data with service partners only when needed for hosting, security, support, account checks or rail reconciliation. Those partners receive limited details for the task and must handle them under agreed controls.

Contact us from the email or session linked to your y04 account and explain what needs correction. We may ask verification questions before changing records to prevent edits from the wrong person.

Retention depends on the record type and purpose. Security logs, support cases and transaction references may follow different periods because they support account protection, dispute handling and legal duties.

Yes, you can contact support with a privacy access request. We will verify the account connection, check what can be shared, and respond through a secure channel linked to your account.

Yes, the Privacy Policy applies when you access y04 from mobile browser, tablet or another supported device. Device signals may differ, but the privacy purpose and contact rights stay aligned.