LEGAL REFERENCE

Your Privacy Policy, Explained Plainly

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...

Account record choicesJazzCash and Easypaisa referencesDevice and sign-in signalsAccess, correction and erasure
aviator slot Your Privacy Policy, Explained Plainly

How We Handle Your Account Data

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY SUPPORT DESK

Reaching Our Data Desk

Questions about your data go to one desk, staffed every day. Ask for a copy of your record, a correction, a consent...

In-account request form You can raise a data request from inside...
Privacy chat line Our chat line takes privacy questions seven days...
Written data desk Prefer writing? Send your question to our data...
POLICY WRITING TEAM

Who Writes And Keeps This Policy Current

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...

Named policy owners

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.

Change notices

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.

Plain-language drafting

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.

Data-minimisation habit

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 security practice

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.

Regional handling

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.

POLICY CONSISTENCY

One Standard Across Our Policy Pages

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...

01

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.

02

Cookie notice

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.

03

Account rules

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.

04

Withdrawal terms

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.

05

Marketing consent notice

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.

06

Complaints procedure

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.

07

Security page

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.

What You See On This Page

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...

Scannable headings

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.

Payment rail chips

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.

Working-day timings

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.

One request route

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.

Version date at the head

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.

Mobile-first layout

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.

What You Ask About Privacy

Your name, contact details, date of birth for eligibility, and the references JazzCash, Easypaisa, SadaPay, NayaPay or Raast return after a wallet load or withdrawal. We also record device and sign-in signals.

Only to the processors that keep the account running, such as payment partners and identity checks, and only for that purpose. We do not sell your particulars to brokers or resellers.

While your account is open, plus the period local rules require afterwards for transaction and eligibility records. When that period ends, we delete or anonymise the file.

Yes. Raise a request from inside your account or through the privacy desk. You get a case reference the same day, and a reply within a few working days from supported regions.

Promotional messages end across email, SMS and in-account banners within a few working days. Your ability to sign in, use the lobby or take money out is not affected in any way.

Traffic between your device and our servers is encrypted, so a shared connection cannot read your session. Sign-ins from unfamiliar devices or regions may need an extra verification step.