Terms of Use
Owns the account agreement: eligibility, one account per person, how access can be suspended, and what follows if a term is broken. Other policy pages link here instead of restating it.
These pages set out the terms that govern your lottery game account, in clear Pakistani English. You will see how eligibility, deposits through JazzCash, Easypaisa, SadaPay and Raast...
Our policy posture is simple: we apply the terms as written, and where a clause depends on where you live, we say so instead of burying it. If a feature is unavailable in your province, the account you hold stays intact but that feature will not appear for you. Local rails such as JazzCash, Easypaisa, SadaPay and Raast are supported only where
local law permits, and payment partners may add their own conditions as well. When we change a term that affects your account, we publish the new wording with an effective date. Nothing here limits rights you hold under the law that applies to you, and if you disagree with a change you can close the account and take out any remaining balance.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy questions deserve a direct answer, so we send them to people who can read the clause with you. Write from the email address on your account and we reply within one working day, Sunday to Thursday. If a term reads oddly, ask us to point to the paragraph it comes from.
Write from the address registered on your account so we can match the query to your region. We answer within one working day, Sunday to Thursday, in English or Urdu.
Open the help panel inside your account when a policy point affects a live deposit or withdrawal. It passes your account reference to an agent, so no long explanations are needed.
If you think a decision went against our own terms, ask for a written reply. We restate the clause we applied and explain the outcome in full.
Every clause here is drafted by the team that runs account operations, then checked against how the platform behaves on the day it goes live. We name the rails you will genuinely...
The team that handles deposits, withdrawals and account access writes these clauses. Nothing here is produced by an outside party describing our service at arm's length, so what you read matches what we run.
Every policy page carries the date its wording took effect, so you can tell whether you are reading the version that applied when you opened your account.
When a clause moves, we list what changed and why, one line per update. Compare the old wording with the new before deciding whether to keep your account open.
Features that depend on where you live are tagged rather than hidden. The tag names the affected areas, so you see at once why a table or cash-out route is absent.
JazzCash, Easypaisa, SadaPay and Raast appear on these pages only where they genuinely process for your area. If a rail pauses or drops out, the wording is updated to match.
Two people clear each policy update: one from account operations, one from the team handling customer disputes. A page goes live only after both have agreed the wording.
Our policy pages read as one document split into parts, so a phrase you learn on the terms page means the same on the privacy page. Where two pages touch a subject...
Owns the account agreement: eligibility, one account per person, how access can be suspended, and what follows if a term is broken. Other policy pages link here instead of restating it.
Owns what account details we hold, how long we keep them and who can see them. The security and payments pages point here rather than describing data handling in their own words.
Owns the browser storage we set and the choices open to you. The terms page links here instead of repeating cookie wording, so one edit covers every place it appears.
Owns how money moves through JazzCash, Easypaisa, SadaPay and Raast, including clearing times and verification. Rails named elsewhere carry the same wording, so you are never given two different timings.
Owns passwords, two-step checks and how we contact you about unusual sign-in activity. Support pages route security questions to this wording so nothing is answered twice in different ways.
Owns how a dispute is raised, the response times we keep and the escalation step after that. Every other policy page sends you here when a decision needs to be challenged in writing.
Owns which markets and features are switched on in which areas. Pages that mention supported regions take their list from here, so a single version of that list exists across the site.
The policy side of lottery game looks the same wherever you land, which makes a clause quicker to find when you need it. A section index...
A short list of anchors at the head of each policy page. Tap one and jump straight to the clause on eligibility, payments, account closure or disputes without scrolling past wording you do not need.
Sits directly under the headline and shows the day the current wording began to apply, so an older saved copy is easy to spot at a glance.
A shaded box above the legal text restates each clause in everyday Pakistani English. If the summary and the clause ever disagree, the clause governs and the summary is rewritten.
Any table, market or cash-out route that depends on where you live carries a small tag naming the affected areas, so you are not left guessing why it is missing from your account.
A collapsible panel lists every update to the page with its date, one line each. Open it to see whether a term you relied on has moved since you signed up.
Each page has a print layout with the effective date in the footer. Save it as a file if you want a copy of the terms that applied on the day you opened your account.