LEGAL REFERENCE

The Privacy Policy Behind Your zss999 Account

Opening an account with us means handing over a few personal details, so we keep this page updated with what happens to each one. You will see what...

Sign-up detailsWallet referencesDevice recordsCopy requests
zss999 The Privacy Policy Behind Your zss999 Account

How We Treat the Data You Hand Over

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

RAISING A REQUEST

Ways to Reach Us About Your Data

If something on this page needs explaining, or you want a record changed, you reach a person rather than a bot. Our...

Account message Sign in and send a message from your...
Email Write to our privacy desk with the details...
Callback Ask for a call at a time that...
WHO WRITES THIS

The People Who Keep This Policy Current

This page is maintained by the same team that runs accounts, payments and support, not by an outside writer. When a payment rail changes, a new identity check goes live, or a...

Version dates

Every edit carries a date at the foot of the page, so you can tell at a glance whether you are reading a newer version than the one you saved or printed earlier.

Change summary

A short summary of what shifted sits beside the date, written in everyday language rather than legal shorthand, so a change in how we handle your details is easy to spot.

Internal checks

Before anything goes live, our accounts and payments teams read the draft against what the platform actually does, and they flag any line that reads like a promise we cannot keep.

Regional differences

Where a province or region requires something different, we mark it inside the section it affects instead of burying it in small print, so you never guess which rule applies.

Plain wording

We avoid legal shorthand where an ordinary sentence works just as well, because a policy only helps you if you can read it once and understand what we do with your details.

Right to ask

You can question any line on this page at any time, and we will explain how that rule works for your account rather than pointing you back to the same paragraph.

SAME RULES EVERYWHERE

The Same Rules Across Our Policy Pages

Our policy pages share one set of definitions, so you are not reading a different story depending on which tab you open. A term used here means the same thing in our...

01

Shared definitions

Words such as account, personal data and payment reference carry one meaning across every policy page, so nothing changes when you move from here to another page.

02

Terms of use

The rules you accept when you open an account sit beside this policy and point back to the same definitions, which keeps the two documents from drifting apart over time.

03

Cookie notice

Our cookie notice explains the small files stored on your device, and it uses the same wording for tracking that appears in the sign-in records section of this policy.

04

Promo conditions

Any promotion you accept comes with its own conditions, and where those touch your personal details they follow the wording set out here rather than inventing fresh rules.

05

Identity checks

The verification steps across our pages are the same, whether you meet them at sign-up, at withdrawal, or when you update the mobile number saved on your profile.

06

Complaints handling

If you disagree with a decision about your data, our complaints page uses the same escalation steps and timeframes, and the same team picks up the case from there.

07

Language versions

The English and Urdu versions of our policy pages are updated together, and if a sentence ever reads differently, the English wording on this page is the one we stand behind.

Sections You Will See on This Page

We set this policy out so you can find an answer without scrolling through walls of text. A short summary opens the page, the detail follows...

Opening summary

A few lines at the start give you the shape of the policy, so you can tell within seconds whether the section you need sits further down the page.

Clear headings

Each heading names the exact subject underneath, from the details we collect when you join to the way sign-in records and device data are handled.

Tables for lists

Where a list works better than a paragraph, we set the facts out in a table, so you can run your eye down a column instead of reading the same things twice.

Retention timeline

A short timeline shows how long records stay with us after an account closes, with each period written out plainly rather than as a legal formula you have to decode.

Your controls

One block explains the switches inside your account, including the marketing preferences you can turn off without losing access to the lobby or your balance.

Contact block

Every route to our team sits together near the foot of the page, so you can send a message, email the privacy desk or request a callback without searching.

Data Questions We Hear Most Often

Your name, date of birth, mobile number and email address, plus the wallet or bank reference produced whenever you move money through JazzCash, Easypaisa, SadaPay, NayaPay or Raast.

No. A wallet transfer gives us a reference code and the amount, never your PIN or your login for that wallet, so those credentials stay with JazzCash, Easypaisa, SadaPay, NayaPay or Raast.

We hold account records while your account is open and for a set period afterwards, as regional rules require, then delete or anonymise the file. Where local law permits, you can ask sooner.

Yes. Send a request from your account or by email. Once we confirm your identity, we gather what we hold and send it in a readable format, usually within a few working days.

You can close your account whenever you like. We erase what we are allowed to erase straight away and keep only the records a regional rule requires us to hold for a fixed period.

Only to the providers needed to run your account, such as the wallet and bank rails behind JazzCash, Easypaisa, SadaPay, NayaPay and Raast, plus identity checks where local law permits.