How ti8 Handles Your Data
ti8 keeps live casino, slots and sportsbook access under one account, and this Privacy Policy explains what data we collect when you open that account. Read it before...
Our Privacy Policy Posture
This Privacy Policy describes how ti8 collects, uses, stores and shares personal data linked to your account in supported regions. We collect details you provide during account creation, identity checks, payment handling, support contact and security checks. We also use cookies and device signals to keep sessions stable and detect unusual access. Payment references from JazzCash, Easypaisa, SadaPay and Raast are handled
as transaction context, not as public profile content. We may share limited data with vendors that host, secure or process parts of ti8, but only for the purpose stated here. Where local law permits, you can ask us to access, correct or erase eligible account data, subject to security, payment and legal record needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Clear
We write this Privacy Policy from our own account, support and payment workflows rather than using generic wording. Each privacy statement is checked against how ti8 actually collects...
Policy ownership
Our privacy text is maintained by the ti8 operations team that handles account access, payments and support records. That keeps...
Local rail mapping
We separate payment rail references from card-free wallet details, so JazzCash, Easypaisa, SadaPay and Raast records appear in the policy...
Access safeguards
Password resets, device checks and login alerts are described in plain terms because they affect personal data. We explain what...
Retention schedule
The policy distinguishes active account records from records we keep for security, payment reconciliation or legal requests. Timelines are written...
No hidden sale
We do not present personal data as a product to sell. Where vendors help us host, analyse or secure ti8...
Readable changes
When the privacy text changes, we date the page and explain material changes in account-facing language. You can compare what...
How This Policy Connects Across ti8
Privacy does not sit alone on ti8. Our terms, cookie wording, security messages and support scripts all need to say the same thing about data use. This section...
| Cookie wording | Cookie text explains browser storage, session tools and preference choices. The Privacy Policy gives the broader purpose, while the cookie page handles the setting-level detail you see on your device. |
|---|---|
| Account terms | Our account terms explain access rules, while this Privacy Policy explains the data collected to apply those rules. The two pages are kept consistent on identity checks and session records. |
| Security messages | Login alerts, reset emails and device warnings must match this policy. When we mention security logging, the same purpose appears here so you can see why data is processed. |
| Support scripts | Support agents use privacy-approved prompts when they ask for account details. We avoid asking for full wallet credentials and keep identity checks limited to what the request needs. |
| Payment references | Payment pages may show JazzCash, Easypaisa, SadaPay and Raast steps. This policy explains how the related references are stored, checked and limited inside account records. |
| Promo preferences | If we send account messages, this policy explains the data used to select and deliver them. You can change eligible preferences without changing core security or payment notices. |
| Change handling | When a related page changes how data is described, we check this Privacy Policy as well. That prevents mixed wording across account, cookie, payment and support screens. |
What The Privacy Page Shows
This page is arranged so you can scan the privacy points before creating or managing a ti8 account. The layout highlights what data is collected, why...
Date marker
The page carries an update marker so you can tell when the wording last changed. We use that marker to separate current privacy terms from older account-facing language.
Plain headings
Section headings use direct privacy wording, such as data use, cookies, retention and access requests. This helps you find the legal point without reading unrelated platform copy.
Local context chips
Short chips name Pakistan payment rails only when they matter to privacy handling. They remind you that transaction references may be processed differently from profile or support data.
Request prompts
Contact prompts show the minimum details we need to locate your account data. We avoid asking for full wallet credentials, passwords or unnecessary screenshots in privacy requests.
Purpose labels
Where a data category appears, the page pairs it with a purpose such as account access, fraud checks, support handling or payment reconciliation. That keeps collection reasons visible.
Rights summary
The rights area explains how eligible access, correction or erasure requests work in supported regions. It also says when records may remain for security, payment or legal needs.