LEGAL REFERENCE

How yyy9 handles your data

yyy9 keeps your account privacy, device checks and payment records under one clear policy for Pakistan access where local law permits. Open your account when ready, and you...

Account data scopeDevice safety checksPakistan payment recordsPrivacy contact paths
yyy9 How yyy9 handles your data

Privacy terms for Pakistan access

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

PRIVACY HELP

Contact paths for privacy requests

If you want to ask about your data, correct account details or request a copy of records we hold, use the contact...

Privacy email Send data access, correction or deletion requests to...
Live chat privacy queue Use live chat for quick questions about what...
Payment record support For JazzCash, Easypaisa, SadaPay or Raast privacy queries...
POLICY CHECKS

How we keep the policy reliable

Our privacy text is maintained by teams that run account operations, security checks and support handling for yyy9. We check the wording when product screens change, when a payment flow changes, or...

Operational ownership

Account, support and finance teams feed changes into this policy when data fields change, so the wording reflects the records we use during verification and withdrawal handling.

Security input

Our security team checks language around device signals, login records and unusual account activity, making sure privacy wording matches the controls used to protect your account.

Payment flow checks

When JazzCash, Easypaisa, SadaPay or Raast matching steps change, we update the policy text so you know which transaction details may be kept.

Support feedback loop

Common privacy questions from email and chat are tracked internally, then used to make explanations clearer without adding claims that do not match our process.

Retention mapping

We connect each data category to a retention reason, such as account security, finance records or dispute handling, and remove records when the reason expires.

Change records

Policy edits are logged with the reason for the change, the affected data area and the team that requested it, creating a clear internal trail.

Where this policy connects

This Privacy Policy works beside other yyy9 legal pages, but it stays focused on personal data. If another page explains account rules, cookies or promotions, this page explains...

Account termsThe account terms describe what you agree to when using yyy9. This policy explains the personal data linked to those account actions and support checks.
Cookie pageThe cookie page explains browser storage and tracking choices. This Privacy Policy connects those signals to account protection, analytics and session management.
Promotions pageWhen you check offers, we may record eligibility, opt-in status and reward history. This policy explains how those records are used and retained.
Payment pagesPayment screens show transaction steps. This policy explains how references from JazzCash, Easypaisa, SadaPay and Raast connect to your account record.
Support pagesSupport pages explain how to contact us. This policy explains how chat logs, email records and verification replies are stored and protected.
Security pagesSecurity pages describe account protection tools. This policy explains the login, device and risk signals we may process to secure access.
Update handlingWhen one legal page changes a data-related process, we check this Privacy Policy so the same meaning appears across connected pages.

Policy cues you can see

We place privacy cues near the areas where your data is collected, not hidden far from the action. Account forms, verification prompts, chat uploads and transaction...

Form labels

Account fields use plain labels, so you can see whether we ask for contact details, identity checks or security data before you submit a form.

Verification prompts

When extra checks are needed, prompts explain the purpose before you upload documents or confirm details, helping you connect the step to account protection.

Chat upload warnings

Support chat reminds you to share only the document or reference requested. This limits unnecessary data and keeps private material inside the right case.

Session messages

Login and session messages may mention device checks or location signals, so you understand why access can be challenged when something looks unusual.

Preference controls

Where account preference controls are available, we label them clearly and link them to this policy so you know how choices affect your data.

Policy links

Privacy links appear on account, support and transaction screens, placing the policy close to the data request that made you look for it.

Questions about your privacy

We collect account details such as your name, phone number, login credentials, device data and verification records. We use them to create access, protect your account and support withdrawals where local law permits.

We keep the transaction reference needed to match your account record, confirm a payment trail and answer support queries. We do not need your full wallet history for this process.

Yes. Email [email protected] with your account name and registered phone number. We will verify your identity before sharing records, so private data is not sent to the wrong person.

Retention depends on the record type. Account security, finance matching and dispute handling may require different periods, and we remove or anonymise records when there is no valid reason to keep them.

We share data only where needed for account operation, security checks, payment matching, legal duties or support handling. Service providers must handle the data for the task we assign.

Contact support or email the privacy address with the detail that needs correction. We may ask for proof before changing sensitive records such as phone numbers, identity fields or payment references.