Account terms
Our account terms describe access rules, while this Privacy Policy explains the data behind those rules. Both pages use the same account identifiers so your rights stay consistent.
LEGAL REFERENCE
Privacy Policy for Your 66pk Account
66pk keeps your account privacy, device signals and Pakistan payout records explained before you open an account. Read this policy to see what we collect, why we need...
Account data usePakistan privacy contextSecurity checksContact routes
How We Handle Your Data
This Privacy Policy explains how we collect and use data when you access 66pk where local law permits. We collect account details you provide, login records, device signals, transaction references and support messages. We use that data to run your account, verify access, process withdrawals, detect misuse, answer privacy requests and meet lawful record duties in supported regions. Pakistani payment rails may
send reference numbers or status messages linked to JazzCash, Easypaisa, SadaPay or Raast activity; we keep those records separate from game outcomes. We do not sell your personal data. When a service partner helps with hosting, identity checks, analytics or support tools, we require limited access tied to the purpose of that task.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Contact Us About Privacy
Privacy questions need a clear route, not a maze. Use the channel that matches your request and include the account email or mobile number you used with 66pk. We may ask for extra checks before sharing or changing personal data.
Team online
Live chat queue
Ask for the privacy desk inside chat when you need help with account data, device records or transaction references. We will verify your account first, then route the request to the correct team.
Email request
Send privacy requests by email when you need a written trail for correction, access or deletion queries. Include only the details needed to identify your account and the data issue.
Account panel
Use your account panel to update editable profile fields before contacting us. Some records, such as verified payment references or security logs, need manual checks before they can change.
POLICY CHECKS
How We Keep Policy Text Accurate
We write this policy from the way 66pk actually handles account records. Our team checks wording against support flows, payment references, login controls and partner access. When a...
Named data fields
We avoid vague labels where possible and name the data types we handle, including mobile numbers, account email, session logs...
Local rails
JazzCash, Easypaisa, SadaPay and Raast records are described as payment references, not full banking files. We keep only what we...
Session security
Login times, device type and network signals help us protect account access and spot unusual activity. These records are kept...
Policy dates
When we change this Privacy Policy, we update the page date and adjust affected wording. Older requests are handled under...
Plain language
We explain privacy duties in clear Pakistani English, with short sections and named contact paths. You should not need legal...
Access checks
Before sharing account data, we confirm the request comes from you. This protects your profile, payout history, security logs and...
PAGE ALIGNMENT
Consistent Privacy Wording Across Pages
Privacy wording should match wherever you read it on 66pk. We align this policy with account terms, cookie wording, verification screens and support scripts. That keeps data use clear when you move...
Cookie wording
Cookie messages connect to this policy because device signals are part of privacy handling. We separate necessary security cookies from analytics tools so the purpose is clearer.
Verification screens
If we ask for identity checks, the screen wording matches this policy. It tells you why the file is needed, who can see it and how long records may remain.
Withdrawal checks
Payout checks use transaction references and account status data. This policy explains that privacy handling without turning payment records into broader profile data for unrelated use.
Message settings
Account messages and service alerts are covered here because they can include personal data. You can ask us how contact details are stored and used for account notices.
Device entries
Device entries shown in security screens are tied to this policy. They help you understand which sessions we log and why those logs matter for account privacy.
Closure request
If you ask to close your account, privacy handling continues for required records. We explain what may be retained for security, transaction matching and lawful record duties.
VISIBLE MARKERS
Privacy Page Signals You Can See
This page is built so privacy details are easy to scan before you join. Look for dated policy text, named contact paths, local payment references and short explanations...
Clear page date
A visible policy date helps you know which version you...
Short data labels
We use labels such as account data, device signals and...
Pakistan context
Local references are included where they affect privacy handling, especially...
Contact prompts
Privacy contact routes appear near the policy text because questions...
Partner wording
When outside tools help us run hosting, analytics or support...
Security cues
Lock icons, access wording and account-check language mark the parts...
Privacy Questions Before You Join
We collect the details you give us, such as mobile number, email, account profile fields and support messages. We also log device signals, session records and payment references needed to run your account.
Device and session records help us protect account access, investigate unusual logins and keep service records accurate. They may include device type, browser data, access time and network signals linked to your account.
JazzCash and Easypaisa activity is stored as transaction references, status data and matching records. We use it to connect payments to your account and handle support queries, not to build unrelated profiles.
Yes. Contact us with the field that needs correction and enough account details to verify you. Some records, such as completed transaction logs, may need to remain unchanged for matching and security reasons.
We may share limited data with partners that help with hosting, account checks, analytics, support tools or payment processing. Access is limited to the task, and partners should handle records under agreed controls.
Retention depends on the record type. Profile fields may remain while your account is active, while transaction references, security logs and support messages may be kept longer for dispute handling and lawful duties.