Payment Terms
Transfer rules match the payment page exactly, including JazzCash, Easypaisa, SadaPay, NayaPay and Raast clearing windows, reversal handling and the balance your account shows after settlement.
These conditions spell out the arrangement between you and us: what your account covers, how transfers through JazzCash and Easypaisa settle, and what each side owes the other...
Your account with free slots is offered only where local law permits, and these conditions are written so you always know which rules sit behind it. Access depends on the region you register from, so we ask you to confirm you meet the entry requirements before you deposit. Transfers made through JazzCash, Easypaisa, SadaPay, NayaPay or Raast follow the same terms as
any other route: once cleared, the amount visible on your account is what governs play, and reversals or failed transfers are handled case by case. Where a market changes its rules, we update this page and the effective date moves with it. Continuing to use the account after an update means you accept the revised conditions, and if a clause no longer
suits you, you can close the account at any time.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If a line in these conditions reads awkwardly or you cannot tell how it affects your account, write to us through live chat or email and quote the clause number. Our team answers between 9am and 1am Pakistan time, seven days a week, and we aim to reply to written terms questions within one working day.
Open live chat from your account dashboard for questions on clauses, closure or a transfer that did not settle. Advisors reply in English or Urdu and stay on the thread.
Send a written question to our policy inbox and keep the ticket number. Email suits disputes, version differences and requests for a copy of the conditions from your registration date.
Changes to these conditions arrive as an in-account message ahead of the effective date, so the notice and the clause sit together and nothing slips past you.
These conditions are drafted by the team that runs the free slots platform day to day: the same people handling account sign-ups, JazzCash and Easypaisa transfers and live table scheduling. A legal...
Clauses on transfers, access and market availability are written by staff handling those flows daily, so the wording matches what happens when you use JazzCash, Easypaisa, SadaPay, NayaPay or Raast.
A colleague outside operations reads each draft before publication, checking that account rules, payout timing and closure rights are stated clearly and do not contradict other pages.
Every update carries its own effective date and older versions stay on record, so you can always see which wording applied on the day you registered.
We rewrite dense clauses into short sentences while editing, because a term you cannot follow is a term you cannot rely on. Jargon the platform never uses gets cut.
Material changes reach you as an in-account message before they take effect. Where a change narrows what your account can do, the notice says so plainly.
If you think a clause misstates how the platform behaves, raise it with support and cite the section. Confirmed errors are corrected and the revised version is dated.
The conditions on this page sit beside our privacy notice, account rules and payment terms, and the wording is kept aligned so no clause contradicts another. Where a topic appears in more...
Transfer rules match the payment page exactly, including JazzCash, Easypaisa, SadaPay, NayaPay and Raast clearing windows, reversal handling and the balance your account shows after settlement.
Data clauses line up with the privacy page, so the identifiers requested at registration appear in both places with the same retention period and the same stated purpose.
One account per person, verification at withdrawal and closure on request appear in identical words on both pages, so you never read two versions of one rule.
Changes to a shared clause are applied to every affected page on the same date, so no page is left stale and you always know which version binds your account.
Region restrictions are described once and referenced elsewhere with the same supported-regions wording, so the entry test reads identically across the terms and payment pages.
The complaint path here repeats the escalation steps in our account rules, including response windows and the records we keep, so a dispute follows one route.
Each policy page shows when its wording took effect. Comparing the dates tells you which version was live when you acted, useful if you query an old transfer.
This page is built short on purpose: a summary at the opening, the full posture in the middle, then the contact routes and the questions people...
The opening block gives you the shape of the agreement in a few lines, naming which areas carry their own clauses further down the page.
Access clauses are written with regional limits in view, so you can see whether your location qualifies before you commit funds or open an account.
The rails we support sit as chips near the opening, because transfer terms only make sense once you know which routes they govern.
Support routes appear as their own block with channels, hours and expected response times, so a terms question has a clear destination.
Each clause block shows when its wording took effect, letting you match a rule to the date you registered or the date a transfer was submitted.
The closing block answers the terms questions we field most often, from account closure to transfer reversals, in the same plain language used above.