Terms of Use
Covers account conduct, acceptable use and what happens when an account breaks the rules. Questions about the data we hold route back to this page for the full answer.
This page sets out what dk9999 collects when you open an account in Pakistan, why we hold it, and how you get it changed or removed. It applies...
Here is our posture in plain terms. We collect only what an account needs: your name, date of birth, contact number, and the transaction records tied to your chosen rail. Those records verify who you are, settle withdrawals, and meet the bookkeeping duties that apply where local law permits. Access inside the company is limited to the teams that need it, and
every pull is logged. Where local law permits, we also process limited technical data such as device type, session length and approximate region to catch fraud and keep tables stable. We do not sell identifiers to advertisers. Retention follows the period regulators expect for account and transaction records in supported regions; after that, files are deleted or stripped of anything pointing back
to you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Need something corrected on your account record? Three routes reach the team that handles data requests, and each one hands back a reference number so you can follow the case without repeating yourself. Chat is fastest, email suits anything you want written down, and the in-account form keeps everything on one screen.
Our chat window runs around the clock from the help button in your account. Share the request, take the reference number, and the team that handles data matters picks it up the same day.
Write to the address listed under account settings. Describe what you want corrected, exported or removed, and we return a case ID. Never attach identity documents to that first message; we will ask through a secure link.
The settings panel holds a data request form. Choose export, correction or deletion, confirm with your password, and watch the status change on the same screen. No phone call is needed at any stage.
You should be able to see who writes a policy like this and how it stays current. These are the working habits behind the page: named ownership, dated edits, plain-language checks, yearly...
One internal team owns this document and answers for it. Their role sits on the page footer, so you know exactly who to address when a sentence looks unclear or out of date.
Every edit carries a date and a short reason. Scroll to the bottom for the running list, so you are never left guessing whether the wording shifted before your last visit.
Legal drafting gets rewritten before publishing. If a paragraph needs a dictionary to follow, it goes back to the editor until someone reading on a phone can understand it first time.
Independent firms test our account controls each year, checking how access is logged, how long deletion requests take, and whether the process matches what this page promises.
Pakistani advisers read every revision against the rules that apply here. That is why the text names supported regions instead of pretending a single law covers every account.
Spotted something inaccurate or stale? Send it through support. We correct the page, then log the fix with a date so the next person reading it sees an accurate version.
We keep our policy set aligned, so a rule you read here is not contradicted three clicks away. These are the pages this one sits beside, and what each of them covers...
Covers account conduct, acceptable use and what happens when an account breaks the rules. Questions about the data we hold route back to this page for the full answer.
Explains the small files that keep you logged in and measure page speed. Each tracking category is listed with a switch beside it, matching the controls on this page.
Sets the verification steps before funds move to JazzCash or Easypaisa. The identity records requested there are the same ones described here, so nothing new appears late.
Covers password rules, two-step sign-in and device alerts. It shares the same incident reporting channel as this document, which keeps a single route for anything data-related.
Describes how promotional offers are credited, when they expire and what is collected to run them. Any data those offers touch stays inside the scope set on this page.
Lists what counts as abusive play and how we act on it. Findings are logged the way account access records are, with the same retention window applied.
Shows the escalation order when a data request is not answered to your satisfaction, including the outside body you can approach here in Pakistan once internal steps are exhausted.
Before you scroll further, here is what you can actually see and use on this page. Every block below is built so you can act on a data...