Privacy Policy for your x66y account
x66y keeps account, device, payment, and support privacy choices in one clear policy so you know what we collect before you open an account. We connect those privacy...
How our Pakistan privacy stance works
This Privacy Policy explains how x66y handles data linked to your account, identity checks, device access, wallet activity, lobby sessions, and support messages. We collect only what we need to run secure account access, process payment records, maintain game session logs, answer your requests, and meet duties that apply in supported regions. When you use JazzCash, Easypaisa, SadaPay, or Raast, we may
receive payment references, timing data, and status messages, not your full banking credentials. We keep records for practical, legal, and security reasons, then remove or mask them when they are no longer required. Access to x66y services remains subject to where local law permits, and this policy explains the privacy side of that access.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact us about privacy choices
Privacy questions need clear routes, not guesswork. Use the contact path that matches your request, include your account email or phone reference, and avoid sending card images unless we ask for a specific verification step. We answer with the action available under this policy.
Account privacy email
Email us from the address on your x66y account so we can match the request without asking for extra proof. We reply with the data category, action taken, and any limit that applies.
Live chat privacy flag
Start chat from inside your account and ask for privacy help. Our team tags the thread, checks access history, and moves complex data requests to the correct privacy queue.
Payment data query
For JazzCash, Easypaisa, SadaPay, or Raast concerns, share the transaction reference and date. We check the status record while keeping wallet credentials outside the conversation.
How we keep policy text accurate
We write this policy from the systems we operate: account login, payment status checks, identity verification, support records, and session security. When a workflow changes, we check whether the privacy wording still...
System-linked wording
Policy terms are matched against account screens, verification prompts, payment status labels, and support forms, so the wording reflects how x66y actually handles your data during normal account use.
Pakistan context
We mention JazzCash, Easypaisa, SadaPay, and Raast only where those rails affect privacy records, such as payment references, confirmation timing, account matching, and dispute checks.
Access control
Internal access to privacy records is limited by role. Support can see what is needed for your request, while sensitive verification files require a narrower permission path.
Change tracking
When we adjust this policy, we keep a record of the changed section, the reason for the edit, and the date the updated wording went live.
Security checks
Login attempts, device signals, and session events are used to protect your account. The policy explains these checks without treating them as marketing copy.
Plain language
We avoid vague legal wording where direct language works. You should be able to see what data we collect, why it is used, and how to contact us.
Consistency across related privacy pages
A privacy policy should not conflict with nearby legal pages. We keep this page aligned with our terms, cookie wording, account security text, and support process pages, while...
Brand cues inside this policy
This page is built to help you scan privacy details quickly before you create or manage an account. We separate data categories, contact routes, record retention...
Short section labels
Each privacy area uses direct labels, such as account data, device signals, support records, and payment references, so you can find the right topic without decoding legal phrasing.
Local context chips
Where payment privacy is relevant, we show Pakistan rail names as context chips. That keeps the policy clear without turning the page into a cashier screen.
Action-ready contacts
Contact details are written around real privacy actions: access, correction, deletion where available, payment record questions, and account matching checks handled by our team.
Plain retention cues
Retention wording explains why some records stay for security, legal, or dispute reasons. We avoid open-ended promises and tell you what drives the timing.
Device clarity
Device and browser references explain login safety, session continuity, and fraud checks. They are included because they affect privacy, not because they promote features.
Readable legal flow
The policy moves from data collected, to reasons for use, to sharing, retention, security, and contact choices, giving your account privacy path a clear order.