How y400 handles your privacy
Live Baccarat, Andar Bahar, Aviator and sportsbook markets sit behind one y400 account, and this Privacy Policy explains the account, device and payment data we collect when you...
Our privacy posture for Pakistan
This Privacy Policy explains how y400 collects, uses, stores and shares personal data connected with your account, lobby access, support conversations and payment activity in supported regions. We collect only the data needed to run your account flow, confirm transactions, protect access, answer support requests and meet lawful duties where local law permits. Pakistan payment context matters because JazzCash, Easypaisa, SadaPay and
Raast records may create references, timestamps and confirmation messages that help us match your payment to your y400 balance. We do not sell your personal data. We may share limited records with payment partners, security providers, verification services or public authorities when the request is valid and connected with account safety, payment handling or legal duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep policy checks credible
We write this Privacy Policy from the operator side, based on the data flows we use for account access, live tables, slots, sportsbook markets and Pakistan payment matching...
Account flow mapping
We map each account step, from opening your profile to wallet confirmation, so the policy reflects where data is collected...
Payment record checks
Our team compares policy wording with JazzCash, Easypaisa, SadaPay and Raast handling, including references, timestamps and status messages used to...
Device data control
We describe device signals only where they support account protection, session management or abuse checks. We avoid vague labels and...
Support transcript care
Support messages may contain private details, so we keep access limited to staff handling your request. Privacy requests are separated...
Withdrawal verification
When you request a withdrawal, we may compare account identity, payment ownership and transaction history. The policy explains that verification...
Policy date control
We keep a visible policy date and adjust wording when collection, storage or sharing changes. Material updates are written in...
Consistent wording across policy pages
Your privacy experience should not change because you move from this page to account terms, cookie settings or support pages. We keep related policy wording aligned, while this...
Visible privacy markers on this page
We design the Privacy Policy so you can find the data points that matter before you create or use a y400 account. The layout separates account...
Plain language headings
Section names use direct wording so you can scan for account data, payment records or support messages without needing legal training or a separate glossary.
Local payment labels
We name JazzCash, Easypaisa, SadaPay and Raast where they affect privacy records, because Pakistan payment references create different data points from generic wallet labels.
Account-first contact route
Privacy contact paths point back to your y400 account where possible. That reduces the chance of exposing data to someone who cannot prove account control.
Data purpose wording
Each category is tied to a clear purpose, such as account access, transaction matching, security checks or support response, rather than a broad collection statement.
Update visibility
When policy wording changes, we keep the page structure stable so returning account holders can find changed privacy sections without re-learning the whole layout.
Rights request cues
We place correction, access and deletion request cues near the contact section, so you can ask about your data without searching through unrelated service text.