Cookie page
The cookie page explains browser storage, device signals and preference tools. This Privacy Policy connects those signals to account security, session continuity and how we recognise your device during access checks.
LEGAL REFERENCE
How 9xbuddy protects your privacy
9xbuddy keeps your privacy choices, account records and Pakistan payment references in one clear policy, so you know what we collect before you open your account. Read this...
Pakistan privacy termsJazzCash record handlingEasypaisa privacy contextSadaPay account checksRaast transfer records
Pakistan privacy posture and scope
This Privacy Policy explains how 9xbuddy handles your personal data when you access our casino and sportsbook pages in supported regions, where local law permits. We collect only the records needed to create your account, secure access, process Pakistan payment references and answer support requests. Payment names such as JazzCash, Easypaisa, SadaPay and Raast are used here as context for the records
we may receive or verify. We do not sell your personal data, and we limit internal access to teams that need it for account, security or service handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CHECKS
Signals behind our privacy handling
We write this policy from the operator side of 9xbuddy, with plain wording around what happens inside your account flow. Our privacy handling is tied to real controls: limited staff access, payment...
Named owner
Our privacy desk owns this page and handles data requests sent through support. That keeps privacy questions separate from general lobby help and gives your request a clear internal path.
Local mapping
We map Pakistan payment references separately from profile fields. JazzCash, Easypaisa, SadaPay and Raast records are treated as transaction context, not as extra marketing labels attached to your account.
Access control
Only staff roles that need a record for account security, support or payment handling can see it. We avoid broad internal access and keep permissions aligned with the task being completed.
Retention calendar
We keep records only for as long as account service, dispute handling, security checks or legal duties require. When a record no longer has a valid purpose, we remove or anonymise it.
Change tracking
When this policy changes, we update the page date and keep the new wording available here. Material changes are written in plain English so you can understand what shifted.
Security logging
Account access events, device signals and support actions may be logged to protect your account. These records help us spot unusual access and confirm whether a request really came from you.
PAGE ALIGNMENT
Policy pages stay aligned
Our Privacy Policy sits beside our cookie, terms and account safety pages. Each page has a separate job, but the privacy wording stays consistent across them so you are not left comparing...
Terms page
The terms page sets account rules, while this page explains the personal data used to apply those rules. We keep the wording aligned so account action and data handling do not conflict.
Promotions page
If you check a promotion, we may process account status, region and eligibility records. This policy explains that data use without turning promotional content into a separate privacy promise.
Support page
Support forms collect your contact details, case text and attachments you choose to send. This Privacy Policy explains how those support records are routed, stored and connected to your account.
Security page
Security content explains access protection, while this policy explains the data behind it. Device signals, login records and verification steps are handled as privacy-relevant account safety records.
Payment pages
Payment pages mention JazzCash, Easypaisa, SadaPay and Raast for account funding context. This policy explains the privacy side: reference numbers, verification checks and retention of transaction records.
FAQ page
Short answers elsewhere should match this policy on collection, retention and access rights. If wording differs, we treat this Privacy Policy as the fuller statement for data handling.
Visible privacy cues on this page
We built the policy page so you can scan privacy duties without hunting through dense legal text. The layout separates collection, use, storage, sharing and contact...
Hero badges
The badges under the heading call out privacy areas you may care about first: Pakistan scope, payment records, account checks and support contact routes. They are labels, not shortcuts around the policy.
Scope chips
The chips in the legal section name JazzCash, Easypaisa, SadaPay and Raast as context for privacy records. They help you see which local references may appear in account handling.
Contact cards
Support cards separate email, chat and account-centre requests. This keeps privacy contact options visible and reduces the chance that you send sensitive data through the wrong channel.
Control icons
Icons for locks, calendars and shields mark security, retention and access sections. They make the policy easier to scan while the full text still carries the privacy meaning.
Update placement
Policy change wording is kept near the trust signals so you can see how updates are handled. We avoid burying change details where you would only find them by accident.
FAQ accordions
The question section repeats common privacy concerns in direct language. Each answer points back to the same data handling principles used across the full policy page.
Questions about your privacy
We collect account details such as your name, contact fields, login records, device signals and support messages. We may also keep payment references when needed to verify JazzCash, Easypaisa, SadaPay or Raast activity.
We use your data to create and protect your account, process service requests, verify payment references, maintain security logs and respond to privacy questions. We do not use more data than the task requires.
Payment references are kept as account transaction records. JazzCash, Easypaisa, SadaPay and Raast details may be checked for matching, dispute handling and security, but they are not sold or shared for unrelated marketing.
Yes. Contact our privacy desk with the account email or phone number you used. We verify identity first, then help with access, correction or deletion where the request fits our duties.
Retention depends on the record type. Account, payment and support records are kept while needed for service, security, disputes or legal duties, then removed or anonymised when no valid purpose remains.
We may share limited data with service providers that help with hosting, security, support or payment verification. They receive only what they need for that task and must handle it under privacy controls.