Cookie Banner
The cookie controls you meet on this page behave the same way across the site. Accept, reject or adjust, and your choice carries with you.
We collect only what your account needs to run: your name, contact details, date of birth and the payment handles you connect for JazzCash, Easypaisa, SadaPay or Raast...
Our handling of your data follows the rules that apply in the supported regions where your account is opened, and where local law permits extra protection we apply it. We hold identity details, contact records, transaction logs from JazzCash, Easypaisa, SadaPay and Raast, plus device and login data that keeps your session secure. Records stay only while a legal or operational need
exists, after which we remove or anonymise them. You can ask what we hold, request a correction, or close the account and have personal data erased where no retention duty applies. Where local law permits, we answer within thirty days of confirming who you are. If a request touches data we must keep for audit or reconciliation, we set out which part
stays and why.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about privacy on pokies game do not need a long detour. Our support desk is staffed every day and we pass data requests to people who can act on them, not a general queue. Tell us what you want changed, corrected or removed and we walk you through each step.
Open the chat window from your signed-in account and an agent picks up the thread. We take access requests and closure steps here, then email you the transcript.
Write to our privacy mailbox from the address tied to your account. Attach anything that helps us match your record and we send a reference number for tracking.
Sign in, open your profile and download a copy of the details we hold, change your contact number, or begin closing the account. Edits sync to our records at once.
This page is written and maintained by the team that runs pokies game day to day, which means the wording tracks how the platform actually behaves. We set clear internal rules for...
One named team holds this policy, answers for its wording and signs off every change before it goes live. You never read text nobody inside the platform stands behind.
We map each field we store to a reason for storing it, from age checks to settlement matching. Anything without a live reason is flagged for removal at the next sweep.
Staff open a customer record only when a task needs it. Every lookup is logged against an individual login, and odd patterns reach the security team the same day.
Your JazzCash, Easypaisa, SadaPay and Raast handles are held as references, not open credentials. Settlement files stay restricted and are checked against your transaction history nightly.
We publish how long each record class is kept, then delete or anonymise on schedule. Identity files, chat threads and settlement logs each follow their own window.
When this policy changes we post the new version here and flag it inside your account. Material changes come with a short message explaining the difference.
The same promises about your data run across our sibling pages, because they all describe one platform. Our account rules, cookie banner and terms of use borrow the definitions you read here...
The cookie controls you meet on this page behave the same way across the site. Accept, reject or adjust, and your choice carries with you.
Our account terms describe the same stored fields you read about here. When a rule changes, both pages update together so you never meet two versions.
Sections covering JazzCash, Easypaisa, SadaPay and Raast use identical language wherever they appear, which keeps the promise about your payment references steady.
The reply windows we quote for data requests match the ones on our help pages. Nothing here claims a faster answer than the support desk can deliver.
Closing an account is described the same way in our terms and on this page. Confirmation, balance handling and record removal follow one sequence.
English across every policy page keeps one meaning for each rule. Where local wording helps you, we add it rather than replacing the English version.
Each of our policy pages carries the date it last changed, so you can follow the order of revisions without hunting through separate documents.
The layout of this policy is deliberate. Consent toggles sit high so you can set cookie preferences before you scroll, the chips row names the rails...
Cookie settings sit high on this page so you can switch categories before reading further. Your choice is saved against your browser and your account.
The chips row names every rail we support, JazzCash, Easypaisa, SadaPay, NayaPay and Raast, so you can see which handles this policy covers.
Each heading asks the question you arrived with. We keep dense clause numbering out of the way where a short sentence explains the same rule to you.
One link saves the whole policy as a file. Keep it beside your account records if you want a dated copy of what applied when you signed up.
Beside each request type we state how long a reply takes in supported regions: instant on chat, same day by email, up to thirty days for formal requests.
The support block at the foot of this page repeats our channels with working links, so you can raise a privacy question without searching the rest of the site.