668game Privacy Policy
This Privacy Policy explains how 668game collects, uses, stores and protects personal data connected with your account in Pakistan. We keep the wording practical so you can understand...
How We Handle Personal Data
We collect details you provide during account creation, such as your name, contact details, date of birth where required, login credentials and selected region. We also receive transaction references, support messages, device details, IP address, browser data and activity records needed to operate, secure and improve the service. Payment partners may send confirmation data when you use JazzCash, Easypaisa, SadaPay or Raast;
we do not need to store your full wallet credentials to confirm a transaction. We use data to open and maintain your account, process requests, detect suspicious access, meet applicable legal duties and answer support queries. Access may depend on supported regions and local law. We retain records only for operational, security or legal needs, then remove or anonymise them under our
retention procedures. Questions about this policy can be sent through our account support channels.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Us About Your Data
Our support paths are designed to keep privacy requests separate from ordinary account questions. When you contact us, we may ask for enough account detail to confirm your identity before discussing personal data. Please avoid sending wallet PINs, passwords or full payment credentials in a message.
Account chat
Use the signed-in support chat for access, correction or deletion requests. We can link your message to the correct account while limiting unnecessary personal details in the conversation.
Email request
Send a privacy question through our listed contact email with your account reference and the action you seek. We may reply with verification steps before releasing account-specific details.
Security alert
Tell us promptly if your login, device or contact details appear compromised. We can record the incident, restrict unusual access and explain the next account-security steps.
Privacy Signals We Maintain
We apply practical controls around account data rather than treating privacy as a single notice on a page. Our processes distinguish identity details, payment references, device signals and support content, allowing access...
Purpose-based access
Account data is made available according to work need, such as verification, payment matching, fraud detection or support. This helps reduce broad internal access to personal records.
Payment references
For JazzCash, Easypaisa, SadaPay and Raast activity, we generally handle confirmation references and status details rather than wallet passwords or secret access codes.
Device awareness
Login time, browser type, IP address and device signals can help us identify unusual access. These records support account protection and may be retained for security needs.
Correction route
If your contact or identity details change, you can ask support to correct the relevant record after verification. We aim to keep account data accurate for service and security.
Retention control
We keep personal data for the period needed for account operation, dispute handling, security checks or legal duties. Records may then be deleted or changed into non-identifying data.
Plain-language notice
This page describes our privacy approach in direct language, including collection, use, sharing, storage and requests. If a situation is not clear, our support team can clarify it.
How This Policy Fits Together
Our privacy wording is intended to align with the account, payment and security notices shown across 668game. Each page has a different purpose, but the same core approach...
What This Privacy Page Shows
The privacy side of our site is arranged around the questions people usually ask before opening or using an account. You can move from the short...
Collection summary
The opening details identify the main categories we may receive, including account, transaction, device, network and support data, so the scope is easy to scan.
Use purposes
Each stated use connects data to a practical need such as access, security, transaction matching, legal duties or replying to a request.
Sharing context
Partner handling is described by task and data type, helping you understand why a payment, technical or security service may receive limited records.
Storage approach
Retention wording explains that records remain only for operational, security, dispute or legal needs, followed by deletion or anonymisation where appropriate.
Request routes
The page points you towards signed-in chat and email paths for privacy questions, while reminding you not to send passwords or wallet secrets.
Regional wording
References to Pakistan, supported regions and local law clarify that account access and data handling can vary according to applicable requirements.