LEGAL REFERENCE

Privacy Policy For Your jk999 Account

jk999 keeps one privacy policy for the whole platform, and this page explains it in plain Pakistani English. Read how we collect account details, where your data sits...

Account Data ExplainedPlain Pakistani EnglishControls You Can UseUpdated As Rules Shift
jk999 Privacy Policy For Your jk999 Account

How We Handle Your Account Data

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

REACH THE DESK

Reaching Our Privacy Desk

Our privacy desk runs seven days a week, 9am to 11pm Pakistan time, and answers in English or Urdu. Use live chat inside your account panel for anything urgent; email works better for written requests you want on record. Both routes reach the same small team.

Team online

Live Chat Desk

Open live chat from your account panel and a privacy agent picks up the thread within a minute. Share your registered email so we can pull the right record.

Privacy Email

Write to our privacy mailbox about deletion requests, data copies or consent. We verify your identity before releasing anything, then reply in two working days.

Account Settings

Inside your account you can see which details we hold, change your contact number and switch off optional messages. Switching them off never affects payment or security notices.

WHY YOU CAN CHECK

Why Our Privacy Terms Stay Clear

Clause wording on this page goes through a small internal check before it goes live: the data owner signs it, a second reader tests it for plain English, and we log the...

Named Policy Owner

Every wording change on this page is signed off by the person who runs our data desk, so you always know who to question when a clause reads oddly.

Version History

We keep each past wording of this policy on record. When a clause changes, the new text goes live and the older one stays available. Request it from our desk.

Plain Language Pass

Before a clause ships, we read it back as a customer would and cut legal padding. If a sentence needs two readings, we rewrite it until one pass is enough.

Rails Data Map

Our policy names which payment partner sees what. JazzCash, Easypaisa, SadaPay and Raast each receive only the fields needed to settle your transfer. Nothing beyond that is handed over.

Retention Schedule

We publish how long each data type stays with us: payment records follow Pakistan tax timelines, while marketing preferences are deleted once you close the account. Sign-in logs clear sooner.

Escalation Path

If a reply from our desk does not settle your concern, ask for a written escalation and a senior agent takes over the same thread within three working days.

CONSISTENT POLICY PAGES

The Same Rules On Every Policy Page

Every policy page of ours follows the same structure: a short summary, the full clause, then a date stamp. Move from this page to our cookie notice or terms of use and...

01

Cookie Notice

Our cookie notice covers browser storage while this policy covers account records. Read them together and you see everything we keep on you. Both sit in the footer.

02

Terms of Use

The terms of use handle account conduct and payouts, while this policy handles data. Where the two touch, both quote identical retention timelines and numbering. Move between them mid-read.

03

Account Rules

Account rules explain what pauses your access. The privacy side explains what we store when that happens, and how long a closed record stays on file. The wording style is shared.

04

Verification Checks

Identity checks described in our verification wording follow the same data rules you read here. Nothing gathered during a check is used beyond your account. Ask the privacy desk if one stalls.

05

Complaints Route

Complaints follow the timeline printed on this page too. You get an acknowledgement the same day and a written outcome once the data question is resolved. Ask for the reference number.

06

Data Retention

Retention wording stays identical across our policy pages, so a payment record is kept the same number of years whichever page you open first. Switch pages mid-read and nothing shifts.

07

Policy Updates

Each update carries a date stamp and a short line on what moved, so you can spot a change without rereading every clause. Older wording stays on record.

POLICY PAGE LAYOUT

What You See On This Page

This page keeps its structure deliberately simple: a jump list, a plain summary under each heading, a date stamp, and a chip row naming the rails the policy...

Anchor List A short jump list sits above the first clause so...
Plain Summary Box Each long clause opens with a two-line summary in everyday...
Version Stamp A date stamp sits under every heading, showing when that...
Chip Row The payment chips under our hero name the rails this...
Contact Block A contact block closes the page with chat, email and...
Print-Friendly Text Long clauses stay readable when printed or saved as a...

Privacy Questions, Answered Plainly

Your email, mobile number, date of birth and country, plus the payment reference for each JazzCash, Easypaisa, SadaPay or Raast transfer. Sign-in logs and device details sit alongside those records.

Yes. Message the privacy desk from your registered email and we compile a copy covering account records, payment references and sign-in history, usually within two working days. There is no charge for that.

No. We share only what a payment partner needs to settle a transfer, or what a regulator can lawfully request in a supported region. Nobody buys your record from us.

Payment references follow Pakistan tax timelines, so expect several years of storage. Sign-in logs clear after ninety days, and marketing preferences disappear once you close the account. Ask the desk for exact dates.

We pause access straight away, stop optional messages, then keep only the records a Pakistani payment trail requires. Everything else is deleted on a fixed schedule you can ask us to confirm.

Yes. We stamp the date, summarise the moved clause in one line, and post a note in your account panel. Older wording stays on record if you need to compare.