Account terms
These cover your side of the deal, such as keeping your sign-in details private and using one account only. The privacy wording covers what we do with the profile behind it.
LEGAL REFERENCE
How temi slot Handles Your Account Data
temi slot runs one plain-language policy covering everything your account touches, from a JazzCash, Easypaisa, SadaPay or Raast transfer to the slot rooms and live tables you open...
What we holdWhy we keep itHow to ask usWhere law permits
Where This Policy Applies For You
temi slot treats this policy as the single reference point for personal data on our platform, and it takes effect the moment you open an account, whether you sign in from Pakistan or from a supported region abroad. We hold three kinds of record: what you type in at registration, what your device reports when you load a page, and what our
payment partners confirm once a transfer clears. We name JazzCash, Easypaisa, SadaPay and Raast only as rails we work with, so you can see which transaction records sit with us and which sit with your provider. Where local law permits, we may keep records longer to answer an audit or a regulator request. Where local law is stricter, the stricter rule wins
and our retention window shortens to match.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
REACHING OUR DESK
How To Contact Us About Your Data
Privacy requests get their own queue, so you are not pushed through the same thread as a game or wallet query. Write from the address on your account and we can match the request to your profile without asking for anything extra. We read that queue daily, weekends included. Use the email on your profile; one line is enough to start.
Team online
Privacy email desk
Send a note from the address tied to your account and we can trace your profile straight away. Say which page or feature is involved and what you want changed.
Message from your account
Signed-in messages carry your account reference automatically, which saves a round of questions. Use this route when the request touches a payment rail or a table session. It lands there.
Written outcome
Every request ends with a written answer, even when we cannot action it. If we need more time we say so and give you a date for the reply.
KEEPING IT CURRENT
The Team Behind This Policy
This policy is maintained by the same people who build and run the temi slot account system, not written once and shelved. When we add a feature, a sign-in step or a...
Written by operators
The draft comes from the team running accounts, transfers and support queues daily, so the wording reflects how the systems behave behind the interface you use today.
Checked before release
Every edit passes a second reader who looks for commitments we cannot keep, vague timelines, and any gap between what the page promises and what our desk can deliver.
Plain language first
We keep sentences short and avoid legal padding, because a policy you cannot follow is a policy that fails you. Where a term is unavoidable we explain it there.
Updated on a schedule
The page is read on a fixed cycle and whenever a product change lands. Each revision moves the date line so you can see how fresh the wording is.
No hidden clauses
Anything that affects your data sits in the main text, never a footnote. If a section changes in a way that shifts your rights we flag it at the head.
Open to challenge
If a line reads badly or seems to promise more than we can honour, tell us. Reader feedback has shaped real edits, including how we describe retention windows.
CONSISTENT ACROSS PAGES
One Set Of Rules Across Our Pages
Our privacy wording does not stand alone. It sits beside the account terms, the cookie passage and the complaints route we publish for Pakistan, so you never find two pages telling you...
Cookie passage
That page explains the small files that keep you signed in and remember your language. Here you learn why those files count as personal data and how long they live.
Payment record terms
This page sets out which transaction details our rails partners hold and which stay with us, sharing the same definitions used here for JazzCash, Easypaisa, SadaPay and Raast rows.
Complaints route
If a reply from our desk does not settle your question, the complaints page lists the next step and its timeframes. Data disagreements follow exactly the same path.
Help pages
Those articles handle game rules, wallet steps and sign-in fixes. When one touches personal data we link back here rather than repeating wording that could drift apart over time.
Updated date line
One date sits at the foot of every legal page so you can tell which version is live. If two pages show different dates, read the later one.
Language versions
We publish in English for Pakistan and keep the same meaning across translations. If a translated line reads differently, the English version governs and we fix the other copy.
Layout Elements That Carry This Policy
The page is built to be skimmed before it is read. A summary strip at the head shows the shape of the wording in a few...
Summary strip
A short block at the head lists the four or five points you ask about most, so you get the shape of the wording before the numbered clauses.
Rail chips
Coloured chips name each rail referenced in the text, so you can see which transaction records the clauses cover before you reach the detail.
Numbered clauses
Each block carries a number and a short heading, which makes it easy to quote one point when you write to our desk, and helps us trace edits later.
Date line
The revision date sits in the same spot every time, so you can check how fresh the wording is in a second without scrolling through it again. Nothing shifts around.
Contact block
A single block near the foot gathers the desk address and the account-message route, so you do not have to hunt through clauses to find where to write.
Print-friendly view
The wording prints cleanly without menus or images, so a paper copy for your records stays readable. Nothing hides behind a login. Every clause shows on the printed sheet.
Questions We Hear About Your Data
We hold what you type in to register, what your device reports on each visit, and what our payment partners confirm once a transfer clears. That covers your name, contact line and references.
We share only what a rail needs to move money, such as the amount, the reference and the account you are paying into. Nothing beyond that leaves our systems.
An open account keeps its details for as long as it stays open. After you close it we hold a shorter tail for audit and dispute reasons, then delete.
Yes. Write from the address on your account and ask. We confirm what we hold, correct anything wrong and erase what we are not required to keep, then tell you what we did.
They can, and we treat them that way. A sign-in cookie and a device identifier both help us keep your session secure and spot an unfamiliar login, so they sit under the same wording.
Access is limited by role. Support staff see what they need to answer your query, and finance staff see transaction lines only. Every lookup is logged and checked.