LEGAL REFERENCE

How xs999 Handles Your Privacy

Your privacy policy sits at the centre of how we run xs999 for Pakistan. It sets out what we collect when you open an account, how your JazzCash...

Data you controlPlain-English clausesLocal payment contextUpdated with you in mind
xs999 How xs999 Handles Your Privacy

Scope Of This Policy In Pakistan

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

REACHING US

Talk To Us About Your Data

Privacy questions should reach a person, not a void. Our support desk answers account-data queries in English from morning to late evening Pakistan time, seven days a week. Tell us which record you want corrected and we confirm the outcome in writing.

Team online

In-App Live Chat

Open the chat window from your account menu to raise a privacy request. A named agent picks it up, so you follow one thread instead of repeating your details to a new person.

Email Records

Send written requests to our support mailbox and keep the reply for your own files. We answer within one working day and confirm which records were amended.

Account Settings

Update contact details, device lists and consent choices inside your profile. Anything you switch off there stops future collection and leaves a dated entry you can check yourself.

EDITORIAL STANDARDS

Who Drafts And Checks These Clauses

Our privacy wording is drafted by the operations team that handles account data daily, then checked by an independent data adviser before publication. We date every amendment and say plainly what changed...

Named Data Officer

One accountable person signs off every privacy change at xs999. You can ask for their role and the date of the last sign-off and get a straight answer, not a ticket number.

Independent Advice

We brief an outside data adviser on how funds move through JazzCash, Easypaisa, SadaPay and Raast, then apply their points before any wording goes live for Pakistan.

Version History

Every published copy carries a date. Earlier versions stay available on request, so you can compare what applied when you registered with what applies now.

Plain Language Rule

We avoid legal padding. Where a clause needs a technical term, we explain it in the same paragraph so you do not need a second tab to understand your own rights.

No Lifted Templates

These clauses were written for xs999 and our supported regions. We do not paste in another operator's template, which is why the wording matches how our account flow behaves.

Reader Feedback Loop

If a sentence still reads like fog, write to support and it returns to the drafting queue. Several current clauses began as reader complaints about unclear phrasing.

How This Page Matches Our Others

This privacy policy is one of several documents describing how we run xs999. Our terms of use, cookie notice and account security pages share the same definitions, so...

Same Definitions
Any term defined here carries the same meaning on our terms of use, cookie notice and account security pages, so you never guess which version of your data applies.
Terms Of Use
The terms of use explains how you hold an account and what we expect from each other. This policy covers the records behind that account and sits alongside it.
Cookie Notice
Device-level detail such as session cookies and analytics tags lives on the cookie notice. Here we cover the purpose and your choices, not individual browser strings.
Account Security
Password rules, device checks and sign-in alerts belong to the security page. We cross-reference them instead of repeating them, so a change lands once and updates everywhere.
Withdrawal Records
How a payout request is verified and logged is set out on the withdrawal page. Here we explain who can see that record and how long we hold it.
Language Versions
Our English wording is the reference text for supported regions. If a translated copy drifts from it, the English version decides and we correct the translation at the next pass.
Aligned Change Dates
When a definition changes, the update date moves on every sibling page in the same release. Check any two pages and you should see the same revision date.
WHAT YOU CAN SEE

The Layout You Read On This Page

A policy should be easy to move around, so this page is built for how you actually read. A contents strip stays with you as you scroll, the...

Sticky Contents Strip A slim contents bar follows you down the page and...
Revision Date Banner The revision date sits above the first clause rather than...
Summary Boxes Each long clause opens with a two-line plain summary. Read...
Rail Chip Row A chip row names the rails your records may reference...
Print And Save View One button produces a clean copy with the date and...
Contact Panel The support panel closes every clause group, so a question...

Privacy Questions You Send Us

Your registration details, the contact addresses you give us, device and sign-in records, and transaction references created when you move money through JazzCash, Easypaisa, SadaPay or Raast. Nothing is collected before you submit the form.

No. We share records only with the processors needed to run your account, such as payment and verification partners, and only as far as the task requires. We do not trade contact lists or profile data.

Account details stay while your account is open. After closure we keep transaction references for the period our accounting and audit duties require, then delete or anonymise them. Ask for the exact timeframe on your file.

Yes. Ask through chat or email and we confirm what is on file, where it came from and who it has been shared with, inside the response window that applies in your supported region.

Dormant accounts keep their data, but marketing messages stop once you switch them off in settings. Reactivating later restores your preferences, including any consent choices you had already changed.

Some fields you can edit yourself in your profile. For anything locked, such as a verified name, send the correction with supporting context and we update the record and confirm it in writing.