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.
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...
Our privacy posture is built around the practical account flow you use on bt 21: opening an account, entering the lobby, choosing a table or market, sending payment proof, requesting a withdrawal, and speaking with support. We collect only the data needed to run those steps, protect account access, confirm payment status, investigate disputes, and meet lawful requests in supported regions. Pakistan
payment rails such as JazzCash, Easypaisa, SadaPay and Raast may create transaction references, sender names, wallet numbers, timestamps and bank response messages. We use those records to match your request with your bt 21 balance and to reduce mistaken credits. We do not sell your personal data. Access inside our team is limited by role, logged where practical, and checked when policy
wording changes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
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...
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.
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.
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.
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.
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.
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.
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...
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.
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.
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.
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.
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.
Security statements cover account protection. This policy explains the related data, including device signals, failed login records and alerts used to reduce unauthorised 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.
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...