LEGAL REFERENCE

How We Handle Your Personal Data

Plain-language privacy terms you can read in a few minutes: what we collect when you open an account, why we keep it, and how you can ask us...

What we collectWhy we keep itYour requestsCookie controls
7777b game How We Handle Your Personal Data

What This Policy Covers Where Local Law Permits

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

PRIVACY DESK

Reaching Our Privacy Desk

Getting something changed should not feel like a hunt. Here are the three routes our privacy desk watches, what each one suits, and the reply window you can expect inside Pakistan. All three reach the same team, so nothing you raise in chat gets lost when you follow up by email. Reply times sit beside each channel.

Team online

Privacy inbox

Email [email protected] with your account number and the change you want. Every message gets a reference, and we reply between 9am and 9pm Pakistan time, six days a week.

Live chat

Once you are signed in, open the chat panel on your dashboard. Chat suits quick questions about stored details, sign-in alerts and access from a device you have not used before.

Account settings

Under Settings you can download a summary of the details we hold, update your contact number, or begin a deletion request. Each action is confirmed by email so you keep a record.

POLICY STANDARDS

How We Keep These Terms Accountable

A privacy page is only useful if you can see who wrote it, how often it changes, and where to complain. We publish a revision date, keep an archive of earlier versions...

Plain wording

We write privacy clauses in the same English we use across the site, so you can read a clause once and act on it without a legal dictionary.

Revision log

Every change carries a date and a short summary of what moved, letting you compare the version you accepted at sign-up with the one live on the site today.

Named owners

Policy questions land with a small team that also manages account security, so whoever answers already understands how sign-in alerts and payment references are stored on our side.

Local context

Our wording reflects Pakistani banking practice, including the fact that JazzCash, Easypaisa, SadaPay, NayaPay and Raast share a payment reference with us rather than your full bank credentials.

Device guidance

We explain what the mobile app stores on your handset and which permissions you can switch off without affecting withdrawals, sign-in or live table streaming on a slower connection.

Escalation path

If a reply does not settle your question, this page shows how to escalate to our data protection contact and the timeline you can expect for a written response.

PAGE CONSISTENCY

One Standard Across Every Policy Page

This page sits beside our terms and cookie notice, and all three share one structure: what we hold, why we hold it, how long we keep it, and how you tell us...

01

Shared definitions

Terms such as account, verification reference and retention period mean the same thing here as they do in our terms of use and cookie notice.

02

Same revision date

All three documents carry the same revision date whenever a shared clause moves, so you never have to work out which page is the newer one.

03

No buried clauses

Nothing about how we handle your details hides in a footer or a pop-up. Anything that affects your data appears on a policy page you can bookmark and return to.

04

Cookie wording

Our cookie notice lists the categories we actually run, and this page explains what each category stores and how you can refuse the optional ones on any device.

05

Payment references

Where payment handling is mentioned, it refers only to the reference number your bank or wallet shares after a JazzCash, Easypaisa, SadaPay, NayaPay or Raast transfer.

06

Closure steps

The steps for closing an account are written once and linked from both the terms and this policy, so the process you read about is the process we follow.

07

Contact overlap

Support, site and policy questions all use the same channels, which means you will not be passed between teams keeping separate records of your request.

BRAND HIGHLIGHTS

What You Will See On This Page

We shaped this page so the parts you need are reachable in a single scroll rather than one wall of clauses. Scope, retention, contact routes and your own...

Opening summary The opening block lists what we collect and why, so...
Retention table A compact table shows how long we keep registration details...
Your controls Your controls sit together in one place: correcting contact details...
Channel cards Each contact route gets its own card with expected reply...
Revision banner A dated banner near the page heading shows when this...
Region labels Short labels mark the clauses that vary by jurisdiction, so...

Privacy Policy Questions We Get Asked

We hold what you type at registration, a verification reference, your chosen payment rail, and technical logs from each sign-in. We do not store your full wallet or bank credentials.

Only with processors that keep the platform running, such as payment partners and hosting suppliers, and only as far as each task needs. We do not sell account records to data brokers.

Payment references tied to JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers stay on file for the period local rules require, after which we delete or anonymise them rather than holding them indefinitely.

Yes. Open Settings, choose close account, and we confirm the request by email. We then delete what we are allowed to erase and keep only records we are legally bound to retain.

The date printed beside the page heading moves whenever we edit a clause, and we post a short summary of the change so you can see exactly what was rewritten.

Message the privacy desk with the field that looks wrong and any reference you hold. We check it against our logs and reply with the correction or an explanation.