Terms Of Use
The terms page covers account rules, closures and disputes. This policy covers your data only, so open both if you want the complete picture of how we run accounts.
When you open an account on py999, you hand us a small set of personal details. This page explains what we keep, why we keep it, and how...
This policy applies wherever you use py999 in a supported region and local law permits. It covers the details you give when you open your account, the payment references our Pakistani rails return, and the device data our app records. It does not cover third-party sites you reach from our lobby. Where provincial or national law gives you stronger rights over your
data, those rights apply instead. Keep your contact email current so notices actually reach you. If a clause does not sit right with you, close the account from settings and ask us to erase what we no longer need.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Data questions go to a live desk rather than a queue that never closes. Use whichever channel suits you and quote the email tied to your account so the team can pull the right record without extra back-and-forth. We answer in English or Urdu, and every request gets a reference number you can follow up on later.
Write to our privacy desk from the address tied to your py999 account. Replies usually land within one working day, Monday to Saturday, in English or Urdu, whichever you prefer.
Open the chat bubble inside your account and ask for the data team. Chat runs from nine in the morning to eleven at night, Pakistan time, seven days a week.
Export a copy of your account data, correct a phone number we have wrong, or close the profile outright from your own settings page, without waiting on a reply.
Someone who works on the platform writes this page, and a second person checks it before it goes live. That matters for a policy, because the wording has...
Every line here is written by the py999 operations team, people who work with our account systems daily, rather than...
Our compliance lead reads the text before it goes live and signs off again after each edit, so the published...
Each release carries a signature from the person who approved it, so there is always a name behind a change...
Short sentences, one idea each, and no clause that hides a data practice behind vague wording. Where legal language is...
Our examples use the rails you actually use here: JazzCash, Easypaisa, SadaPay, NayaPay and Raast, not card networks that never...
If a paragraph reads oddly or a link is stale, email the privacy desk. We fix the wording in the...
This policy is one page in a set. Each sibling page owns a single topic, and we keep the definitions, the region wording and the contact routes identical across all of them...
The terms page covers account rules, closures and disputes. This policy covers your data only, so open both if you want the complete picture of how we run accounts.
Cookies live under their own notice, which names every tag we run. Blocking them keeps your account working, though the lobby will load more slowly on mobile data.
Payment handling sits on a separate page and names JazzCash, Easypaisa, SadaPay and Raast. Here we explain only what data those rails hand back to us each time you move money.
Bonus conditions are published separately. Where a promotion needs your data for verification, that page links back here rather than repeating the same clauses in different words.
Identity checks are described on the verification page. The same wording about supported regions and local law appears on both, so neither page contradicts the other.
Closing your profile gets one short page. What happens to stored data afterwards is handled here, in the retention paragraph further down this page. Read them together.
If you disagree with how we answered a data request, the complaints page sets out the escalation order, and the same inbox stays open for you throughout.
Before you read the full text, the page itself gives you a few handles: a version stamp, a short summary strip, a table of what we...
A date and version code sit above the headline. Compare them with the footer copy on your next visit and you will see at once whether anything changed.
Six short lines sit under the hero, so you can scan the main points about data handling before deciding whether the full text deserves your time today.
Toggle between English and Urdu from the corner of the page. Both versions carry the same meaning, and if they ever differ, the English text is treated as binding.
One table lists what we hold, why we hold it and how long it stays. No column is left blank, so nothing quietly hides in a footnote at the bottom.
A pinned card shows the privacy inbox, chat hours and our Pakistan working days, then repeats at the foot of the page for anyone who scrolled straight down.
A short list of past edits, newest first. When we alter how long payment references are kept, the entry says so in one plain sentence you can actually follow.