Same Headings
Each policy page opens with a dated header and a short summary, so you always know which version you are reading and when it took effect for your account.
Every account you open with us starts with a clear promise about your data, and this page spells it out in plain Pakistani English. Read what we collect...
788 apk serves account holders in the regions where local law permits, and this policy is written for those supported regions. If you sign in from a place where our services are not offered, the account tools simply stay closed to you. Data handling can differ by market: a JazzCash or Easypaisa wallet used for a deposit in Pakistan may be verified
through a different partner than a card used elsewhere, and the retention window we apply follows the rules of the region your account sits in. We also treat policy versions the way we treat app builds — new wording arrives with a dated notice, older wording stays readable, and nothing about your existing choices changes overnight. Where a local rule asks for
more than we describe here, that rule wins.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about your own data land with a real person, not a queue that never moves. Our support desk answers privacy and account requests every day from 9am to midnight Pakistan time, and we log each ticket so nothing gets lost between shifts.
Open the in-app chat and a policy-trained agent picks up within minutes. Share the email on your account and the request you want actioned, and we confirm it afterwards.
Write to our privacy team and keep the thread as your paper trail. Requests about your data or account closure get a reference number, and we reply inside three working days.
Many choices sit in your own hands. Update your contact details, switch optional messages off, or close the account from the settings screen, without waiting on us at all.
This page is maintained by the same team that builds our payment and account flows, so the wording matches what the app actually does. Every revision passes a second pair of eyes...
The same engineers who build our deposit flow and wallet checks help draft these clauses. Nothing here is rented copy from an outside agency writing promises we cannot keep.
Each revision carries the date it went live, and earlier wording stays readable for anyone who wants to compare. You can always see what changed and when it changed.
No clause reaches this page until two people sign it off, one from the payment team and one from account security. That keeps wording tied to how the platform behaves.
Where a Pakistani rule asks for stricter handling than we describe, that rule wins for your account. We adjust wallet check timelines across JazzCash, Easypaisa, SadaPay and Raast to match.
We avoid legal fog. When a clause could be read two ways, we rewrite it until it reads one way, then test it with readers outside the company.
Ask us anything this page leaves unclear and we answer with a real explanation, not a link dump. Recurring questions shape the next revision, so your message can improve it.
Our policy pages share one voice and one structure, so you can jump between them without learning a new layout. This page covers data, the terms page covers account conduct, and the...
Each policy page opens with a dated header and a short summary, so you always know which version you are reading and when it took effect for your account.
This page handles your data only. Rules about how you run your account sit on the terms page, and we link across so you never guess which document answers you.
The cookies note explains what your device stores when you sign in and how long it stays there. We keep that separate so each promise stays short enough to read.
Every page sends you to the same support desk, so a request about your data, your account or your payment history lands in one tracked queue rather than three inboxes.
Terms like account, wallet and verification carry the same meaning on every page we publish. That consistency matters when a clause here points you to a rule elsewhere.
Older versions of every policy stay online with their original dates. If you joined under earlier wording, you can still open it and see what you agreed to then.
When wording changes, we post a dated notice above the clauses and, for anything that affects your choices, message you through the account before the new version applies.
Our policy screens follow one layout so nothing important hides. A summary opens the page, the full wording runs underneath with anchor links, and the contact...
The first block names what this page covers in a few lines, so you can decide in seconds whether to read on or jump to a specific clause.
A sticky menu keeps every heading one tap away on mobile data. Jump from data collection to retention to your choices without scrolling the whole document on a slow connection.
Each version shows the day it took effect and the day it was last touched. That header is the quickest way to prove which wording applied to you.
A short note states where our services are offered and reminds you that access depends on local law. It sits above the clauses so scope is clear first.
A button in the account area links back to this page and to the toggle that turns optional messages off. You should never hunt for that switch yourself.
Body text sits large enough to read on a mid-range handset in daylight, with short paragraphs and plain words. We test the layout on cheaper Android screens before publishing.