Terms link
Our Terms describe service access, while this policy explains the personal data behind that access. We check both pages so account rules do not conflict with privacy promises.
LEGAL REFERENCE
Privacy Policy for Your 663 bat Account
Our Privacy Policy explains how 663 bat collects, uses, stores and shares the data tied to your account, device and activity in supported regions of Pakistan. Read it...
Account dataDevice checksWallet referencesSupport requests
How We Handle Your Data
We collect only the data needed to create your account, verify access, protect sessions and process requests connected with our lobby where local law permits. This includes identity details you submit, contact details, device signals, login timestamps, wallet references and activity records linked with casino, live table or sportsbook use. Payment references from JazzCash, Easypaisa, SadaPay and Raast are handled as transaction
records, not as public profile content. We keep records for security, dispute handling, legal requests and account service, then restrict or remove them when retention is no longer needed. When service partners help with hosting, streaming, risk checks or payment routing, we require them to handle your data only for the task we assign. You may contact us to ask about access,
correction or deletion paths.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How We Keep This Policy Checked
We write this Privacy Policy from the way our service is operated, not from generic wording. Each check looks at account creation, session security, Pakistan wallet references, live...
Named owner
663 bat owns the wording on this page and keeps it tied to our account flow. We avoid third-party claims...
Local payment context
Our privacy checks include JazzCash, Easypaisa, SadaPay and Raast references because Pakistan wallet records can contain sender names, numbers and...
Device security
We log device, browser and IP signals to protect access and spot unusual sessions. The policy explains this plainly so...
Limited partner use
Hosting, streaming, risk checks and payment routing may involve service partners. Our policy limits partner access to assigned tasks, with...
Change tracking
When we change account screens, wallet fields or support scripts, we check whether the Privacy Policy still matches. Major wording...
Access rights
The policy explains how you can ask to access, correct or delete eligible records. We also explain why some records...
PAGE ALIGNMENT
Aligned Privacy Across Our Legal Pages
Our legal pages must speak with one voice. This Privacy Policy connects with terms, cookie wording, account rules and promotional terms so you can see how privacy choices, service access and record...
Cookie wording
Cookie wording covers browser storage and similar tools. This policy connects those tools to privacy choices, session security and measurement records, without repeating the same content again there.
Offer terms
Offer terms may ask for account eligibility checks. This policy explains the data side of those checks, including identity, region and account status, rather than reward wording.
Payment wording
Payment pages explain cashier steps, while this policy explains how transaction references are stored and protected. JazzCash, Easypaisa, SadaPay and Raast are treated as records tied to your account.
Security page
Security wording explains access protection; this policy shows the data involved, such as login times, device signals and verification outcomes. The two pages should support the same privacy posture.
Contact wording
Support pages tell you where to ask for help. This policy tells you which route to use when the subject is personal data, correction or deletion requests account.
Eligibility wording
Eligibility wording explains who may use the service where local law permits. This policy explains the checks and records used to confirm that access without publishing private details.
Policy Layout You Can Read Quickly
We design this page for quick reading on mobile screens common in Pakistan. The privacy layout uses plain headings, short sections and visible contact routes, so...
Plain headings
Each heading names the privacy subject directly, such as data collection, sharing or retention. You can scan the page quickly, then slow down on the section that affects your account.
Short badges
The hero badges summarise key privacy areas without replacing the policy. They point you toward account data, wallet references and support access before you read the longer sections.
Local examples
Pakistan examples appear only where they help explain privacy handling. JazzCash, Easypaisa, SadaPay and Raast are used as context for transaction records, not as separate sales copy.
Clear rights
Rights wording is kept close to contact routes, so you can see how to ask for access, correction or deletion. We also state when retention duties may limit removal.
Mobile spacing
Paragraphs are kept short for small screens, with cards that separate contact, checks and common questions. The layout helps you read privacy terms without losing your place.
No hidden claims
We avoid licence, award or traffic claims that are not part of the privacy subject. The page stays focused on data handling, choices and support routes.
Privacy Questions Before You Join
We collect account details you provide, login and device signals, activity records and payment references linked to supported Pakistan options. We use them for account service, security, transaction handling and privacy request management.
No. Your JazzCash, Easypaisa, SadaPay or Raast reference is treated as a transaction record tied to your account. We do not turn wallet details into public profile content.
We use identity or account checks before discussing private records. That protects your data from being released to another person who only knows your username or contact detail.
We keep records while they are needed for account service, security, dispute handling and legal duties. When a record is no longer needed, we restrict, delete or anonymise it where practical.
Yes, you can ask us to correct eligible account details. We may request proof when the change affects identity, contact access or wallet records connected with your account.
Some service partners handle hosting, streaming, risk checks or payment routing. They receive only the data needed for assigned tasks and must not use it for unrelated purposes.
Use the privacy email or ask live chat to create a privacy ticket. For detailed requests, we may move the conversation to email so identity checks are handled safely.