Terms link
Our Terms explain account rules, while this policy explains personal data handling. When a term needs identity, security or transaction records, this page describes the privacy side of that process.
4rr keeps live casino, slots and sportsbook account data under one Privacy Policy, so you can see what we collect before you open your account. We explain how...
This Privacy Policy describes how 4rr collects, uses, stores and shares personal data when you access our brand home, create an account, complete verification, contact support or use casino and sportsbook areas where local law permits. We collect only the account details, security signals, payment references and service records needed to run your account flow, process requests, reduce misuse and answer privacy
questions. Pakistani payment context may include JazzCash, Easypaisa, SadaPay and Raast transaction references, but we do not need your wallet PIN or banking password. Access can vary by supported regions, and we may ask for identity checks before releasing account-specific data. By continuing with 4rr, you confirm that you have read how this policy applies to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions deserve a clear route, not a generic inbox loop. Use the account email where possible, include the phone number linked to 4rr, and tell us which privacy right or data record you want handled.
Ask us what personal data is linked to your account, including phone, email, login device and transaction references. We route privacy requests to the team that can verify you before sharing any account-specific reply.
If you start in chat, ask for a privacy escalation and keep your account email ready. Chat can record your request, but we may move sensitive replies to email after identity checks.
For JazzCash, Easypaisa, SadaPay or Raast privacy questions, send only the transaction reference and date. Never send wallet PINs, passwords or screenshots showing private balances outside the requested record.
We write this policy from our own account flow, support records and payment handling steps. When a screen, verification request or data retention period changes, our internal team...
Our privacy text is written from the processes we run at 4rr, not copied from a template. It reflects account...
When we adjust a form field, security prompt or support route, we check whether this policy needs an update. That...
Only trained staff can open account records needed for privacy support, payment trace checks or security investigation. Internal access is...
We retain records for account security, dispute handling, transaction tracing and legal duties where they apply. When a record is...
JazzCash, Easypaisa, SadaPay and Raast references are used to match your request to the right account event. We do not...
We keep the policy in clear Pakistani English, with short explanations for data collection, sharing and your choices. If wording...
Our Privacy Policy connects with other legal pages without repeating every clause. Each page has a separate job, but the privacy promises stay consistent wherever you read about account access, cookies, terms...
Our Terms explain account rules, while this policy explains personal data handling. When a term needs identity, security or transaction records, this page describes the privacy side of that process.
Cookie language covers browser storage, session signals and preference tools. This Privacy Policy explains how those signals may connect with your account, fraud checks and service improvement inside 4rr.
Support pages explain how to reach us; this policy explains how chat text, email threads and verification answers may be stored. We keep them to resolve account and privacy requests accurately.
Cashier screens show transaction status; this policy explains the data trail behind that status. References from JazzCash, Easypaisa, SadaPay and Raast help us match payments to your account.
Security text may mention passwords, device checks and suspicious access. This Privacy Policy explains which signals we collect, why they matter and how they support account protection.
If you interact with a promo board, we may store eligibility, timing and account response data. This policy explains that handling without turning promo rules into privacy language.
Where access depends on supported regions, related pages may explain availability. This policy focuses on how data is handled when you browse, create an account or contact us from Pakistan.
We place privacy cues where decisions happen: account forms, cashier context, login checks and support prompts. These small labels help you understand why data is requested...
Account fields use short labels explaining why we ask for phone, email or identity details. The goal is to make privacy purpose clear at the moment you type, not later.
When a setting needs your choice, we separate that prompt from ordinary account text. You should be able to spot privacy choices quickly and change optional selections where the account flow allows.
Login and device checks may show short privacy notices explaining risk signals. These notices help you understand why a second check appears after unusual access, failed passwords or location changes.
Cashier screens may mention how transaction references are stored for tracing and dispute support. We keep that wording close to JazzCash, Easypaisa, SadaPay and Raast fields for clarity.
Support forms remind you not to share wallet PINs, passwords or full card-style secrets. That protects your privacy while still letting us verify account ownership and transaction history.
We keep the Privacy Policy reachable from account and footer areas so you can read it before sending data. If a screen changes, the linked policy remains the reference point.