Privacy Policy for your re9 account
re9 keeps casino, sportsbook and wallet privacy terms in one clear policy, including how JazzCash, Easypaisa, SadaPay and Raast records support account checks. Read it before you open...
How our Privacy Policy applies
Our Privacy Policy explains the personal details we collect when you create, secure and use your re9 account in supported regions where local law permits. This can include your name, mobile number, account access logs, device signals, wallet references and messages you send to support. We use these details to verify access, process withdrawal checks, protect your balance, answer privacy requests and
meet records duties that apply to our service. We do not sell your personal data. Limited sharing may happen with payment, verification, hosting, fraud prevention or customer-care partners that help us run the account flow. Each partner is given only the data needed for its task, and we keep internal access restricted to trained staff handling privacy, finance or security work.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ask us about your privacy
When you ask us about privacy, we separate account help from policy requests so your message reaches the right desk. Tell us which data concern you want checked, such as wallet records, login history or identity details. We may ask for verification before discussing personal data, because privacy answers must go only to the account owner.
Privacy email
Send your request through the privacy email listed in your account area. Include your re9 username, registered mobile number and the exact data issue, so our team can route it without exposing extra details.
Live chat handoff
If you start in live chat, ask for privacy support rather than general account help. The agent will confirm ownership and create a private case for data access, correction or deletion handling.
Wallet record query
For JazzCash, Easypaisa, SadaPay or Raast references, send the transaction time and account name. We use those fields to match records while avoiding unnecessary screenshots or unrelated wallet data.
How we keep policy details accurate
We write this policy from the way re9 actually handles account records, wallet checks and support cases. Each privacy change is tied to a real process, not a broad claim. When a...
Process-linked wording
Each section reflects a live re9 process, such as account creation, login checks, wallet reconciliation or support replies. We avoid vague privacy language when a concrete data flow can be described.
Pakistan context
The policy names local payment rails because they create real account records. JazzCash, Easypaisa, SadaPay and Raast references are described as wallet data, not as broad financial profiling.
Access controls
Internal staff access is limited by role, so support, finance and security teams see only the data needed for their task. Privacy requests are handled through logged case channels.
Data retention checks
We keep account and transaction records for periods needed for service, dispute handling and legal duties. When retention no longer applies, records are deleted or separated from direct identity fields.
Security signals
Device, IP and login signals help us detect unusual account access. The policy explains this security use so you understand why technical records appear beside your profile details.
Plain language edits
We rewrite policy language when a sentence becomes too legal-heavy. The aim is simple: you should understand what data we collect, why it matters and how to contact us.
Consistent privacy across our pages
Your privacy reading should not change from one re9 legal page to another. We align this Privacy Policy with account terms, cookie wording and wallet record language. If...
Privacy layout points you can scan
We designed this privacy page so you can find the parts that affect your account quickly. The layout separates data types, usage reasons, sharing partners and...
Data type labels
Profile details, wallet references, login records and support messages are named separately. This helps you see which privacy rule applies to each part of your re9 account journey.
Purpose markers
Each data category is linked to a purpose, such as verification, account security, transaction matching or support. We avoid collecting details without connecting them to a clear service need.
Sharing boundaries
Partner sharing is described by function, not by broad labels. Payment, hosting, verification and fraud prevention partners receive only the fields needed to carry out their assigned task.
Rights pathway
You can ask to access, correct or delete eligible personal data. The policy explains when verification is needed and when retention duties may limit a deletion request.
Security cues
We place security-related data near login and device wording, so it is clear why IP records, session logs and risk signals may be kept with your account.
Update marker
When this policy changes, the page text is updated to reflect the current account flow. You should read the latest wording before sharing new details with re9.