Account Terms
The terms page covers what you agree to when you open an account, while this policy covers what we do with the details that agreement creates, and both are meant to be read together.
LEGAL REFERENCE
How dream 9999 Handles Your Account Data
This page sets out what we collect when you open your account, why we hold it, and the choices you have. It is written in plain Pakistani English...
Plain-English policy textRegion-aware retentionDated change log
Where Local Law Permits, We Apply This Policy
We treat this policy as the baseline for every account, though the exact rules move with the region you sign in from. Where local law permits, we keep account data inside the operating region and apply the retention window that region sets; supported regions outside Pakistan may run on a shorter or longer clock. Transfers clear through JazzCash, Easypaisa, SadaPay, NayaPay and
Raast, and each rail returns a reference we log against your account, so a later query can be traced without holding your full banking details. If a rule in your jurisdiction asks for something different, that local requirement wins. Nothing here overrides a legal duty we hold where your data sits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
ACCOUNTABILITY CHECK
How We Keep This Policy Accountable
Credibility on a policy page comes from showing the work. We name the team that owns this text, date every change, and tie each claim about your data...
Policy Owner
This text is maintained by our account operations team in Pakistan, the same people who handle JazzCash and Easypaisa payment...
Dated Change Log
Every amendment to this page is dated and summarised where it appears, so you can see what moved since your...
Data Category Map
We list the categories we hold, identity, contact, transaction reference and session logs, next to the reason each exists, which...
Plain Language Pass
Before a clause lands here we strip jargon that leaves the meaning unchanged; if something cannot be explained in a...
Role-Based Access
Account access runs on encrypted sessions, two-step verification for sensitive changes, and staff permissions tied to a job role, so...
Verification Path
You can request a copy of the data tied to your account and compare it with what this page claims...
CONSISTENT ACROSS PAGES
How This Policy Lines Up With Our Other Pages
Our policy, account terms and payment pages describe one system from different angles. Read them together and they should not contradict each other; spot a gap, tell us, and we will reconcile...
Transaction Pages
Those pages explain how JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers clear; here we only describe the reference data those rails return and how long we keep it.
Support Routes
Support lists every contact route in full; on this page we flag which of them accept a data request, so you are not guessing which channel reaches the right desk.
Security Controls
Security explains session handling and two-step verification; this policy inherits those same controls instead of defining a competing set of rules, so the two read as one system.
Lobby Behaviour
Lobby pages describe games and markets and never ask for more than an account session needs; whatever they do record falls inside the categories listed on this page.
Cookie Notice
Where a separate cookie notice applies, it expands on the session and preference cookies summarised here; the same retention clock governs both, so nothing outlives the window we state.
Release Alignment
When a sibling page changes in a way that touches your data, this policy is updated in the same release cycle, so you never read two documents describing different practices.
INSIDE THIS PAGE
What You Will Find Across This Policy
We laid this page out so you can scan it rather than read it end to end: a short summary first, category blocks through the middle, and plain...
Plain Summary Block
The opening block gives you the short version before the...
Category Blocks
Each block names one category of information, identity, contact, transaction...
Reference Row
A compact row shows which rails feed transaction references into...
Retention Timeline
One timeline shows how long each category survives after an...
Your Control Panel
A single block maps your controls, copy request, correction and...
Straight Answers
The closing block answers the questions we get most about...
Questions About Your Data and This Policy
It covers account identity details, contact details, the transaction references your JazzCash or Easypaisa payments generate, device and session logs, and any support messages you send us.
No. When a transfer clears through Raast or SadaPay we store a reference number and a status, not your banking credentials; that reference is enough to trace a query later.
Session logs drop on a short clock, while transaction references stay for the period local accounting rules require. The retention timeline on this page lists each category with its own window.
Yes. Raise a request from the privacy tile in your account settings or email the privacy desk, and we reply with the categories tied to your account and the reason each is held.
Access is role-based and logged. Payment operations see a transaction reference, support sees your ticket history, and anything wider needs a recorded reason and a second staff check.
It can change when a rule in your region shifts or when we alter how a feature handles data. Every amendment is dated on this page so you can see what moved.
Where local law permits a different treatment, the local requirement takes priority for accounts in that region, and we tell you when it applies rather than leaving you to interpret the gap.