Terms of use
Our main agreement sets the account rules; this page explains how we apply them in practice and which parts change when local law requires a different outcome.
One page holds the terms you agree to when you open an account with us, written in plain English instead of dense legalese. Read it once before you...
Access to our lobby, and everything inside it, follows the rules that apply where you are sitting, so we write our terms to bend with local law rather than pretend one rule fits every country. Where local law permits, you can hold an account with us from Pakistan and use JazzCash, Easypaisa, SadaPay or Raast to move funds; where a region is
not supported, our sign-up flow ends before anything is created. We keep the wording plain: what you agree to, what we agree to, and what happens if either side breaks it. Payment rails appear in our terms as context chips only, because each one carries its own processing window and its own verification steps outside our control. Read it alongside your account
agreement and the two fit together.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This page is maintained by the same team that runs accounts daily, so answers reflect how verification, closure and disputes actually move through the system. We date every edit and name the...
Each block on this page names the team responsible for keeping it accurate, so a question about a clause reaches the people who wrote it rather than a generic inbox.
Every edit carries a date and a one-line reason, so you can see which paragraph changed after you joined and whether that change touches your account terms at all.
We redraft dense legal phrasing into sentences you can read once, and we keep the names of Pakistani rails spelled exactly as they appear on your payment records.
Policy questions are answered from 09:00 to 01:00 Pakistan time, because an account dispute rarely arrives at a convenient hour and you should not wait two days.
When we settle a disagreement, the outcome reaches you in writing with the section quoted, so you hold a record rather than a verbal promise from a chat window.
We ask for your password and a one-time code before any policy change is applied to your account, and we never request your payment PIN through chat or email.
Every policy page on wink slots is written to the same structure, so a term keeps one meaning whether you read it here, on the account agreement or on the privacy wording...
Our main agreement sets the account rules; this page explains how we apply them in practice and which parts change when local law requires a different outcome.
Privacy wording follows the same structure as this page, so the way we describe data handling matches the way we describe account rules across wink slots.
Cookie wording borrows the same section names, which means you can move between both pages without learning a fresh layout halfway through reading a clause.
Account rules repeat the definitions used here, so a term such as supported region means one thing across the site rather than something different on every page.
Identity and payment verification copy follows the same order as this page, from what we ask for to how long a check usually takes on Pakistani rails.
Complaint wording mirrors the process described here, so escalation steps, response windows and the address you write to stay identical across every policy page on wink slots.
Closing an account reads the same here and on the agreement page, covering what stays on record, what is deleted and how long each step takes in practice.
This page is built to be read through, not skimmed past. Numbered clauses, a fixed side list and consistent section names let you find a single...
A fixed side list keeps every clause one tap away, so you can jump straight to account rules, closure wording or the dispute route without scrolling through the whole page.
The revision date sits above each block, letting you confirm at a glance whether you are reading wording that was updated after your last visit to wink slots.
Words with a specific meaning are marked the first time they appear, so a phrase such as supported region carries one fixed definition through the whole agreement rather than shifting halfway.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast appear as chips wherever a clause touches them, which keeps our wording tied to the rails you actually use in Pakistan.
Short paragraphs, numbered clauses and no footnotes mean you can read one rule on a phone screen while travelling rather than printing twenty pages at a desk.
Every block prints cleanly from a desktop browser, so you can keep an offline copy of the terms that applied on the day you opened your wink slots account.