LEGAL REFERENCE

Privacy Policy for bt 21

bt 21 links your account, lobby activity, support chats and Pakistan payment traces to one privacy framework. Before you open your account, this policy explains what we collect...

Account dataCookie choicesPakistan payment tracesSupport privacy
bt 21 Privacy Policy for bt 21

How we handle your data

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

HELP ROUTES

Privacy contact paths at bt 21

Privacy questions should reach the team that can see account records, payment references and device signals without moving your data through unnecessary...

Account desk Use account support when your name, phone number...
Payment privacy Use the payment contact path for JazzCash, Easypaisa...
Cookie requests Ask the support team about browser cookies, device...
DATA CHECKS

Policy checks behind the page

We write this privacy policy from our own operating records, not from generic legal filler. The wording is checked against the account screens, payment queue, live chat process, cookie banner and withdrawal...

Role access

Staff access is separated by task, so a support agent does not automatically see the same payment trace as a finance checker. This reduces casual exposure while still allowing service work.

Payment matching

Transaction references from JazzCash, Easypaisa, SadaPay and Raast are used to match your request with your account. We keep enough detail to resolve disputes without asking for private wallet secrets.

Session records

Login time, device type, IP region and browser signals help us spot unusual access. These records also help you recover an account when your phone or email changes.

Cookie labelling

Cookies are grouped by purpose, including login memory, security checks, preference saving and measurement. Where a cookie is not essential, we explain why it exists before using it.

Support logging

Chat and email messages may be stored with timestamps so we can continue a case, verify what was asked, and check whether a privacy request was handled correctly.

Policy edits

When wording changes, we compare it with current account, payment and support flows. This keeps the page tied to real bt 21 practice rather than broad legal phrasing.

POLICY MATCH

Consistency across our legal pages

This privacy policy sits beside our terms, cookie wording and account rules, so each page needs to speak clearly without repeating the same legal text. The privacy page focuses on personal data...

01

Terms page

The terms explain account use and site rules, while this page explains the personal data involved in those rules. We keep the split clear so you can find privacy duties quickly.

02

Cookie wording

Cookie wording explains browser storage in more detail, but this policy states why cookies matter for account access, security, preferences and measurement across the bt 21 site.

03

Payment records

Payment pages may explain steps for JazzCash, Easypaisa, SadaPay or Raast. This policy explains which references may be stored and how those references support account balance checks.

04

Withdrawal checks

Withdrawal rules cover timing and verification steps. This privacy policy explains the identity, transaction and account records used when our team checks a payout request.

05

Support terms

Support pages tell you where to contact us. This policy explains how messages, attachments and case history may be kept when you ask for privacy help.

06

Security wording

Security statements cover account protection. This policy explains the related data, including device signals, failed login records and alerts used to reduce unauthorised access.

07

Regional access

Access wording may mention supported regions. This policy explains how region signals can be used to apply local access rules and answer lawful data requests.

SCREEN DETAILS

Visible cues inside this policy

We designed the policy page so you can scan privacy points before you create or adjust an account. Headings separate account data, payment traces, cookies, retention and contact...

Plain headings Each heading names the data practice it covers, such as...
Local chips Chips mention JazzCash, Easypaisa, SadaPay and Raast because those references...
Short explanations We keep paragraphs direct so you can see why data...
Action wording Where you can ask for a correction, copy, deletion or...
Device clarity The policy names device and session signals because they affect...
Change markers When the privacy wording changes, we aim to make the...

Privacy Policy questions answered

We collect the account details you provide, login signals, device data, region checks and security records. If you use Pakistan payment rails, related references may be stored to match funds and resolve disputes.

We may use payment references from JazzCash, Easypaisa, SadaPay or Raast to confirm a transaction, but we avoid sending more personal data than needed for matching, verification or dispute handling.

Cookies support login sessions, security checks, saved preferences and site measurement. Some cookies are needed for account access, while others can be adjusted where the browser or cookie panel allows.

Yes, you can contact support to correct account data that is outdated or wrong. We may verify your identity first, especially when the change affects payments, withdrawals or account recovery.

We keep payment references for as long as they are needed to confirm balances, answer disputes, meet lawful requests and maintain financial records. Retention can vary by record type and supported region.

Do not send full wallet passwords, one-time codes, complete bank secrets or private screenshots with unrelated data. Mask sensitive parts and share only what helps us identify the account or transaction.

When this privacy policy changes, we update the page wording and may highlight material changes near the relevant section. You should check this page before changing account or payment details.