Account Terms
Our account terms describe service rules, while this Privacy Policy explains data handling. Where both pages mention verification, this page controls how personal data is collected and protected.
LEGAL REFERENCE
Privacy Policy For Your tu 46 Account
tu 46 keeps account data, KYC checks, live casino activity records and Pakistan payment references in one privacy flow, so you know what we collect before you open...
Pakistan data handlingKYC record careAccount securityPayment reference privacy
How We Handle Your Personal Data
This Privacy Policy explains how we collect, use, store and share personal data when you open, access or manage a tu 46 account from supported regions in Pakistan, where local law permits. We collect account details you provide, device and session records, KYC documents needed for checks, gameplay logs tied to your balance, and payment references linked to JazzCash, Easypaisa, SadaPay or
Raast. We use this data to run your account, verify withdrawals, detect misuse, answer support requests, maintain security, and meet legal duties that apply to our service. We limit access inside our team, keep records only for needed periods, and apply technical controls so your account history is handled with care.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Privacy Questions And Data Requests
If you want to ask about this Privacy Policy, correct account data, or request access to records we hold, contact us from the account area first. That route helps us match your request to your verified profile, reduce impersonation risk, and respond with the right privacy context.
Team online
Account Centre
Use the secure account message form for privacy requests tied to KYC, login records, withdrawal checks, or payment references. We may ask for extra confirmation before discussing sensitive account data.
Email Privacy Desk
Send privacy questions to the address shown inside your account area if you cannot log in. Include your account email and avoid sending full card, wallet, or identity numbers.
Live Help Escalation
Our support team can route privacy concerns to the right internal contact. Chat is useful for status checks, but document access or correction requests may need account inbox follow-up.
PRIVACY CHECKS
Controls Behind This Privacy Policy
We write this policy from the way tu 46 actually operates: account creation, KYC screening, wallet checks, live table sessions and support contact all create records. Our privacy controls are designed around...
Access Control
Only assigned team roles can view sensitive account records. KYC files, withdrawal checks and support transcripts are separated so routine service work does not expose more data than needed.
KYC Handling
Identity documents are used to confirm account ownership and withdrawal eligibility. We do not ask you to resend documents in open chat when the secure upload route is available.
Payment References
JazzCash, Easypaisa, SadaPay and Raast records are stored as transaction references, amounts and timing markers. We use them to reconcile balances and investigate account queries.
Session Records
Login time, device type, IP region and failed access attempts help us protect your account. These records also help support confirm whether an access issue is technical or security related.
Retention Periods
We keep account records for operational, dispute and legal needs, then remove or archive them when those needs end. Some payment and KYC records may require longer retention.
Policy Updates
When this Privacy Policy changes, we update the page date and may place a message inside your account area. Continued account use means the revised policy applies.
PAGE ALIGNMENT
How This Policy Stays Consistent
Your privacy experience should read the same across tu 46 pages, whether you are checking account rules, wallet steps or help content. This section explains how the Privacy Policy connects with related...
Cookie Page
Cookie details focus on browser storage, device signals and preference controls. This Privacy Policy explains how those signals connect with account security, analytics and session protection.
KYC Steps
Verification screens ask for documents only when needed for account checks. The Privacy Policy explains why those files are requested, who can view them, and how retention is handled.
Wallet Records
Wallet pages show balance movement and transaction status. This policy covers the personal data behind those entries, including wallet names, transfer references and reconciliation records.
Support Scripts
Support replies should follow this Privacy Policy when asking for account data. We avoid requesting sensitive documents in public channels when a safer account route is available.
Security Alerts
Login warnings and password reset messages use contact details linked to your account. This policy explains why those details are processed for fraud prevention and account recovery.
Regional Access
Access may depend on supported regions and where local law permits. Privacy handling still applies to records we hold, even if account access later changes.
POLICY LAYOUT
Privacy Layout You Can Read
We structure this Privacy Policy so you can find the part that matters before sharing data. The page separates account data, KYC checks, security logs, payment references, support...
Clear Data Sections
Each privacy section focuses on one record type, such as...
Readable Request Routes
Contact paths are placed near the policy content so you...
Local Context
Pakistan wallet references appear where they matter for privacy, especially...
Security Signals
The layout explains why device, IP region and login records...
Retention Wording
Record retention is described in plain language rather than vague...
Update Markers
Policy changes are handled through page updates and account messages...
Privacy Policy Questions We Receive
We collect account details, contact records, login signals, device data, KYC files, wallet references and activity logs connected to your account. The exact data depends on how you access and use tu 46.
KYC documents help confirm account ownership, reduce misuse and support withdrawal checks. We use secure upload routes where possible and restrict internal access to people who need the documents for verification.
We store transaction references, timing, amounts and account matching details needed to reconcile your balance. We do not treat wallet records as public data or share them for unrelated use.
Yes. Contact us from your account area and explain which detail needs correction. We may request extra confirmation before changing sensitive data such as identity, wallet or contact records.
We may share limited data with partners that help with verification, payments, security, hosting or support. They receive only the data needed for their role and must handle it under agreed controls.
Retention depends on the record type and the reason it was collected. Account, KYC, wallet and support records may be kept for operational, dispute, security or legal requirements.