LEGAL REFERENCE

Privacy Policy For Your Account

ti 2022 explains how we collect, use and protect the data linked to your casino, sportsbook and wallet activity in supported regions of Pakistan. Open your account with...

Pakistan account privacyWallet data handlingSecurity checksSupport contact paths
ti 2022 Privacy Policy For Your Account

How Our Privacy Policy Works

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

CONTACT ROUTES

How To Reach Us About Privacy

If you want to ask about your data, correct account details or request access to records we hold, use the contact route that matches your issue. Our team may need account checks before discussing private details, especially when a request involves wallet records, withdrawal status or login history.

Team online

Privacy email

Send privacy requests to our support mailbox with your account mobile number and a short reason. We use that detail to locate records without asking you to repeat sensitive data in chat.

Live chat check

Use live chat for quick privacy questions about data use, account access or correction steps. We will ask verification questions before discussing wallet references or recent account activity.

Wallet query path

For JazzCash, Easypaisa, SadaPay or Raast privacy queries, share only the reference number shown in your wallet app. Our team matches it to internal records before replying.

CHECKED TEXT

How We Keep Policy Text Accurate

We write this Privacy Policy from the way ti 2022 actually operates. Our legal, support and payments teams check the wording against account flows, wallet handling, security controls and contact steps before...

Account flow mapping

We compare each privacy clause with the account screens you use, including mobile number entry, password reset, profile edits and access checks, so the policy reflects real data collection points.

Payment record checks

Wallet references from JazzCash, Easypaisa, SadaPay and Raast are handled as account records. Our policy explains why we keep them, who can see them and when sharing may apply.

Security wording

Our security team checks privacy language around encryption, access logs and account alerts. We describe these controls in plain English so you understand how data protection works.

Support alignment

Support scripts are aligned with this Privacy Policy, including what agents can ask, what they should not request and how privacy questions move to a safer contact path.

Change records

When we adjust this Privacy Policy, we keep an internal record of the change, the reason and the team that approved it, helping us answer questions about older wording.

Plain language

We avoid legal clutter where possible and explain privacy duties in everyday Pakistani English, especially for account checks, wallet matching, device data and customer contact.

Consistency Across Related Legal Pages

Your privacy rights should not change depending on which legal page you open. We keep our Privacy Policy aligned with account terms, cookie language, wallet procedures and support...

Account terms
Our account terms explain service access, while this Privacy Policy explains the personal data behind that access. We keep names, verification language and contact steps consistent across both pages.
Cookie wording
Cookie text deals with browser storage and device signals. This page connects those signals to privacy purposes such as login safety, session continuity and fraud checks.
Wallet procedures
Payment pages describe how wallet transfers appear. This Privacy Policy explains how related references, sender details and support messages are stored and used for account matching.
Support process
Help pages show how to reach us. This policy explains what support may collect during contact, how identity checks work and why some answers require extra verification.
Security notices
Security messages may appear when access looks unusual. This page explains the privacy side of those checks, including device signals, login records and account protection steps.
Withdrawal records
Withdrawal pages focus on processing status. Our Privacy Policy explains the record keeping linked to name checks, wallet references, timing queries and compliance requests where required.
Policy updates
Related legal pages may change at different times, but privacy wording is checked for consistency whenever account data, wallet handling or support verification steps are updated.

Privacy Cues Across The Page

We design our privacy layout so you can find key points without searching through dense legal wording. The visible cues on this page point to collection...

Clear section labels

Each block uses a short label so you know whether the text covers collection, security, sharing or contact. That structure helps you move through privacy matters without confusion.

Local context chips

Short chips name Pakistani wallet rails only when they matter to privacy. They remind you which payment references may connect to account matching and support verification.

Plain request steps

Contact instructions explain what to send and what to avoid sending. We want privacy requests to reach the correct team without exposing extra personal data.

Security prompts

Where privacy and account safety meet, we flag verification needs clearly. That includes login changes, wallet disputes, device checks and requests involving sensitive account records.

Update visibility

Policy changes are written so you can spot what affects account data, wallet records or contact choices. We aim to keep revisions readable, not buried.

Direct wording

We describe what we collect, why we collect it and when sharing may happen. The layout keeps legal wording close to the account action it relates to.

Privacy Policy Questions From Pakistan

We collect data needed to run your account, such as your name, mobile number, login records, device signals, wallet references and support messages. We avoid asking for details that are not needed for account handling.

Wallet references help us match JazzCash, Easypaisa, SadaPay and Raast activity with the correct account. They also help support investigate delays, correction requests and privacy questions linked to transaction records.

Yes, you can contact support and ask for access to records linked to your account. We will verify you first, then explain what data can be shared and any lawful limits.

We use access controls, staff permissions, encrypted storage where suitable and activity logs. These controls reduce unnecessary access and help us detect unusual changes involving account or wallet-related privacy records.

We may share limited data with payment partners when needed to verify wallet activity, resolve a transaction query or meet a lawful request. We share only the details relevant to that purpose.

Contact support with the account mobile number and the detail that needs correction. We may ask for verification before updating private records, especially when the change affects wallet matching or withdrawals.