LEGAL REFERENCE

Privacy Policy for your ti7 account

ti7 keeps one Privacy Policy for account details, casino activity records, sportsbook entries and Pakistan payment checks. Read it before you open your account so you know what...

Account data scopePakistan privacy contactJazzCash data contextPolicy change alerts
ti7 Privacy Policy for your ti7 account

How we handle your account data

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

CONTACT ROUTES

Ask us about privacy choices

Your privacy questions should reach people who can connect account records with policy wording. Use the route that matches your request, include...

Account privacy help Write to our support desk when you need...
Payment record query If your question involves JazzCash, Easypaisa, SadaPay or...
Security concern Contact us quickly if you think account access...
POLICY CONTROLS

How we keep this policy accurate

We write this Privacy Policy from our operating flow, not from a generic template. Each data point described here links to an account action, security check, payment trace, support ticket, or platform...

Account flow mapping

We map sign-up fields, login checks, profile edits, and device records against policy wording, so each collection purpose has a clear account reason rather than vague language.

Game record scope

Live table, slot, and sportsbook records are described as account activity data. We use them for balances, disputes, risk checks, and service logs linked to your account.

Payment trace clarity

Pakistan payment references are handled as transaction records, not profile decoration. We keep only the details needed to reconcile requests, protect balances, and answer account queries.

Security language checks

Our policy wording covers passwords, session tokens, device signals, and access alerts in plain terms. That helps you understand what is logged when account safety tools activate.

Support record handling

Messages you send to us may include screenshots, IDs, or transaction references. We treat those files as privacy-sensitive material and limit access to support handling.

Change tracking

When we update policy wording, we check the page against account screens and support scripts. Material changes are reflected here so your privacy reading stays aligned.

One privacy standard across ti7 pages

Your privacy rights should not change because you moved from the lobby to support, promotions, or account settings. This section explains how the same Privacy Policy logic follows...

Account pages
Profile screens collect contact, verification, and preference data. The policy treats those records as core account details used for access, support, and security checks.
Casino lobby
Casino pages create activity logs such as session time, game reference, balance movement, and device signals. We use those logs to run rounds and settle disputes.
Sportsbook area
Sportsbook activity, where available in supported regions, may include market choices, stake records, settlement status, and account balance changes for audit and support purposes.
Promotion screens
When you view a promotion, we may record eligibility checks and account interaction. The policy limits that data to account management and offer administration.
Support centre
Support conversations may contain contact details, payment references, screenshots, or device context. We keep them to answer requests and protect account history.
Security tools
Fraud and access controls may process IP address, device type, login time, and risk signals. These records help us protect accounts and investigate unusual activity.
Policy pages
Legal pages record ordinary site analytics and preference choices. We use those records to keep the policy page reachable, readable, and consistent for Pakistan access.

Policy layout points you can check

This Privacy Policy is arranged so you can find the data point that matches your question. We separate account identity, game records, payment context, cookies, support...

Data categories

The policy names account, device, transaction, game, and support data separately. That structure helps you see which details come from forms and which come from activity.

Purpose labels

Each data category is tied to a purpose such as account access, security, balance handling, dispute support, or service improvement, so the reason for use stays visible.

Sharing boundaries

We describe the service partners who may process data for hosting, payments, support, security, or analytics. We do not present sharing as an open-ended permission.

Retention signals

Retention wording explains that records stay only as long as needed for account operation, compliance, disputes, security checks, and service history connected with ti7.

Cookie choices

Cookie language covers site function, account security, preferences, and measurement. It explains why certain signals are needed when you browse or manage your account.

Request pathway

The contact section tells you how to ask about access, correction, deletion discussion, or security concerns. Verification may be required before account data is shared.

Privacy Policy questions from Pakistan

We collect account contact details, verification records, login signals, device data, game activity, transaction references, support messages, and preference choices. The exact data depends on how you use your account.

Payment-related data helps us reconcile JazzCash, Easypaisa, SadaPay and Raast activity, protect balances, handle disputes, and answer account queries. We use masked or limited references where full details are not needed.

We may share limited data with partners who help with hosting, security, payment reconciliation, analytics, and support tools. They process data for ti7 purposes and are not allowed to sell it.

We keep records for the period needed to operate your account, meet legal duties, resolve disputes, check security events, and maintain service history. Different record types may have different retention periods.

Yes. Contact support with the detail you want corrected and include enough account context for verification. We will check the request, confirm identity, and update eligible records where appropriate.

Cookies and similar signals help keep sessions active, protect sign-ins, remember preferences, and measure page performance. Some are needed for account functions, while others support service improvement.

We update this page when privacy wording changes. If the change is material, we aim to make it clear on the page so you can understand the updated handling before continuing.