LEGAL REFERENCE

Your Data Terms, Written Plainly

pak555 keeps one page for how account details, wallet records and session data are handled from the moment you open an account. Below, we explain what we collect...

Account dataWallet recordsSession logsYour settings
Explore The Lobby Read FAQ
pak555 Your Data Terms, Written Plainly

Where This Policy Applies

pak555 serves customers in supported regions, and this page explains how we handle personal data where local law permits. When you register from Pakistan we record your name, phone number, email and date of birth to confirm you are eligible for an account. Wallet details tied to JazzCash, Easypaisa, SadaPay and Raast stay masked: we keep the reference number needed to match

a transfer, not your full wallet credentials. Sign-in times and IP addresses help us spot unusual access early. Where a regulator, bank or court asks for records, we release only what the request covers and tell you when we are allowed to. Closing an account does not wipe everything at once; tax and anti-fraud rules require some records to stay for a

set period.

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

REACH THE TEAM

Talking To Us About Your Data

We answer privacy requests through three routes, and each one reaches a person rather than a queue robot. Live chat runs during Pakistan evening hours, email is answered within one working day, and in-account messages stay attached to your profile so nothing gets lost. Say what you need changed and we confirm in writing.

Team online

Live chat

Open live chat and a Pakistan-based agent picks up during evening hours, seven days a week. Every data request gets a reference number you can quote later.

Email desk

Write to our privacy mailbox and we reply within one working day, usually sooner. Include your account email so we match the request without asking you twice.

Profile tools

Inside your profile settings you can edit your details, close the account, or request a copy of the records we hold. Both actions confirm by email before anything changes.

WHO WRITES THIS

The People Behind This Policy

This policy is written and kept by the pak555 account and payments team, the same people who handle identity checks and wallet disputes daily. Nobody outside that group...

Policy owner

One named account lead owns this page, checking it each quarter against how our systems actually behave. If the two...

Wallet handling

The payments team documents which references we store for JazzCash, Easypaisa, SadaPay and Raast, and which we discard once a...

Support leads

Agents flag confusing clauses during chat shifts, and that list forms the change log for the next published version of...

Security desk

Our security desk watches access logs for odd sign-ins and decides when a session must be cut, feeding the data...

Local context

We read this page with Pakistani customers in mind: wallet rails, support hours and the languages our agents speak are...

Revision history

Every change gets a date near the page title, and older versions stay archived internally so we can show what...

Staying Consistent With Our Other Pages

Everything we publish lines up with the same commitments you find on our terms of use, cookie notice and account closure page. The wording differs because each page...

Terms of use
Account rules live on the terms page, while this page covers what we do with your details. Both share one definition of an account holder and one complaint route.
Cookie notice
The cookie notice lists each tag we run and how long it lives. This policy explains why those tags exist and which ones you can switch off yourself.
Wallet terms
Wallet terms describe how JazzCash, Easypaisa, SadaPay and Raast transfers settle, while the privacy side states which reference numbers we keep afterwards and nothing beyond them.
Account closure
Closure takes effect immediately for sign-in, but record retention follows tax and anti-fraud rules. The closure page lists the exact period for each record type, and this page explains the deletion step.
Identity checks
Verification rules set out which documents we ask for and when. Here we add the storage side: how long scans stay, who opens them and when they go.
Complaint handling
If you disagree with how a request was handled, the complaints page sets the escalation order. Privacy disputes follow that same ladder, with a named case handler at each step.
Revision dates
Each policy page carries its own revision date. When one changes we check the others for knock-on edits, so nothing quietly falls out of step. That check is scheduled, not left to chance.
INSIDE THE LAYOUT

How This Policy Page Is Built

You will notice the same layout on every policy page here: plain headings, jump links down the side, and a short summary above each long clause. Wallet names...

Jump links A sticky side menu takes you straight to the clause...
Plain headings Headings use everyday words rather than legal shorthand, because a...
Summary boxes Long clauses open with a two-line summary in bold before...
Rail chips JazzCash, Easypaisa, SadaPay and Raast appear as labelled chips wherever...
Version stamp The revision date sits near the title with a short...
Contact block Live chat, email and in-account messaging sit together at the...

Data Questions We Hear Often

We ask for your name, phone number, email and date of birth to confirm eligibility, then log device and sign-in data as you use the account. Documents come later, when a rule requires them.

No. We only keep the transaction reference and masked account identifier needed to match your transfer. Full wallet logins never reach our systems, and the same applies to Raast and NayaPay.

Sign-in stops straight away, but tax and anti-fraud rules require some records to stay for a defined period. We delete each set when its window closes and confirm in writing.

Yes. Request one through live chat, email or your profile settings, and we reply within one working day with the file and a short explanation of each field.

Staff who need them for verification, wallet matching or a request you raised. Every lookup is logged, and anyone outside that group is blocked at the account level.

We date the new version near the page title and note what moved. Material changes reach the email on your account before the update takes effect.