Privacy Policy for your 9yyy account
9yyy keeps your casino, sportsbook and wallet data inside one privacy flow, so you can see how account checks, cookies and payout records are handled before you open...
How our policy treats account data
Our Privacy Policy applies when you access 9yyy.run, open an account, enter the lobby, contact support or use wallet services linked to your account. We collect data that helps us run account access, verify payment activity, protect sessions and respond to privacy requests. This can include contact details, device signals, login records, cookie choices, transaction references and support messages. For Pakistan, payment
records may involve JazzCash, Easypaisa, SadaPay and Raast references, but we only keep what is needed for account handling, security checks, legal requests and dispute resolution. Access is intended for supported regions where local law permits, and we may restrict or refuse activity when verification cannot be completed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ask us about your privacy rights
You can contact us when you want to access, correct or question data linked with your 9yyy account. We route privacy messages away from general lobby requests, so account records, wallet references and cookie concerns can be checked by the right support team. Keep your account email and recent payment reference ready, because that helps us confirm the request belongs to you.
Email privacy desk
Send privacy requests by email when you need a written record of your question. Include your account email, Pakistan region and the data type you want us to check, correct or explain.
Live chat handoff
Use live chat for short privacy questions while signed in. If the matter needs document checks or wallet tracing, our team moves it to email so your request has a clear case trail.
Account centre request
Inside your account area, privacy requests can be linked to your login session. That helps us compare device activity, cookie consent and payment references without asking for details we do not need.
How we keep this policy accurate
We write this Privacy Policy from the way 9yyy is operated, not from a generic legal template. The policy is checked against account creation, login security, live casino access, sportsbook records, cookie...
Policy owners
Our account, support and technical teams feed changes into the Privacy Policy. That keeps the page tied to real workflows, including login recovery, wallet verification and privacy request handling.
Data mapping
We map each data point to a purpose before it appears in this policy. Account details, device records and support messages are listed only when they serve security, access or service handling.
Wallet scope
For JazzCash, Easypaisa, SadaPay and Raast, we record transaction references needed to trace payments and withdrawals. We do not ask for wallet credentials or full banking access.
Security checks
Privacy controls connect with session security, password resets and unusual login checks. These steps help protect your account while keeping data use limited to clear operational needs.
Cookie controls
Cookie choices are documented so you can understand which cookies support login, fraud checks, page performance and preference storage. Non-essential choices can be adjusted where the tool permits.
Regional wording
We use Pakistan-specific examples because wallet rails and support expectations differ by market. Access language also refers to supported regions where local law permits.
Matching privacy rules across 9yyy pages
Your privacy rights should not change just because you move from the lobby to help pages, wallet pages or account settings. We keep related legal pages aligned so...
Privacy cues you can see
We design the Privacy Policy page so you can spot important controls without digging through unrelated copy. The layout points you toward account data, cookie choices...
Clear section anchors
Section anchors help you jump between account data, cookies, security and contact routes. They are written as plain labels so you know which part of the policy answers your question.
Account data panel
The account data area explains contact details, login records and verification files together. Keeping those fields in one place shows how each item connects to account access.
Cookie banner link
A cookie link stays close to the privacy wording so you can revisit browser choices. It separates essential session cookies from optional measurement tools where settings are available.
Rights request card
The request card explains how to ask for access, correction or deletion where available. It also tells you which account details help us verify your request safely.
Security badge row
Security badges summarise encryption, session checks and restricted staff access. They are quick cues, but the policy text gives the fuller explanation behind each control.
Date marker
A visible date marker helps you see when the policy was last changed. If wording changes, we aim to make the affected privacy area clear rather than hiding it.