LEGAL REFERENCE

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...

Plain-English summaryDated version headerRegion-specific clausesLive support route
555ace Your Data, Held To Our Policy

How We Apply This Policy

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

DATA REQUESTS

Reaching Us About Your Data

If a clause reads oddly or you want to see what we hold, our support desk answers privacy questions seven days a...

Live Chat Privacy Desk Open live chat from your account and a...
Written Data Requests Send a request from the address registered on...
In-App Policy Centre Your account area carries the current policy version...
WHO WROTE THIS

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...

Terms Of Use
The terms page covers what you may do inside the lobby, while this policy covers what we do with the data that activity creates, and the two are read together.
Account Rules
Sign-up requirements, verification steps and closure rights appear on the account rules page, while the policy explains which records each of those steps leaves behind on your file.
Payments Page
The page covering JazzCash, Easypaisa, SadaPay and Raast describes how those rails work; the policy describes how long the transaction references they create stay in our records after you withdraw.
Cookie Notice
The cookie notice lists the device-side storage we use for sign-in and language; this policy explains how those identifiers combine with the account profile we hold on you.
Security Wording
Our account-security writing explains sign-in protection and device checks, and the policy states clearly which of those signals we store for verification rather than for marketing use at all.
Contact Routes
Every policy page points to the same support inbox and chat entry, so a question about data never depends on which page you happened to be reading first.
Update History
Revisions carry a date and a short note, and older versions stay readable on request, which lets you check whether a clause changed after you opened your account.

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.

What You Ask About Data

It covers the personal data you give 555ace when you open an account, plus the records our lobby creates — sign-in activity, wallet references, support threads — and explains how we handle each.

Name, contact details, date of birth and your chosen payment reference, whether that is a JazzCash wallet, an Easypaisa account, a SadaPay card or a Raast-linked bank account.

Yes. Raise it through live chat or the support email, we verify your account reference, then send a written summary of what we hold and any correction we make.

References tied to your JazzCash, Easypaisa, SadaPay and Raast activity stay for the period our auditors set, after which they move to a deletion queue and are cleared.

We pass only what a payments provider or verification partner needs to complete a step you started, and we do not sell your personal data to outside advertising lists.

We publish the revised version here with a new effective date and show an in-app notice before a material clause applies, so you can read the wording first.