Terms Of Use
The terms page covers what you and we agree to when you open an account. Anything about how records are held, shared or deleted sits here instead.
LEGAL REFERENCE
How pk38 game Handles Your Account Data
Open an account and this policy tells you exactly what we record, why we record it, and how long we keep it. We wrote it in plain English...
Account Data You ControlPlain-English ClausesWallet References MaskedSupport You Can Reach
Where Local Law Sets The Rules
We hold your account details under the rules that apply where you live. In Pakistan, that means records are kept, stored and shared only where local law permits, and where a request falls outside those rules we tell you before anything moves. Payment references from JazzCash, Easypaisa, SadaPay, NayaPay and Raast are stored as transaction identifiers rather than full wallet credentials, so
a support agent can trace a deposit without ever seeing your wallet PIN or one-time code. Where you open the account from a supported region, the same standards apply to identity checks, device logs and chat history. If you travel or move, some parts of this policy may work differently for you, and we say so at the point the difference matters
rather than burying it. You can ask us to correct, export or close a record at any time, and we answer those requests through the contact routes below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY SUPPORT
Reaching The Team About Your Data
Privacy questions do not sit in a queue behind gameplay queries. When you write to us about your data, we route it to the team that handles account records, and we tell you which person is holding it.
Team online
Live Chat Desk
Open the chat window from your account and a privacy-trained agent picks it up. Chat runs daily, and any transcript we keep is stored against your profile so you never repeat yourself.
Email Records Desk
Write to the address shown inside your account settings and include your registered number. Email suits data requests that need a written trail, such as correction, export or deletion.
In-App Request Form
Send a request straight from the settings screen and it lands in the same queue as chat and email. You get a reference number so you can follow it up later.
DATA PRACTICE
Who Writes And Checks This Policy
This page is maintained by the same team that runs account operations, not an outside copywriter. Every change is dated, checked against how our systems actually behave, and pushed live only after...
Checked By Operations
The account team that handles your deposits and withdrawals reads each update before it goes live, so the wording matches what actually happens when you use JazzCash or Raast.
Dated Change Log
We stamp every revision with the date it took effect, so you can see when a clause changed rather than guessing from a version number. Older wording stays available on request.
Plain-English Drafting
Clauses are written so a reader without a legal background can follow them. Where a term has to stay technical, we add a short line beneath it explaining what it means for your account.
Security Checks
Account access runs over encrypted connections, and sensitive fields such as wallet numbers are masked on screen. Session logs help us spot unusual sign-ins before they turn into a problem.
Support Hours Shown
Our contact windows are listed inside your account rather than hidden in small print, so you know when a privacy request will be picked up by a person rather than an auto-reply.
No Data Selling
We do not sell your account records to third parties. Sharing is limited to the processors that keep payments, identity checks and messaging running, and each one is bound to the same standards.
PAGE CONSISTENCY
How This Page Lines Up With Our Others
Our terms, cookie notice and payment pages all speak with one voice, and each one points back here when the subject is data. If two pages ever appear to disagree, this policy...
Cookie Notice
Cookies keep you signed in and help us measure which lobby screens load slowly. The cookie page covers each category; this policy explains who can see the data behind them.
Withdrawals Page
That page walks through payout timing and verification steps. This policy explains why we hold proof-of-account documents, who can open them, and when they are removed.
Accessibility Statement
Both pages stay readable across screen sizes and assistive tools, and we avoid jargon where a plain phrase works. That standard applies here as much as anywhere else on the site.
Account Settings
Settings is where you change a number, add a device or close the account. Each action is mirrored by a clause here, so you can see what happens to the record afterwards.
Complaints Route
If you think a data decision went wrong, the complaints route takes priority over the general queue. We acknowledge the message, name the handler and give you a date for the reply.
Contact Page
The contact page lists every channel in one place. Privacy requests sent there are tagged on arrival so they reach the data team rather than the gameplay desk.
ON THIS PAGE
What You See On This Page
Six blocks carry the weight here: the opening summary, the jurisdiction clause, the contact routes, the editorial checks, the cross-page links and the question list below. Each one...
Anchor Row
A single row of jump links sits under the headline...
Summary Panel
The first panel condenses the whole policy into a few...
Chip Row
Small chips name the rails tied to your account history...
Definition Blocks
Where a term could be read two ways, we bold...
Update Banner
A thin banner appears whenever the wording changes, showing the...
Print And Save
Every block prints cleanly and keeps its numbering, which matters...
What You Ask About Your Data
Your name, contact number, date of birth and the wallet or bank details you use to move money. We also log device type, sign-in times and pages visited so we can spot unusual activity.
Only with processors that keep the service running, such as payment partners and messaging tools. Where local law permits, we name those categories in the clause and never sell a record.
Active accounts keep records for as long as you hold them. After closure we retain a smaller set for the period local rules require, then delete it, unless a dispute is still open.
Yes. Send an export request from your account settings or through our support channels and we compile the file, usually within a few working days of verifying the account.
No. Each rail creates a transaction reference and a status, and we store both the same way. Full wallet credentials, PINs and one-time codes never reach our records.
Changes are dated and posted here, and material shifts come with a notice inside your account. Continuing to use the service after that date means you accept the updated wording.