Cookie wording
Our cookie page explains browser storage and tracking choices, while this Privacy Policy explains the personal data linked to those signals. Together they show what is stored and why it matters.
LEGAL REFERENCE
90x Privacy Policy For Pakistan
90x keeps one Privacy Policy for account, lobby, and payment data, so you can see what we collect before you open your account. We explain JazzCash, Easypaisa, SadaPay...
Account data explainedPakistan privacy wordingPayment data contextSupport contact paths
How We Handle Your Data
This Privacy Policy explains how 90x collects, uses, stores, shares, and deletes data linked to your account where local law permits access. We ask for account details, security signals, device records, payment references, and support messages only when they help us run your account, verify activity, answer privacy requests, or meet legal duties in supported regions. We do not sell your personal
data. Some checks use service partners that process data for identity, fraud screening, hosting, analytics, and transaction matching. When you open your account, you should read this page alongside our cookie and terms pages so you know how your privacy choices fit the full account flow.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY CONTACTS
Ways To Reach Privacy Support
Your privacy request should reach the right desk without being passed around. Use these contact paths when you want to ask what data we hold, correct account details, raise a security concern, or ask how transaction records are kept. We may ask for account verification before acting on any request.
Team online
Privacy inbox
Send your privacy request through the account help area and choose the privacy category. Include your account name, the request type, and any relevant payment reference so we can trace the right record.
Live chat handoff
If you start in chat, ask our team to move the case to privacy handling. Chat staff can confirm receipt, but they will not disclose sensitive account data inside an open chat window.
Security escalation
Use the security route if you think your account data or payment references were exposed. We lock sensitive changes while we check the case and may request fresh identity confirmation.
POLICY CARE
Signals Behind This Privacy Page
We write this Privacy Policy from our own account flow, not from a template sitting away from the product. The policy reflects how sign-in, payments, support, device security...
Local wording
We use plain Pakistani English and name local rails such as JazzCash, Easypaisa, SadaPay and Raast where they create privacy...
Account checks
We explain why identity and login checks may be needed before privacy requests are completed. This protects account records from...
Transaction trace
We describe transaction references as privacy data, not just finance records. A payment code, timestamp, wallet name, or Raast reference...
Device signals
The policy covers device and session signals because they help us detect unusual access. We use them to secure your...
Partner limits
Where partners process hosting, analytics, payment matching, or fraud checks, we keep their role tied to service delivery. They are...
Change tracking
When the Privacy Policy changes, we adjust the date and wording so you can see what has moved. Material changes...
PAGE CONSISTENCY
Same Privacy Language Across Policy Pages
Our legal pages should not conflict with one another. This section explains how the Privacy Policy sits beside cookie, terms, support, and security wording on 90x. If another page discusses data use...
Terms wording
Terms explain account rules, while this Privacy Policy explains the data used to run those rules. If verification is mentioned there, this page describes the privacy handling behind it.
Support wording
Support pages describe how to contact us, while this Privacy Policy explains what we do with messages, attachments, chat logs, and identity checks sent through those contact routes.
Security wording
Security wording explains account protection steps, while this Privacy Policy explains the device, session, and verification data used for those steps. Both pages should read as one account process.
Payment wording
Transaction pages may mention JazzCash, Easypaisa, SadaPay and Raast flows. This Privacy Policy explains the personal data attached to references, matching checks, timing records, and support disputes.
Access wording
Where access is offered in supported regions, this Privacy Policy explains the data needed to open, maintain, restrict, or close an account. The same privacy standards apply across those account states.
Retention wording
Retention language stays aligned across pages. We keep account and transaction records only for valid service, security, legal, or dispute reasons, then remove or anonymise them when no longer needed.
LAYOUT MARKERS
Privacy Layout That Keeps You Oriented
This Privacy Policy is arranged so you can scan it quickly before opening your account or sending a request. The visible page elements separate legal wording from practical...
Clear date marker
The page carries a visible update date so you can...
Data category labels
Account, transaction, device, support, and security data are separated into...
Purpose blocks
Each data purpose is written as a short block, such...
Choice prompts
Where you can act, the page points you toward a...
Partner labels
Service partners are described by role, such as hosting, analytics...
Contact placement
Privacy contact routes appear before the FAQ so you do...
Common Questions About Your Privacy
We collect account details, login records, device signals, transaction references, support messages, and verification material when needed. The exact data depends on what you do in your account and which privacy request you make.
JazzCash, Easypaisa, SadaPay and Raast references help us match transactions to your account, resolve support cases, and keep records accurate. We treat those references as personal data when they identify you.
Yes. Send a privacy request through the account help area and state that you want access to your data. We may verify your identity first so records are not released incorrectly.
Use the privacy contact path and explain which detail is wrong. We may ask for proof before changing sensitive fields, especially where the correction affects payment matching or account security.
We keep data for service, security, legal, and dispute reasons. Retention length depends on the record type, local requirements, and whether an open support or transaction issue still needs that record.
Some partners process data for hosting, analytics, security screening, support tooling, or transaction matching. They receive only what is needed for their role and must handle it under service instructions.
Cookies and similar tools may create device or session data. Our cookie page explains browser controls, while this Privacy Policy explains how related data is used for account security and service operation.