Privacy Policy for Your 663bat Account
663bat treats privacy as part of your account setup: we explain what data we collect, why it is needed, and how it is protected before you open your...
How Our Privacy Policy Applies
At 663bat, our Privacy Policy applies to account creation, login, identity checks, game-session records, wallet activity, device security signals, and support conversations connected with your account. We process this data to run the service, meet verification duties, protect accounts from unauthorised access, and answer your privacy requests. Access is offered in supported regions and where local law permits; if a location rule
changes, privacy handling for existing records still follows this policy and any legal duty that applies. Payment references such as JazzCash, Easypaisa, SadaPay and Raast help us reconcile wallet records, but we do not ask you to share full app passwords or PINs with us. We limit access inside our team by role, keep audit records for sensitive actions, and remove or
anonymise data when retention is no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Routes at 663bat
Privacy questions need a clear route, not a generic inbox. Use the path that matches your request, include your account ID only when asked, and avoid sending screenshots that reveal full wallet credentials or private banking codes.
Logged-in chat
Use live chat after login for quick privacy questions about your account record. Our team can verify you inside the session and explain what data is visible without exposing private wallet credentials.
Email requests
For access or correction requests, email [email protected] from the address on your account. We may ask for verification details, then route the request to the staff trained for privacy handling.
Wallet reference help
If your concern involves JazzCash, Easypaisa, SadaPay or Raast references, share only the transaction ID and date. We use those fields to locate records without collecting app PINs.
How We Keep Wording Accurate
We write this Privacy Policy from our operating workflow, so the wording follows the way account checks, wallet matching, session logs, and support records are handled. Each signal below shows how we...
Named data categories
Each policy section uses plain labels for account, device, payment, support and security data. You can see why each category is collected and which account activity connects to it.
Role based access
Internal access to privacy records is limited by job need. Support staff see request history, payment staff see reconciliation fields, and security staff see login risk signals.
Update checks
We check the policy when account flows, verification steps, or Pakistan payment rails change inside 663bat. New wording is added only when the actual data handling has changed.
Retention wording
We state that records are kept only for service, legal, security, or dispute needs. When a purpose ends, we securely delete, aggregate, or anonymise the related data.
Security records
Login attempts, device fingerprints, IP signals, and session alerts are used to protect your account. The policy explains this without turning security tools into unclear legal wording for you.
Local payment context
References to JazzCash, Easypaisa, SadaPay and Raast are included because they affect wallet matching. The policy separates transaction references from private app credentials we never need from you.
Privacy Consistency Across Legal Pages
Our legal pages use the same privacy definitions so you do not get mixed messages. This section explains how the Privacy Policy stays aligned with nearby pages while...
| Terms page alignment | The Terms page may mention account verification, but this Privacy Policy explains the data behind that step. We keep the wording consistent so your account duties and data rights are not separated. |
|---|---|
| Cookie page link | Our cookie page covers browser storage and tracking choices, while this Privacy Policy explains how those signals connect to login security, device recognition, and account analytics for your session. |
| Account security page | Security pages describe password care and login alerts. This Privacy Policy adds the data angle, including IP signals, device IDs, failed login records, and action logs kept for investigation. |
| Payments page boundary | Payment pages may show JazzCash, Easypaisa, SadaPay and Raast steps. The Privacy Policy explains which transaction references we keep and why wallet credentials stay outside our records by design. |
| Support page match | Support pages explain response routes, while this policy covers the messages, attachments, and verification details you may share during a privacy request or account query with us. |
| Promo page limits | Any promo page may refer to eligibility checks, but privacy wording remains here. We explain the account signals used for eligibility without expanding them into unrelated profiling or scoring. |
| Change record link | When a sibling page changes a process that touches data, we adjust this Privacy Policy as needed. That keeps your rights, account duties, and retention wording aligned across pages. |
Privacy Page Layout Cues
We designed this legal page so you can scan privacy points before opening an account. The visible cues below show where data scope, account controls, retention, and contact...