Shared definitions
Terms such as account data, payment reference, device signal and session record carry the same meaning across our legal pages, so your rights and our duties are not described in conflicting language.
LEGAL REFERENCE
Privacy Policy for your r6s account
r6s keeps account data, cookie choices, device signals and payment records inside one Privacy Policy, so you can see how your details support access to our casino and...
Account data explainedCookie choices coveredPakistan payment contextSecurity checks named
How we handle your details
This Privacy Policy applies when you create an r6s account, browse the lobby, contact our team or use payment rails available in supported regions of Pakistan. We collect only the data needed to run your account, verify access, protect sessions, process withdrawals, answer messages and meet record duties where local law permits. That may include your name, contact details, age confirmation, device
data, login history, transaction references and cookie choices. We do not sell your personal data. When we share limited records with payment, fraud screening or technical partners, we restrict the purpose, keep audit trails and require secure handling. You can ask us to access, correct or erase eligible records, subject to legal retention rules.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CARE
Signals behind this policy
We write this Privacy Policy from the operator side of r6s, not as a detached summary. The wording follows how our account checks, payment references, cookie tools and support queues actually work...
Account verification
We compare registration details with account activity before major changes, withdrawals or privacy actions. That helps us confirm the request came from you and not from a copied email or shared device.
Payment records
JazzCash, Easypaisa, SadaPay and Raast references are kept with time, amount and account markers. We use them to reconcile requests, resolve disputes and meet record duties where required.
Cookie controls
Cookies support login continuity, fraud checks and language preferences. Where choice is available, we separate essential cookies from analytics so your privacy setting can be applied without blocking core account access.
Limited access
Only trained staff with a work need can reach personal records. Access is logged, roles are separated and sensitive cases move through escalation instead of open team channels.
Retention checks
We keep records while your account is active and for legal, dispute or security periods after that. When retention no longer applies, we delete or de-identify eligible data.
Clear updates
When this Privacy Policy changes in a meaningful way, we update the date and may place a notice near account access. You can read the changed sections before continuing.
POLICY ALIGNMENT
How policy pages stay aligned
Our legal pages speak to different parts of your account, but they use the same naming, dates and contact routes. That consistency helps you understand whether a privacy question, cookie choice or...
Cookie link
The cookie page expands the browser and device parts of this Privacy Policy. It explains which cookies are essential, which support measurement and how available choices are stored.
Terms link
The terms page covers account rules, while this page covers personal data handling. If a suspension, withdrawal or verification step uses records, both pages should be read together.
Date control
Each legal page carries its own update date, but changes are checked against related pages before publishing. That avoids old wording staying live after a privacy process changes.
Contact match
Privacy, cookie and account questions all start from the same support routes, then move to the right team. You do not need to repeat your concern across multiple inboxes.
Payment wording
Payment references are described as records, not as public account details. That same wording appears wherever JazzCash, Easypaisa, SadaPay or Raast records are mentioned in legal text.
Rights wording
Access, correction and erasure requests are framed consistently, with limits for security, disputes and legal retention. We avoid promising action that law or account protection may prevent.
PAGE MARKERS
Visible markers for privacy reading
This page is laid out so you can scan the privacy parts that matter before you open or manage an account. Labels, chips and contact cards keep the...
Hero badges
The badges at the start show the data areas covered...
Local chips
JazzCash, Easypaisa, SadaPay and Raast chips appear as context markers...
Contact cards
The contact cards separate urgent access issues from detailed rights...
Rights language
Rights are written in plain Pakistani English, with limits stated...
Security wording
Security sections name practical checks such as login history, device...
Update cues
Policy change cues are kept close to the sections they...
Privacy questions before you join
We collect account details, contact data, age confirmation, login history, device signals, cookie choices and payment references. Each record supports account access, security checks, service messages or legal retention where local law permits.
Payment references help us match JazzCash, Easypaisa, SadaPay or Raast activity to your account. We use them for reconciliation, withdrawal checks, dispute handling and required records, not for public display.
Yes, you can ask for eligible personal data linked to your account. We may verify your identity first, then provide access subject to security, fraud prevention, dispute and legal retention limits.
Cookies help keep you logged in, remember settings, detect risky sessions and measure page function. Essential cookies support account access, while available preference controls apply to non-essential cookies where the setting is offered.
We keep records while your account is active and for periods needed for law, disputes, fraud checks or payment reconciliation. After those reasons end, eligible records are deleted or de-identified.
Access is limited to staff and service partners who need the record for account, payment, security or support work. We use role controls, logging and purpose limits to reduce unnecessary access.
Contact us through live chat for urgent session issues or email for detailed rights requests. Share your registered contact and request type, but do not send passwords or unnecessary payment screenshots.