LEGAL REFERENCE

Your Account Data, Explained Clearly

This page explains what happens to the details you hand over when you open an account with dk99 game. We keep the list short, we say why each...

Account data kept shortWhy each field is neededAsk for a copy or correctionWording updated when practice shifts
dk99 game Your Account Data, Explained Clearly

How We Handle Your Data In Pakistan

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

PRIVACY DESK

How To Reach Our Privacy Desk

Questions about your record do not need a ticket number. Message our privacy desk from the chat inside your account, or write from the email address you registered so we can match you to the right file. Support runs through the day, every day, in English, and we confirm every data request in writing once the team closes it.

Team online

Live Chat

Open chat inside your account and tell the agent you have a data question. The thread is routed to the privacy desk and stays open until someone answers you properly.

Email Request

Write from the email address on your account so we can confirm identity before we act. We ask for the minimum needed to locate your file and nothing more.

Support Window

Our desk runs through the day, every day, in English. Requests sent outside the window queue for the next shift, and you receive a written outcome rather than a spoken one.

WHY IT HOLDS

The Work Behind This Wording

This text is drafted by the same team that runs account verification, payments and support for Pakistan, so each clause reflects something we genuinely do. When a payment rail, a security step...

Policy Drafting

Clauses are written by people who handle account verification and payment reconciliation daily, then checked against what our systems actually log so nothing is promised that we cannot deliver.

Rail Knowledge

We document exactly how JazzCash, Easypaisa, SadaPay, Raast and NayaPay references are stored, which keeps the wording you read grounded in real payment rails rather than broad statements.

Regional Wording

Rules differ between provinces and supported regions, so we say plainly that local law leads, and we name the situations where a request from you may be limited.

Security Practice

Access to account records is restricted to named roles, sign-in sessions are logged, and encryption covers data in transit and at rest, all of which we describe here.

Retention Schedule

Transaction history, verification files and chat transcripts each carry a set lifespan. Once that period closes, the record is removed from live systems on a scheduled job, not left to drift.

Plain Language

We avoid legal padding. Every heading answers one question, and where a term needs defining, the definition sits in the same paragraph so you never have to search for it.

Matching Terms Across Sibling Pages

Our policy pages share one set of definitions, so a term you read here means the same thing on the terms page, the account page and the payments...

Shared Definitions
Terms such as account record, verification file and retention window carry one meaning that holds across every policy page we publish, so nothing shifts when you move between them.
Payments Page
The payments page covers rail timings for JazzCash, Easypaisa, SadaPay, Raast and NayaPay. Data handling for those rails stays here, using the same labels and rail names.
Account Page
Sign-in, device checks and profile edits are described there in the language used here, so a security clause reads identically in both places rather than being reworded.
Terms Page
Eligibility, one-account-per-person and closure rules sit on the terms page. Where those rules touch your data, this page points to them directly without repeating the full clause.
Cookie Page
Session and preference cookies are listed separately, and each entry names what it stores and how long it lives, using the labels you see on this page.
Support Page
Contact routes, desk hours and escalation steps appear on the support page, mirroring the privacy desk details written above, so you reach the same team whichever page you start from.
Update Discipline
When one page changes, we check the others for knock-on edits in the same pass, which keeps dated wording consistent across the whole set rather than drifting apart.
PAGE HIGHLIGHTS

Elements That Shape This Policy Page

Everything here is built for quick reading on a phone. Headings carry one idea each, cards group related points, and the questions below cover what our desk is...

Short Headings Each heading covers a single idea, so you can scan...
Grouped Cards Related points sit together in small cards instead of one...
Recognisable Labels We name the things you know — JazzCash, Easypaisa, SadaPay...
Defined Terms Where a word carries legal weight, we define it in...
Version Date A date stamp sits above the first heading whenever the...
Local Focus This page is written for Pakistan in plain English, with...

Privacy Questions We Answer Often

Your name, mobile number, date of birth and the payment handle you register, plus the verification file you send. Each item is needed to confirm identity and keep one account per person.

We do not sell personal data or pass it on for outside marketing. Payment rails see only the reference needed to clear a transfer, and nobody else opens your file.

Transaction logs stay for the period our auditors require, then a scheduled job removes them. Verification files and chat transcripts follow shorter windows, both set out above.

Yes. Message the privacy desk from inside your account and we compile what we hold, confirm who you are first, then send it to you in writing.

You can close your account at any time. Records tied to completed payments stay until the audit window closes, then they are deleted, and we confirm that to you in writing.

We publish the new wording on this page with a fresh date stamp. Where a change affects your choices, we message you before it takes effect so you can respond.