Terms page connection
Our Terms describe account conditions; this Privacy Policy explains the personal data used to create, secure and manage that account under those conditions.
LEGAL REFERENCE
Privacy Policy For Your t20 Account
t20 keeps your account, device, payment and support data explained in one Privacy Policy before you open your account. We show what we collect, why we use it...
Account dataJazzCash contextSecurity checksSupport access
How We Handle Your Data
This Privacy Policy explains how t20 processes data when you create an account, verify access, use payment rails and contact support from supported regions where local law permits. We collect only the details needed to run your account flow, protect balances, answer privacy requests and meet record duties that apply to our service. Payment references from JazzCash, Easypaisa, SadaPay and Raast are
used to match your own transactions with your account, not to sell your financial profile. Device and session data help us detect unusual access, keep the lobby stable and reduce misuse. We keep records for limited periods based on legal, security and support needs, then delete or anonymise them when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How We Keep Policy Text Current
Our Privacy Policy is maintained by people who work with account, payment, security and support flows inside t20. When a form, wallet step or verification process changes, we check whether the policy...
Change log discipline
Each policy change is logged internally with date, reason and owner, so our team can trace why wording moved and which account process it reflects.
Local payment mapping
We map privacy wording to JazzCash, Easypaisa, SadaPay and Raast steps, including transaction references, sender matching and verification checks used for account safety.
Security team input
Access logs, device markers and unusual session checks are described with input from our security team, not copied from a generic legal template.
Support script alignment
Support replies are checked against this Privacy Policy, so the answer you receive about correction, access or deletion follows the same wording.
Retention checks
We connect retention periods to real needs such as account disputes, wallet matching, fraud prevention and legal record duties before data is removed.
Plain English editing
We write this page in clear Pakistani English, keeping legal meaning intact while avoiding dense phrasing that makes your privacy choices hard to understand.
LEGAL CONSISTENCY
Consistency Across Our Legal Pages
This Privacy Policy sits beside our other legal pages, but it has a separate purpose: it explains personal data handling. We keep wording aligned where topics touch, such as account verification, support...
Cookie notice connection
Cookie wording covers browser storage; this policy explains how those signals may connect with sessions, device checks and account safety records.
Promotions rules connection
When a promotion needs eligibility checks, this page explains which account records may be used and why access is limited to authorised staff.
Support page connection
Support pages tell you how to contact us; this policy explains how chat logs, email history and identity checks are stored.
Security page connection
Security wording explains access protection; this policy states how device markers, login times and alert records are handled during that protection.
Closure request connection
If you close an account, this policy explains which records can be deleted quickly and which may stay for legal or dispute reasons.
Wallet help connection
Wallet help explains transaction steps; this policy explains how JazzCash, Easypaisa, SadaPay and Raast references are matched with your account.
PAGE MARKERS
Privacy Layout You Can Scan
We designed this Privacy Policy page so you can find the privacy point you came for without reading unrelated material first. The layout separates data categories, reasons for...
Short privacy summary
The page opens with a short statement covering account, payment...
Data category blocks
Separate blocks explain identity details, wallet references, device signals and...
Purpose labels
Each data category is tied to a purpose label, such...
Retention prompts
Retention prompts explain why some records stay for a period...
Choice panel
A choice panel lists how you may ask for access...
Update marker
A visible update marker helps you spot material wording changes...
Privacy Questions We Hear Often
We collect account details you provide, access records from your device, verification results and support messages. We use them to run your account, protect access and answer privacy requests.
We use wallet references to match your transaction with your account, confirm sender details and resolve support queries. We do not use those references to build unrelated financial profiles.
Yes. Contact us through chat or email after account checks are complete. We may ask for proof before changing personal data, especially phone, email or wallet details.
Device and login records help us detect unusual access, protect balances and investigate account concerns. We keep them only for periods tied to security, support or legal needs.
Only authorised team members who need the messages for support, privacy handling, security checks or dispute work can access them. Access is limited and linked to internal roles.
We update the policy date and adjust the wording where account flow, payment handling, security checks or legal duties change. Material updates are placed where you can see them.