Shared definitions
Terms used here — account, verification, settlement — carry the same meaning on our other policy pages, so you never have to guess which wording applies to the request you filed.
Your privacy policy matters most at two moments: when you open an account, and when you request a withdrawal. We set out in plain English what we collect...
Where local law permits, this policy covers every account you open with luck33 online from Pakistan and any supported region we serve. We decide why your data is collected and how it is used, so the wording here is ours. Some parts change with jurisdiction: countries set different retention periods, different marketing-consent rules, and different rights to request a copy or a
correction. Where those rules differ, the stricter local requirement wins. If you relocate or open an account while travelling, tell our support desk so your account maps to the right regional rules. Paying in or out through JazzCash, Easypaisa, SadaPay or Raast changes nothing about what we collect; it only adds the wallet reference that comes back to us.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Questions about your data should never sit unanswered. Our support desk runs on Pakistani hours, and the same team handles account requests and privacy requests, so you are not passed between departments. Tell us what you want — a correction, a copy, or a deletion where the law allows it — and we log it and reply on the channel you used.
Open live chat from inside your account and a Pakistani-hours agent picks up the thread. Transcripts stay against your account, so nothing has to be repeated when you come back.
Write to our privacy mailbox for copies, corrections or account closure. We ask for two identifiers to confirm it is you, then reply within five working days on the same thread.
Every account carries a request form for data access and deletion. Submitting it raises a tracked ticket you can follow from your dashboard, without waiting on a reply.
This page is maintained by the same team that runs the account system, not by an outside writer. When something in the product moves — a wallet rail...
Every edit to this policy carries a date and a short reason, so you can see what moved and when...
Account records sit behind role-based access, so support staff see the fields they need for your ticket and nothing else...
Wallet references from JazzCash, Easypaisa, SadaPay and Raast stay for the period tax and dispute rules require in Pakistan, then...
A request lands with a named privacy contact instead of a shared inbox, so you know who is handling your...
Everyone on the account and support side completes a data-handling session before going live and repeats it each year. New...
We name the categories of outside companies that touch your data, payment handling, messaging and hosting, and we hold each...
This page shares its structure with our terms, cookies and account-usage pages, so you can move between them without relearning the layout. Definitions are shared, change dates are shared, and the contact...
Terms used here — account, verification, settlement — carry the same meaning on our other policy pages, so you never have to guess which wording applies to the request you filed.
Support channels on this page match the ones listed with our terms, so a request opened from anywhere reaches the same privacy desk and joins the same queue.
When one policy page is revised, the others are checked in the same week, so you will not find a cookies page dated behind the wording you are reading now.
Retention periods are set once and reused across the site, keeping JazzCash, Easypaisa, SadaPay and Raast wallet references on one shared timeline rather than several competing ones.
Where the terms page covers account closure and this page covers deletion, both point at the same procedure, so the outcome does not change with the page you started from.
Everything is written in the same en-PK English used across the site, with no translated annex that could read differently from the text you agreed to when joining.
A complaint follows one route regardless of where you started: our support desk first, then the named privacy contact, then the relevant regulator where local law allows it.
We built this policy page to be scanned, not skimmed past. Short sections sit above a wallet chip row, and each card below carries one idea...
Each block opens with a short heading and a two-line summary, so you can reach the part about retention or verification without reading the whole page from start to finish.
A chip row lists JazzCash, Easypaisa, SadaPay and Raast up front, showing which wallet references can appear in your account history and on the statements your wallet sends.
Every card explains one policy idea and stops there. Nothing is buried three paragraphs deep, which makes it easier to find the sentence that answers the question you arrived with.
Section links sit just under the heading, so you can move between jurisdiction wording, support routes and retention rules with a single tap on a phone screen, no scrolling required.
A dated banner at the head of the page shows when the text last moved, so you know you are reading current wording rather than a copy saved from an earlier visit.
The question block at the foot of the page gathers the points raised most often — copies, corrections, closure and retention — and answers each one in a short paragraph.