Shared definitions
Terms such as account data, wallet reference and activity log carry one fixed meaning across every timislots game policy page, so nothing shifts with the page you open.
Every account you open with timislots game carries a data record, and this page sets out what we keep, why we keep it and how long it stays...
We handle personal data under the rules that apply where you are, so access to parts of timislots game depends on what local law permits in your region. From Pakistan, we treat your registration fields, the JazzCash, Easypaisa, SadaPay or Raast reference attached to a wallet, gaming activity logs and support chats as account data. We hold the minimum needed to run
your account, confirm identity when required, settle withdrawals and keep the records our supported regions expect. You can request a copy of what we hold, correct a wrong field, or close the account and have routine data removed inside the retention windows we must follow. Cookies split into those that keep you signed in and those that show how lobby pages load
on your handset.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
When you want to see, change or erase something we hold, raise it with our support desk and we log the request against your profile. In-app chat handles quick points, email suits document requests, and our Pakistan lines stay open 8am to 2am, seven days a week.
Open the chat tab inside your signed-in account and an agent picks up your privacy request, sends a reference number and tracks the thread to a written close.
Write from the address saved on your profile so we can confirm ownership, then send identity documents only through the secure upload link our team replies with.
Ring our Pakistan number between 8am and 2am local time for account access problems, wallet reference checks, or to chase a request that is already open.
The page you are reading is maintained by the team that runs timislots game rather than an outside writer. A compliance lead signs off every wording change, our platform engineers confirm the...
Written by the compliance team at timislots game, so the wording lines up with how our own systems store wallet references, chat transcripts and gaming activity records.
Every update carries a revision date at the foot of the page, and we hold earlier versions for two years so you can compare what moved and when.
Before publishing, our platform engineers confirm each technical claim, checking that cookie groups, log retention windows and deletion jobs behave the way the text describes.
We draft in clear Pakistani English with no legal padding, so someone holding a JazzCash or Easypaisa wallet reads the same points a lawyer would take from it.
Links from this page point to our own policy pages only, and nothing here blocks the full text behind an account step or a wallet transaction.
If our answer to a data request misses the mark, ask for the compliance lead by name and a second person inside the team picks up the thread.
This page sits alongside our terms, cookie and account rules, and we keep one set of definitions across all of them. Where a phrase appears in two places it means the same...
Terms such as account data, wallet reference and activity log carry one fixed meaning across every timislots game policy page, so nothing shifts with the page you open.
Retention periods for chat logs, wallet records and gaming history are quoted the same way here and in our account terms, so the numbers never disagree.
The cookie groups described on this page mirror the table on our cookie page: necessary cookies keep a session open, while optional ones measure how lobby pages load.
The chat tab, email desk and Pakistan phone line listed here are the channels quoted in our account terms, so you never chase an address that has stopped working.
JazzCash, Easypaisa, SadaPay and Raast references are described the same way everywhere, separating what our systems store from what the provider holds on its own side.
When a rule moves, we amend every affected page in one release and stamp them with the same revision date, so no document quietly falls behind the others.
Closing your account clears the same data sets whichever page you read first, with the retention exceptions listed here and repeated in our account terms.
Laid out for reading rather than scrolling past, this page opens with a short summary and then walks through storage, sharing and deletion in order. Headings...
The opening card gives the short version first, naming what we collect from a new account and what we leave alone, before any longer clause appears on screen.
A section moves through each data set in turn, from registration fields to wallet references, setting out where it sits and how long it stays on our systems.
Wallet references sit in their own block, explaining which JazzCash, Easypaisa, SadaPay, NayaPay or Raast details our team can view once a transfer settles.
One card names every case where account data leaves our platform, from identity screening to fraud checks, and states plainly that we do not sell profile data.
Controls for downloading a copy, correcting a field or closing the account sit together, each with the response window you can expect after your request reaches the desk.
The foot of the page carries the current revision date plus a short line on what changed, so a returning reader spots updates without reading the whole document again.