How r2bp Handles Your Privacy
r2bp collects only the account, security, gameplay, and transaction details needed to run your casino access where local law permits. Read this Privacy Policy before you open your...
Privacy Posture for Pakistan Accounts
Our Privacy Policy explains what we collect when you open an r2bp account, verify access, enter the lobby, use live casino tables, browse slots, or place sportsbook entries in supported regions. We handle identity details, device signals, session records, game activity, payment references, support messages, and security logs for account operation, fraud checks, payout handling, and legal record keeping. We do not
sell your personal data. Some data is shared with payment processors, verification partners, game providers, analytics tools, and support systems when that sharing is needed for the service you request. We keep access limited inside our team, record changes to key privacy text, and use Pakistan payment names only as transaction context.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Policy Careful
Our privacy wording is written around the way r2bp actually runs accounts in Pakistan. We check payment flows, account access, device security, live casino sessions, and support handling...
Operational wording
Policy language is tied to real account actions, including login, verification, casino activity, wallet updates, and support messages. That keeps...
Access control
Internal access to personal data is limited by work role. Support, risk, finance, and technical teams see only the records...
Payment context
JazzCash, Easypaisa, SadaPay, and Raast references are treated as transaction data, not public profile content. We use them to reconcile...
Session security
We log device and session signals to detect unusual access, repeated failed logins, and account changes. These logs help us...
Provider handling
Game studios and live table suppliers may receive technical session data needed to load games and settle rounds. We keep...
Change tracking
When privacy wording changes, we keep an internal record of what changed and why. If a change affects how your...
Privacy Consistency Across Our Pages
This Privacy Policy sits alongside our other legal pages, but it has its own job: explaining personal data. We keep wording aligned so you do not see one...
Privacy Layout You Can Read
We designed this policy page so you can find the privacy point you need without digging through unrelated sales copy. The layout separates collection, use, sharing...
Plain sections
Each privacy section is written around a direct account action, such as creating a profile, verifying payment activity, loading a game, or asking support for help with your data.
Visible categories
Data categories are grouped by purpose, so you can see the difference between identity details, technical logs, casino session records, wallet references, and support messages.
Retention cues
Retention wording explains why some records must stay longer than others, especially where account security, payout disputes, fraud prevention, or legal record keeping applies.
Local context
Pakistan payment rails are named only where they matter to privacy. JazzCash, Easypaisa, SadaPay, and Raast appear as transaction context rather than as unrelated service claims.
Rights path
Requests to access, correct, or question personal data are placed near support contact routes. That helps you move from reading the policy to contacting us when needed.
Update marker
Policy updates are placed where you can spot them before reading deeper. If our data handling changes, the page wording is adjusted to match the current r2bp account flow.