LEGAL REFERENCE

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...

Pakistan privacy wordingJazzCash recordsEasypaisa checksSadaPay and RaastAccount data rights
re9 Privacy Policy for your re9 account

How our Privacy Policy applies

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT ROUTES

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.

Team online

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.

POLICY CRAFT

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...

Account terms link
Where account terms discuss verification, this policy explains the data side: what details we collect, why checks are needed and how ownership is confirmed before personal records are shared.
Cookie wording
Cookie language connects to this policy through device, session and preference records. We keep those references consistent so you can see how browser data supports account access and safety.
Wallet records
Payment-related wording across re9 points back to this privacy page for handling of JazzCash, Easypaisa, SadaPay and Raast references, including matching, verification and dispute support.
Security pages
When security text mentions unusual login checks, this policy explains the privacy basis. We connect device signals, IP records and access alerts to account protection rather than unrelated profiling.
Support scripts
Our support replies use the same privacy terms as this page. That helps you recognise when a request needs identity confirmation, account matching or a private case number.
Promo board data
If the promo board uses account preferences or eligibility fields, this policy explains that data use. We do not present promotional checks as separate from privacy duties.
Change history
When privacy wording changes, we keep the new text aligned with related legal pages. The goal is one clear meaning across account, cookie, security and wallet language.

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.

Privacy Policy questions for Pakistan

We collect details needed for your account, such as name, mobile number, login records, device signals, wallet references and support messages. Extra documents may be requested when verification or withdrawal checks require them.

Your mobile number helps us confirm account access, send security messages and match wallet activity. It also supports privacy requests, because we must confirm ownership before discussing personal account records.

JazzCash and Easypaisa references are used to match transactions, verify account ownership and resolve disputes. We store only relevant wallet records with your account and restrict access to staff handling finance or security tasks.

Yes. Send a privacy request with the field you want corrected and evidence that supports the change. We may verify your identity first, then update eligible records or explain any retention duty.

We share limited data with partners that help run hosting, verification, payments, fraud prevention and support. Each partner receives only the fields needed for that service and must handle them securely.

Retention depends on the record type and the reason it was collected. Account, wallet and security records may be kept for service needs, disputes and legal duties, then removed or separated.