LEGAL REFERENCE

Privacy Policy for x 900

x 900 sets out how we collect, use, store and protect your account data when you open an account, verify access or use local rails where local law...

Account dataVerification recordsJazzCash contextRaast handling
x 900 Privacy Policy for x 900

How we handle your data

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

CONTACT PATHS

How to reach us

Privacy questions need a clear route, so we keep contact paths separate from general account help. When you write to us, include...

Privacy email Use our privacy email path for access, correction...
Live chat handoff If you start through chat, our team can...
Security report Tell us quickly if you think account data...
POLICY CHECKS

How this policy stays current

We treat the Privacy Policy as an operating document, not a static page. It is checked when we change account fields, add a local rail, adjust verification steps or alter storage partners...

Plain wording

We avoid legal fog where possible and explain data use in direct language. If a clause affects your account, we describe the record involved, the purpose and the choice available to you.

Local rail mapping

JazzCash, Easypaisa, SadaPay and Raast references are mapped in the policy because those records can confirm transaction status. We identify them as payment references rather than treating them like game activity.

Access controls

Only trained staff with a work reason can see sensitive account records. Access is logged, permission levels are limited, and support screens hide data that is not needed for the request.

Storage checks

We check where account and verification records are stored before adding or changing tools. Hosting partners must support security controls, backups and restricted access aligned with our privacy commitments.

Change tracking

When the policy changes, we update the page date and keep internal records of what changed. Major privacy changes may also be flagged inside your account or through support channels.

Request handling

Requests are logged with dates, account identifiers and resolution status. This helps us answer consistently, avoid duplicate work and prove that privacy actions were completed by the assigned team.

Where this policy fits

x 900 keeps privacy wording aligned with nearby legal pages so you do not receive mixed messages. This page explains personal data handling. Other pages may describe service...

Terms page
Our terms explain account rules and permitted use, while this Privacy Policy explains the data behind those rules. If a rule requires identity checks, this page covers the record handling.
Cookie page
Cookie wording deals with browser storage, session tools and measurement tags. This Privacy Policy connects those signals to account privacy when they help protect login sessions or remember choices.
Security page
Account security material explains passwords, device checks and session alerts. This policy adds the privacy layer by stating what security records we collect and how long we keep them.
KYC page
Verification wording covers documents and checks needed to confirm account ownership. This Privacy Policy explains why those files are requested, who can access them and when removal may be limited.
Promotion terms
Promotional pages can mention eligibility data, but they should not expand privacy rules on their own. If personal records decide eligibility, the handling standard comes back to this policy.
Support scripts
Support replies use the same privacy positions shown here. Agents should not promise data actions outside this policy, and any unusual request is escalated before a final answer is sent.
Account screens
Forms inside your account should ask only for records linked to a clear purpose. If a field collects personal data, its use must match the Privacy Policy language.

Privacy page layout signals

We designed this legal page so you can scan it before opening an account and return to it later without hunting. Headings separate collection, use, sharing...

Date marker

A visible date marker helps you spot whether the Privacy Policy has changed. When we update data practices, the date gives you a quick way to decide what to read again.

Plain headings

Each heading is written around an action, such as collecting data or answering requests. That structure helps you move straight to the privacy issue affecting your x 900 account.

Local chips

Short chips call out Pakistan-specific record contexts, including JazzCash, Easypaisa, SadaPay and Raast. They are included so you can see where local account activity touches privacy handling.

Request cards

Contact cards separate privacy access, correction and security concerns. This keeps sensitive requests away from broad support threads and helps our team apply the right verification steps.

Short clauses

We keep clauses compact so you can compare what we collect with why we collect it. Longer legal points are split into smaller parts when they affect account choices.

Return path

Links from account and support areas should return you to this policy when personal records are discussed. That keeps the privacy position consistent while you move through x 900.

Privacy Policy questions answered

We collect account details, contact data, verification records, device signals, session activity and transaction references. The exact data depends on how you access x 900 and which account checks apply in supported regions.

Payment references help us match account transactions with rails such as JazzCash, Easypaisa, SadaPay and Raast. We use them to confirm status, investigate errors, answer requests and keep financial records accurate.

No. We do not sell your personal data. We may share limited records with processors, verification partners, payment partners, security tools or legal authorities when needed for the purposes stated in this policy.

Contact us through the privacy path with your account email or phone number. We verify identity first, then provide available records or explain if a legal, security or fraud-prevention reason limits disclosure.

Yes, you can ask us to correct inaccurate account data. Some fields may require fresh verification before we change them, especially where the record links to identity checks or transaction history.

We keep records only as long as needed for account operation, security, dispute handling, legal duties and audit needs. When those reasons end, we delete, anonymise or restrict records where possible.

We update the date on this page when the Privacy Policy changes. If a change materially affects how we handle your personal data, we may also flag it through account or support channels.