Your Data, Held To Our Policy
This privacy policy governs how 555ace collects, uses and stores the account details you hand us when you open an account from Pakistan. Every deposit you clear through...
How We Apply This Policy
Where local law permits, this policy sets the minimum we do with your data and the extra steps we take in supported regions. We collect what you give us at sign-up — name, contact details, date of birth and your chosen payment reference — plus what your device sends when you use the lobby. We keep records of deposits and withdrawals cleared
through JazzCash, Easypaisa, SadaPay and Raast so your account history stays reconcilable. If a supported region needs shorter retention windows or a different verification step, those rules sit above this document and override it. Where a clause cannot apply in your region, the rest of the policy still stands. We publish updates here and tell you in-app before a material change takes
effect.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
The Team Behind These Words
This policy is drafted and maintained by the 555ace compliance and platform team, the same people who build the account flows you use day to day. Legal checks run against the regions...
Document Ownership
One named team owns this document end to end, so when a clause changes you can trace who signed it off, which region prompted it and when it went live.
Regional Checks
Before any clause applies in a supported region, our regional lead tests it against local expectations, and anything that cannot apply is flagged rather than quietly left in place.
Data Minimisation
We collect the fields the account actually needs to run, and we drop optional marketing flags from the sign-up form so you never hand over more than the service requires.
Retention Rules
Wallet and bank references tied to JazzCash, Easypaisa, SadaPay and Raast deposits stay on your record for the period our auditors need, then move to a deletion queue.
Access Control
Staff see your personal data only through scoped tools that record every lookup, and those permissions are audited on a schedule so access shrinks when a role changes.
Plain Language
Clauses are written in the same English you read on the rest of the site, and every revision keeps the older wording available so you can compare what moved.
How This Policy Lines Up
Our policy pages are written to agree with each other rather than contradict, so this document, our terms and our data-handling wording all describe the same account journey...
What This Page Sets Out
Scroll this policy page and you will find a dated version header, a clause-by-clause breakdown with anchors, and a plain-English summary sitting above the long-form text...
Dated Version Header
The header of the page states which version is live and the date it took effect, so you know whether you are reading the wording your account currently sits under.
Clause Anchors
Each numbered clause carries its own anchor, which means support can send you straight to the paragraph in question instead of asking you to hunt through the whole document.
Plain-English Summary
A short summary sits above the long-form clauses and restates the main points in everyday English, aimed at the same reading level as the rest of our Pakistan pages.
Change Markers
When a clause is revised, a dated marker appears beside it describing what moved and why, so you can follow the reasoning without comparing two versions on your own.
Region Flags
Clauses that behave differently in a supported region carry a visible flag naming that region, so you can tell at a glance which rules actually apply where you are.
Closing Contact Block
The closing block lists the chat entry, the support email and the hours we answer, so a data question never ends the page without somewhere obvious to take it.