Terms of use
Definitions for account, wallet and rail are mirrored word for word, so a phrase you learn here reads the same in our terms of use and nothing has to be re-interpreted.
Here is the privacy policy for tlml slots in plain English. It sets out what we collect when you open an account, how we store it, and which...
tlml slots applies this policy to every account opened from a supported region, and we follow it wherever local law permits. Data rules are not identical everywhere, so parts of this page may apply differently to you: where a Pakistani regulation or a regional privacy rule asks for more than we describe, that rule wins and we meet it for your account.
One principle stays fixed: we collect the minimum needed to open your account, clear your chosen rail and keep the lobby secure, and we never sell, rent or trade your identity. Where details must reach a payment partner, a processor or a regulator, we pass only the fields that partner needs. You can ask what we hold, ask for a correction, or
close the account and have anything we are not required to keep erased. Retention windows, age checks and transfer rules differ by region, so our desk confirms the position that applies to you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach our policy desk whenever something about your data does not add up. Agents confirm what we hold, log a correction or start a deletion request, and they can see which rail you used so the record is found without guesswork. We reply to written requests inside two working days.
Open the chat chip inside your account and pick data and privacy. An agent takes over between 9am and 11pm PKT and can confirm what our records hold for your profile.
Write to the privacy desk from your registered address and include your account reference. That lets us match the request to your profile without asking you for extra proof.
Ask for a field to be corrected or for your profile to be closed. We confirm in writing what changed, what was removed and what local rules require us to keep.
This page is written and checked by the team that runs the account systems, not by an outside agency. We name the rails, the retention windows and the...
We check every field before it reaches the account form and drop what we cannot justify. If a detail is...
Traffic between your device and our systems runs over an encrypted connection. Payment handoffs to JazzCash, Easypaisa, SadaPay and Raast...
Every admin view of a customer record is stamped with the operator ID, the time and the reason. We read...
Processors and payment partners are listed by role, not buried in a generic clause. When we bring in a new...
Each record type carries its own window in months, so you can see what outlives a closed account. Where nothing...
Every edit to this policy is dated and summarised at the foot of the page. We keep the earlier wording...
Every legal page on tlml slots shares the same definitions, so a term you read here means the same thing in our terms of use, our cookie notice and our payment terms...
Definitions for account, wallet and rail are mirrored word for word, so a phrase you learn here reads the same in our terms of use and nothing has to be re-interpreted.
The cookie notice breaks down each tag by purpose, and those categories match the ones this policy names, so you can line the two pages up without translating between them.
Timing and verification wording sits in our payment terms while the privacy side here covers what we store, so the two pages split one process without repeating each other.
Security steps such as password resets and device checks are described in the same order on both pages, so the sequence you read matches the screens you actually see.
Documents sent for verification are handled under the clause you find here. Our verification page states the same retention window and the same deletion route, so the two never contradict each other.
If you disagree with how a request was handled, the complaints route escalates to the same team named on this page, and the outcome is logged against your account record.
Our contact page lists the same chat chip, email and postal route used for data requests, so you never have to guess which channel reaches the privacy desk.
This page is built to be read on a phone first. Headings carry the topic, a short summary box sits just under the headline, and each...
A short index sits under the headline and links to each clause, so you can reach the retention paragraph or the sharing paragraph without scrolling the whole page on your phone.
A boxed summary under the headline gives the five points that matter most, and every one of them points down to the full clause it came from.
A dated line above the first clause records when the wording last changed, so you can tell at a glance whether the version you are reading is newer than the one you saved.
The chip row names the Pakistani rails we support here, and tapping a chip jumps to the clause that describes how that rail's data is handled.
A print view strips the navigation and leaves clean clauses, which is useful if you want a copy for your own records or for a bank query later.
A short history at the foot lists each revision with its date and the clause it touched, so older wording can be traced without emailing our desk.