LEGAL REFERENCE

How we look after your account details

Open an account with 999sk game and this page tells you, in plain terms, how we handle the details you share. You can see what we collect, why...

What we collectWhy we need itHow long we keep itYour choices
999sk game How we look after your account details

The records behind your account

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

REACH OUR TEAM

Talk to us about your data

If anything in this policy is unclear, or you want to see the records tied to your account, our team will talk you through it. We answer in the order requests arrive, in English, during Pakistan daytime hours. Every exchange is saved against your account so you never explain the same question twice.

Team online

Live chat

Signed-in chat is the quickest route for data questions. Our team can open your account record while you wait and confirm what we hold about you.

Email

Write to our privacy mailbox and put 'account data' in the subject line. We reply from the same address each time, so the thread stays easy to follow.

Data request form

Ask for a copy of your records, a correction or a deletion from your account settings. We confirm each request in writing and give you a reference to follow.

HOW WE WRITE IT

Who writes and checks this policy

This policy is written by the people who run 999sk game accounts, not lifted from a template. Each colleague named below can explain why a field exists and...

Account operations

The colleagues who check sign-ups and process withdrawal requests write the sections on identity and payment records, because they handle...

Security desk

Our security colleagues confirm the wording on device logs, session data and sign-in alerts, and they retest the storage rules...

Payment reconciliation

Staff who match JazzCash, Easypaisa, SadaPay and Raast references to account balances confirm how long transaction records are kept and...

Support leads

Support leads read every data question you send and flag the paragraphs that keep confusing people, so we can redraft...

Change log

Each edit carries a date and a short reason. The log runs at the foot of the page, so you...

Plain-language check

Before anything goes live, a colleague outside the technical team reads it once and marks any sentence that needs shortening...

SAME RULES ACROSS PAGES

How this page fits our other pages

This page sits alongside the terms you accept at sign-up, our cookie notice and the page on sign-in security. The same definitions run across all of them, so words like account, payment...

01

Account terms

The terms you accept at sign-up set out the rules of use. This policy explains the data side of the same relationship, so the two are read together.

02

Cookie notice

Our cookie notice lists the small files your browser stores and why each one is set. Anything that identifies you personally is described here, in this policy, rather than there.

03

Sign-in security

That page covers passwords, device checks and what to do if you lose access. The records those checks create are described in the device-data section of this policy.

04

Shared definitions

Words such as account, deposit reference, session and deletion date carry one meaning across our pages. We keep a single glossary so no page redefines them.

05

One contact route

Whatever page raises your question, the same support team answers it. You will not be passed between departments to find out what we hold against your account.

06

Change dates in step

When a rule changes we update every page that mentions it on the same day and date each one. Older copies are removed so only the live wording remains visible.

07

Same language, same market

This page is published in Pakistani English for our Pakistan audience, and its sibling pages follow the same wording so nothing shifts meaning as you move between them.

INSIDE THIS PAGE

The layout of this policy page

We built this page so you can settle one question without reading all of it. A summary opens the page, section headings stay in a fixed order, and...

Summary block The opening block gives you the shape of the policy...
Fixed section order Sections always run from what we collect to how you...
Jump links A short row of links takes you straight to identity...
Date stamps Every block carries the date it last changed and a...
Plain summaries Technical paragraphs sit beneath a plain summary of the same...
Glossary strip Terms such as account holder, payment reference and retention period...

Questions we get about your data

Your name, date of birth, contact details and the payment reference for the JazzCash, Easypaisa, SadaPay or Raast transfer you use. We also keep device records for the times you sign in.

It is how we match money to the right account. Without it, a transfer can sit unclaimed, so we keep the reference with your balance record and use it for reconciliation and support questions.

Transaction and identity records stay for the period local rules require, then they are deleted. Device logs are kept far shorter, only as long as we need them to spot odd sign-ins.

Yes. Ask through the data request form in your account settings, or write to our support team, and we will send a copy of the records tied to your account in a few working days.

Only with processors that keep the platform running, such as payment partners routing JazzCash and Raast transfers and the studios streaming our live tables. They act on our instructions and cannot use your details otherwise.

We date the edit, describe what moved and publish the new wording on this page. If a change affects how your data is used, we also message the contact details on your account.