Terms of use
Sets the rules for using your account. This page explains what data those rules generate, so the two read as one document rather than two competing versions of it.
LEGAL REFERENCE
Privacy Policy for Your exchange bet Account
This privacy policy explains, in plain Pakistani English, how exchange bet collects, uses and stores the details you share when you open an account, fund it and move...
Account file controlStored region clarityWritten request routeUpdate dates shown
How We Handle Data Across Regions
Where local law permits, your data sits in the region that serves your account, and the rules of that supported region decide how long each record must be retained. When two rule sets overlap we apply the stricter one, so a Pakistani account holder gets the tighter standard. We do not sell account records or move them across borders for marketing. Evidence
tied to JazzCash, Easypaisa, SadaPay or Raast transfers is stored apart from your browsing data, with access limited to the staff who clear those transfers. Retention windows are printed next to each record type, and we tell you before any change takes effect. Nothing here depends on where you happen to be sitting when you read it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY HELP DESK
Reaching Us About Your Privacy Policy
Questions about this privacy policy reach a person, not a ticket void. Our support desk runs daily from 9am to 1am Pakistan time, and the agents on it can pull up your account file, explain what a data field means and log a formal request while you wait. Write in English or Urdu, and we answer in the language you used.
Team online
Live chat desk
Chat is the quickest path for policy questions. Say you are asking about data handling and the agent marks it a privacy case, keeping the thread with one team until closing.
Email records desk
Send a written request to our records desk and a case number arrives the same day. We reply within seven working days, and longer manual pulls get a dated progress note.
In-app request form
Your account settings hold a short form for access, correction or deletion requests. It routes straight to the team that owns your file, and you can track status without emailing anyone.
WHO WROTE THIS
Who Writes and Checks This Policy
Policy wording is worth reading only if you can tell who wrote it and when it changed. Ours is drafted by the team that runs account operations, then checked against what the...
Named drafting team
Each revision lists the internal team that produced it, so you know whether the wording came from account operations, payments or the support desk rather than an unnamed source.
Dated change log
A running log sits under the text. It shows the date of each change and one line about what moved, so returning readers catch an update in seconds instead of rereading everything.
Code-matched wording
Before anything goes live we compare the sentence with the system behaviour it describes, including how JazzCash and Easypaisa transfer records are stored and who inside the company may open them.
No template filler
You will not find paragraphs lifted from a generic policy pack. If a clause does not match how exchange bet handles your account, it does not belong on this page.
Readable summaries
Long clauses sit under short plain-English summaries, so a quick scan gives you the gist. Tap through when you want the statutory wording, which stays on the page, not behind a link.
Open questions route
If a clause reads badly, flag it. Questions raised through our desk are read by the drafting team each week, and wording that keeps confusing people gets rewritten next revision.
CONSISTENT WORDING
How This Page Matches Our Other Policies
The wording here has to line up with the other policy pages on exchange bet, or you end up with two answers to the same question. Retention rules, cookie language and security...
Cookie notice
Lists the small files your browser stores. Here we explain why each one exists and how long it lives, the part most people want settled before they accept anything.
Payments and payouts
Covers how money moves on JazzCash, Easypaisa, SadaPay and Raast. The data angle sits here: which transfer reference we store, and what we never keep after settlement.
Account security
Explains logins, device checks and password resets. Retention for those security logs is set out above, so the two documents agree on how long a session record survives.
Promo terms
Describes how offers are credited and validated. Read it with this page to see which eligibility checks run and how long campaign records stay attached to your account profile.
Complaints handling
Sets out how a dispute travels through our desk. Personal details you attach to a complaint follow the same storage rules that apply to the rest of your account file.
Data request page
Where the request form lives. Submitting it here and tracking it there keeps one case number across both pages, so nobody has to explain their situation twice.
What the Policy Page Shows You
The policy page is built to be scanned, not waded through. Look for the sticky section rail on desktop, the summary chips that sit above each...
Sticky clause rail
A fixed side rail tracks your position as you scroll, so you can jump between consent, retention and sharing clauses without losing your place in a long paragraph.
Summary chips
Short chips above each clause give you the gist in a few words before the statutory sentence begins, which helps when you only need one detail about your own file.
Change stamp
Every revision carries a date and revision number at the head of the section, so you can tell whether the wording you saved last month still applies today.
Plain-English callouts
Key promises sit in bold callouts: no selling of account records, no cross-border movement for marketing, and a fixed reply window on every written request you send.
Mobile reading view
On a phone the rail collapses into a jump menu and clause blocks stack into single columns, so the policy reads the same on a Karachi commute as on a desktop.
Language and format
Dates, currency references and settlement figures follow Pakistani conventions throughout, and the text is written in the English you would hear on a Lahore or Islamabad support call.
Privacy Policy Questions We Get Asked
It covers every piece of personal data exchange bet holds about you, from signup details and JazzCash or Easypaisa transfer references to device logs, chat transcripts and the records our support desk keeps.
Retention depends on the record type and the rules of your supported region. Transfer and identity evidence tied to a JazzCash, Easypaisa, SadaPay or Raast payment stays longer than browsing logs.
No. We do not sell account records and we do not hand them to advertising networks. Payment evidence sits apart from browsing data, and only staff who process transfers can open it.
Open the request form in your account settings and choose access. You get a case number straight away, and our records desk replies within seven working days for a straightforward request.
Yes. Send a correction request naming the field that is wrong, plus anything that proves it. If a payment reference must stay unchanged for audit reasons, we explain why in the reply.
We publish the new wording on this page with a dated change stamp and a one-line summary of what moved. Material changes are also flagged in your account messages before they start.