Privacy policy
The page you are reading covers collection, use, retention and your requests. It is the parent document, and the others here expand one part of it rather than contradicting it.
We collect what an account genuinely needs and nothing beyond that. This privacy policy lists the details you give us, the JazzCash, Easypaisa, SadaPay, NayaPay and Raast references...
Your data belongs to you; we hold it so your account can work. aviator slot keeps your name, contact details and eligibility details, plus the transaction references that JazzCash, Easypaisa, SadaPay, NayaPay and Raast hand back after each wallet load or withdrawal. We retain that record while your account is open and for the period local rules require afterwards. Where local law
permits, some processing rests on your consent, and you can withdraw it at any time; elsewhere the contract between us is the basis. We do not sell your particulars to brokers. File access sits with a small, logged team. You can ask what we hold, request a correction, or ask us to erase what we are not obliged to keep, and requests
from supported regions move in the order they arrive.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This policy is written and kept current by the same team that handles your account requests, so the wording matches what actually happens. Each version carries a date and a plain-language summary...
A small group signs off each version of this privacy policy. Every change carries a date, a short reason and the person accountable, so the wording history stays traceable.
When we alter how your details are used, a notice appears in your account before the change applies. Nothing shifts quietly, and you can close your account instead.
We write in everyday English rather than legal shorthand. If a clause needs a lawyer to unpack it, we rewrite until you can act on it without asking.
Every new feature starts with a question about what it truly needs from you. If a field is not required for sign-in, payouts or record-keeping, we drop it.
Account access runs over encrypted connections and passwords are stored hashed. Staff who open a customer file leave an audit entry, and your account lists recent sign-ins you can end.
Requests from Pakistan and other supported regions follow one process. Wording stays in English, timings sit in working days, and we say plainly when local law limits a request.
Everything you read here lines up with the other notices on this site. Whether you open the privacy policy, the cookie notice or the account rules, the same definitions apply, the same...
The page you are reading covers collection, use, retention and your requests. It is the parent document, and the others here expand one part of it rather than contradicting it.
Cookies and similar storage get their own page because the detail is long. It names each category, what it does on the site and how you switch it off.
Rules for holding an account sit beside this policy. They cover eligibility, one-account-per-person checks and closed accounts, using the exact same definitions you find in this document.
Timings and checks for taking money out sit on their own page. That page mirrors the data points quoted here, so the same verification steps apply to both.
This notice explains how to allow or end promotional messages across email, SMS and in-account banners. Your consent choice never affects your ability to sign in or take money out.
If you think we have handled your details badly, the complaints page sets out the route: our desk first, then an escalation step with the same case number.
The security page lists our safeguards in the same order this document does: encrypted connections, hashed passwords, audit trails on customer files and session controls you run yourself.
This page is built for fast reading. You get a short hero, plain headings you can scan on a phone, and chips that name the rails...
Each part of the policy carries a short heading, so you can jump to the clause you need. Numbers, timings and rail names stay in the text, not in footnotes.
The chips here name the rails this policy talks about, so you can match a clause to the wallet you use without guessing which brand we mean.
Every deadline on this page is given in working days rather than vague phrases, so you know when a response is due and when it is reasonable to chase us.
There is a single path for data requests, shown in the support block above. You do not need to hunt through separate forms or send the same question twice.
The most recent version date sits at the head of the document. When something material changes, that date moves and the summary of changes is updated alongside it.
Most of you read this on a phone, so paragraphs stay short, tables collapse into readable lists and nothing important hides behind a hover state or a desktop-only panel.