Account terms
Your account terms set the rules you accept on registration. This page explains how those clauses are drafted, dated and rewritten when a payment or access rule changes in Pakistan.
Everything governing your pop slots account sits on this page: the terms you accept when you join from Pakistan, how JazzCash, Easypaisa and Raast transfers are recorded, and...
We run a jurisdiction-aware policy. Where local law permits, you can register, hold an account and move money through JazzCash, Easypaisa, SadaPay, NayaPay or Raast from supported regions of Pakistan; outside those areas these terms still describe how we behave, but registration may be closed to you. Access depends on where you are, not on how you found us. If you travel
or relocate, your permissions can change and we will ask you to confirm your details again. We promise no service in any country where offering it would break local rules, and we can suspend a wallet link if a payment partner stops supporting it. Where a clause conflicts with mandatory local law, the law wins and we amend the clause.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy questions rarely need a phone call, and we would rather answer in writing so you keep a record. Send the legal desk your account reference and the clause you mean; a person reads it, not an autoresponder. Chat handles quick points about wallet links through the working day.
Send your account reference and the clause you want explained. A case handler replies in writing inside two working days, so the answer stays on record for you.
Chat covers wallet links, JazzCash and Easypaisa confirmation codes, and account access problems during desktop hours. If the point needs a written ruling, we move the thread to email.
If a reply does not settle your point, ask for a written escalation. We restate the clause, explain how we applied it, and give the timescale for our next response.
Our policy pages are drafted by the same team that runs the account systems, then checked against how JazzCash, Easypaisa, SadaPay, NayaPay and Raast actually behave in Pakistan. When a clause changes...
Every clause carries the date it was last touched. When a payment rule changes the page changes the same day, so you never read a version we have already replaced.
We write in English you can act on, with the legal term kept beside the plain one. You should follow a clause without paying someone to translate it.
Wording is tested against how JazzCash, Easypaisa, SadaPay, NayaPay and Raast settle in Pakistan. If a rail behaves differently, we correct the clause instead of leaving it standing.
Support records the questions you send most often, and the legal team answers them inside the wording itself. That is why these pages read like replies to real queries.
Older wording is kept internally, so we can show you what a clause said on the day you accepted it. Ask and we will send that version for your account.
Anything that affects your account appears on a policy page rather than buried in a promotion paragraph. If a condition is not written here, we do not use it against you.
This page does not stand alone. Account terms, privacy, cookies, cashier rules, verification, complaints and game rules all sit beside it, and we keep them consistent: a payment definition on one page...
Your account terms set the rules you accept on registration. This page explains how those clauses are drafted, dated and rewritten when a payment or access rule changes in Pakistan.
The privacy notice covers what we store and why. The page you are reading covers how that wording is governed, dated and corrected, so the two never contradict each other.
Cookies and similar storage are handled on their own page with the same revision dating. Where a cookie clause touches account access, the wording here takes precedence over any summary.
Cashier rules describe how JazzCash, Easypaisa, SadaPay, NayaPay and Raast movements are recorded. The clauses on this page decide how those rules are interpreted if a dispute arises.
Verification explains what we check before a withdrawal clears. Here we set out how a verification clause is written, how long a check may take, and where you can challenge it.
The complaints route lists the steps after a written reply. This page states how a complaint against a clause is assessed, and who signs off the final written answer to you.
Game rules cover how a round settles. Legal wording covers how those rules are published, dated and corrected, plus what happens if a published rule is shown to be wrong.
Nothing on our policy pages is decorative. Each element you can see — the revision stamp, the plain-English pairing, the market chips, the change history, the...
Each policy page shows the date it was last revised. You can tell at a glance whether you are reading current wording or something we have quietly moved on from.
Legal phrases sit next to a plain English version in the same paragraph, so you never have to hold two documents side by side to work out what a clause means.
Chips naming JazzCash, Easypaisa, SadaPay, NayaPay and Raast mark the clauses that behave differently for Pakistan. A badge means the clause has a local edge case written into it.
You can request the previous wording of any clause, and we will send the version that was live on the day you accepted it. No rewriting of history after the fact.
Every clause has a stable anchor you can copy into an email or a chat thread. When you raise a question, quoting the anchor means we both look at the same sentence.
A contact strip sits under every policy page with the legal desk address and desk hours for Pakistan. You do not have to hunt through a footer to find where to write.