Privacy Policy for your r9999 account
r9999 keeps casino, slots and sportsbook account data under one Privacy Policy, so you can see how your details are collected, used and protected before you open an...
How this policy applies locally
This Privacy Policy applies when you access r9999 in supported regions, create an account, contact us, verify your profile, or use payment rails connected to Pakistan. We collect only the data needed to run your account, protect access, process withdrawals, answer privacy requests and meet legal record duties. That can include your name, phone number, device signals, login history, KYC files, wallet
references and support messages. Where local law permits, we may share limited records with payment partners, identity checks, security vendors and service providers that help us operate the account flow. We do not sell your identity data. Some records must be kept for audit, dispute handling and fraud prevention, then removed or anonymised when retention is no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact paths for privacy requests
If you have a privacy question, start from your r9999 account area so we can confirm the request belongs to you. We keep privacy support separate from general account chat, and we may ask for extra proof before changing, sharing or removing sensitive records.
Account privacy form
Use the form inside your account to request a copy, correction or removal check. We match it with login history before releasing any personal record.
Email privacy desk
Send account privacy concerns to our email desk with your r9999 ID and phone number. We reply after identity checks are complete, not before.
Live chat handoff
Chat can route you to privacy support, but it cannot display sensitive files. The handoff creates a case reference you can follow later.
How we keep policy wording current
We write this Privacy Policy from the systems we operate: account creation, verification, wallet references, security logs and support cases. When those flows change, our internal teams check whether the policy needs...
System mapping
We map each account screen to the data it captures, including phone number, device record and verification file, so the policy mirrors the real r9999 flow.
Access controls
Staff access is limited by role, and sensitive files are not visible in ordinary support screens. Privacy cases require a separate permission path.
Retention checks
Records are tagged by purpose, such as withdrawal audit, dispute handling or security monitoring. Those tags decide how long a file remains active.
Vendor checks
When a service provider handles account data for r9999, we check the purpose, fields shared and deletion process before that connection is approved.
Local wording
We use Pakistani English for this policy because your account flow may include JazzCash, Easypaisa, SadaPay or Raast records in supported regions.
Change log care
Policy edits are tracked internally with date, reason and owner, so support can explain which wording applied when your request was opened.
Consistency across r9999 policy pages
This page sits beside other r9999 legal pages, but it stays focused on privacy. Where another page explains account rules or promotions, this policy explains the data record...
Policy layout you can scan
We designed the Privacy Policy page so you can find data subjects quickly without reading unrelated account copy first. The visible markers point to collection, use...
Plain section labels
Each heading uses direct privacy wording, so you can move from data collection to sharing, retention and requests without searching through unrelated platform copy.
Account flow context
Examples are tied to r9999 actions you recognise, such as login, verification, support chat and withdrawal checks, rather than abstract legal language.
Local record chips
Short chips show where Pakistani wallet references may appear in privacy records, helping you understand why transaction traces can be linked to support cases.
Request route blocks
Contact blocks separate copy requests, correction requests and removal checks, so you can choose the right path before sending personal details.
Retention cues
Retention wording is placed near each record type, making it clearer why some files stay longer for audit, dispute handling or security reasons.
Update markers
When policy wording changes, we keep date and reason markers internally, so support can connect your privacy case with the correct text.