How We Collect, Keep And Use Your Data
This page sets out what we collect when you open an account, why each field is needed, and how long it stays with us. Read it once and...
Where Local Law Shapes This Policy
Access to wealth slot is offered in supported regions and only where local law permits, and this policy is written with that limit in mind. Where you sign in from, and which rail you use, changes what we must hold and for how long. A JazzCash or Easypaisa transfer, a SadaPay wallet load and a Raast bank movement each leave a different
record set, and we store only what the receiving institution and our own auditors need to see. If a rule in your province requires a longer retention period, the longer period wins. If it requires earlier erasure, we erase earlier. We update this page when payment rails or local rules change, and each revision carries a date. Carrying on with your account
after a revision means you accept the updated wording.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching Us About Your Data
Questions about your data reach a real team rather than a queue that swallows them. Write from the address on your profile, name the clause you are asking about, and we answer in plain English. If a payment record is involved, send the reference your wallet or bank issued so we can trace it fast.
Email our data desk
Write from the address on your profile so we can confirm it is you, and name the clause you are asking about. Most replies go out inside one working day.
Message us in-app
Once you are signed in, open a thread from the help panel without leaving the lobby. Your account reference attaches on its own, so there is nothing to retype.
Send a payment reference
If your question touches a JazzCash, Easypaisa, SadaPay or Raast entry, paste the reference your provider issued. We can trace the record in minutes instead of days.
The Checks Behind Every Policy Change
Confidence in a policy comes from who touches it. Each revision here is prepared by the team that runs the account database, checked against what our systems genuinely...
Data owner signs off
Every revision of this policy is read by the person who owns the account database before it goes live, so...
Revisions carry dates
Each update gets a date on this page, and the earlier wording stays reachable. You can compare two versions and...
Payment partners aligned
Before we describe how a rail is handled, we confirm the flow with the provider side, keeping our wording close...
Records encrypted at rest
Profile fields and payment references sit encrypted while stored, and only staff with a named reason can open them. Every...
Role-based access
Support agents see your contact details and ticket history. Full payment credentials sit behind a separate permission held by very...
Retention clocks tracked
Each record type carries a set life span, and our systems flag anything past it. Erasure runs on schedule rather...
This Policy Next To Our Other Pages
Sibling pages handle their own subjects, and this policy is written to sit beside them without repeating them. Each entry below says what the other page covers and...
The Controls On Your Profile Page
Everything this policy describes has a switch on your profile, and you can reach each one without messaging anybody. Below is what you will see when...
Download your records
Ask for a copy of what we hold and we assemble one file covering profile fields, session history and payment references you have generated. It usually arrives within a few working days.
Switch off optional alerts
Email and SMS nudges are opt-in. Toggle them off and the change applies to future messages, with no effect on account notices you must receive under local rules.
Adjust consent choices
Where we rely on consent rather than a legal duty, you can withdraw it. Withdrawing may limit a feature, and we tell you which one before the change lands.
See active sessions
Your profile lists the devices signed in right now, with rough location and last activity. Sign out anything you do not recognise and tell us so we can check the login.
Request a correction
Spot a wrong phone number, a stale address or a misspelled name? Send the fix and we update the record, keeping a short log of what changed and when.
Close and erase
Closing your account starts erasure, though records tied to a completed transaction stay until their life span runs out. We write to you as each stage finishes.