Terms page link
Our terms explain account rules, while this policy explains the personal data behind those rules, including identity checks, account status and access records.
LEGAL REFERENCE
How ar99 Handles Your Privacy
Aviator, live baccarat and sportsbook slips create account, session and transaction data, so our Privacy Policy tells you what ar99 collects, why we use it and how you...
Account dataDevice checksPakistan supportPayment context
Our Privacy Policy Position
This Privacy Policy applies when you use ar99 in supported regions, create an account, verify access, contact our team or send a payment request through local rails. We collect only the data needed to run your account, protect access, process withdrawals and meet lawful checks. Your payment brand, reference code and transaction status may be stored with your account record, but we
do not ask you to post wallet PINs or banking passwords inside chat.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
TEXT CHECKS
How We Keep Policy Text Accurate
We maintain this Privacy Policy as an operating document, not a decorative page. Our account, support and risk teams check wording against the way ar99 actually collects data...
Plain language
We write privacy wording in clear Pakistani English, naming the data we collect and the reason for each use so...
Account flow match
Policy wording is checked against the real account flow, including login, verification and withdrawal steps, so the text reflects what...
Payment rail mapping
JazzCash, Easypaisa, SadaPay and Raast references are described as transaction context, not wallet access. We record status details needed for...
Access control
Support staff see only the privacy records needed for their task. Sensitive account actions require ownership checks before private data...
Change record
When privacy wording changes, we keep the new version clear on this page and use date tracking inside our internal...
Regional wording
Pakistan-specific terms are used where helpful, including local payment names and support routing, while access is described only for supported...
PAGE ALIGNMENT
Aligned Privacy Across ar99 Pages
Your privacy rights should not change from page to page. We align this Privacy Policy with our account terms, cookie wording, verification language and support scripts. Each page has a different purpose...
Cookie page link
Cookie wording deals with browser storage and session markers. This policy explains how those markers connect to login security and account protection.
Verification wording
Identity checks may require documents or matching details. This policy explains why that data is requested and who may view it internally.
Support scripts
Our support replies follow this policy when asking ownership questions, discussing payment references or moving private matters away from open chat.
Payment records
Payment help pages may show JazzCash, Easypaisa, SadaPay or Raast steps. This policy explains the transaction data kept with your account.
Security alerts
When access alerts appear, this policy explains the device, location and session details used to decide whether extra account checks are needed.
Withdrawal checks
Withdrawal wording describes processing steps. This policy explains the privacy side, including account matching, reference checks and support access to status records.
LAYOUT MARKERS
Privacy Page Layout Cues
We design this Privacy Policy so the important parts are easy to find before you open an account. The page separates collection, use, sharing, storage and contact routes...
Short policy badges
The hero badges point to account data, device checks and...
Local context chips
JazzCash, Easypaisa, SadaPay and Raast appear as context chips, showing...
Contact cards
Support cards separate chat, email and security escalation, so you...
Policy alignment cards
Comparison cards show how this policy connects with terms, cookies...
FAQ anchors
Privacy questions are grouped at the end for quick reading...
Readable sections
Each section uses a clear heading, short body and focused...
Privacy Policy Questions Answered
We collect account details, login records, device signals, verification data, support messages and transaction references. Each category is used to run your account, protect access and process account requests.
Payment references help match JazzCash, Easypaisa, SadaPay and Raast activity to your account. We use status, time and reference details, not wallet passwords or private app credentials.
Yes. Contact support with the detail that needs correction and evidence where needed. We will confirm account ownership before changing identity, contact or payment-related records.
We keep records for as long as needed for account operation, payment matching, security checks and lawful record duties. When data is no longer needed, we remove or restrict it.
We share data only when needed for account services, payment handling, security checks, technical hosting or lawful requests. Each sharing purpose is limited to the relevant task.
Use live chat for quick questions or email for formal privacy requests. Include your account name and request type, but never send wallet PINs, passwords or login codes.