Privacy Policy for your r6db account
r6db puts live casino, slot and sportsbook privacy terms in one clear place before you open your account. Read how we collect account data, protect payment records and...
How r6db handles your data
This Privacy Policy explains what r6db collects when you create an account, enter the lobby, contact support or request a withdrawal where local law permits. We use your name, contact details, account identifiers, device signals, session logs and payment references to run access checks, protect your balance record and answer privacy requests. We also process transaction data linked with Pakistan rails such
as JazzCash, Easypaisa, SadaPay and Raast when those rails are shown in your account flow. We do not sell your personal data. We share data only when needed for account verification, fraud prevention, payment processing, legal compliance or service providers working under our instructions. You can contact us to ask about access, correction or deletion, subject to security checks and record keeping
duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep this policy current
We maintain this page as an operator statement, not as outside commentary. When our account flow, verification partners, game access systems or Pakistan payment rails change, we check...
Operator wording
We describe data handling from inside r6db operations, including account checks, support tickets, wallet references and session security. The wording...
Local rail context
Pakistan payment references are named only where they affect privacy handling. JazzCash, Easypaisa, SadaPay and Raast records may be checked...
Security checks
When you request access or correction, we compare account login signals, contact details and recent activity before releasing data. This...
Retention clarity
We keep records only for business, security, payment and legal reasons. Some logs are deleted earlier, while account and withdrawal...
Plain language
We write policy text in clear Pakistani English so you can understand how your data is used. Legal terms appear...
Change tracking
When we adjust this policy, we update the date and the affected wording. Material changes may also appear through account...
Aligned privacy across our pages
Privacy wording has to match the rest of your account experience. We align this policy with our terms, cookie choices, security messages and verification steps so your rights...
Policy layout you can scan
We designed this privacy page so you can find the right clause without reading every paragraph first. The visible layout separates data collection, usage, sharing, retention...
Effective date
The policy date tells you which version applies when you use r6db. If wording changes, the refreshed date helps you separate older handling terms from current account practices.
Data categories
We group data into account details, device signals, payment references, support records and activity logs. That structure helps you see what is collected and why it matters.
Use purposes
Each purpose connects to a real account task, such as login protection, payment matching, withdrawal checks, support handling or legal record keeping. We avoid broad wording where a narrower reason fits.
Sharing section
The sharing clause names the kinds of partners involved, including payment processors, security providers and support tools. It also explains that providers work under instructions tied to r6db services.
Your rights
The rights section explains how you can request access, correction or deletion. We also explain why some records may remain where security, payment disputes or law require retention.
Contact block
The contact block keeps privacy requests away from general chat when deeper handling is needed. It tells you what to include so the team can find your account record.