LEGAL REFERENCE

Privacy Policy for Your o99 Account

o99 keeps account, device, payment and support data under one Privacy Policy, so you know what we collect before you open your account. Read how we handle your...

Account dataDevice checksPayment recordsSupport requests
o99 Privacy Policy for Your o99 Account

How We Treat Your Personal Data

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

CONTACT ROUTES

Privacy Questions and Request Channels

If you want to ask about this Privacy Policy, correct account details or raise a data concern, contact us through the route...

Privacy email Write to our privacy contact with your account...
Live chat handoff Start in chat when you are logged in...
Account centre Use your account area to update basic details...
POLICY CHECKS

How We Keep This Policy Current

We maintain this Privacy Policy as an operating document, not a decorative page. The wording is checked against account flows, support scripts, payment reconciliation and security controls, so the page reflects how...

Operational checks

We compare policy wording with real account steps, including login, wallet activity, withdrawal checks and support tickets, so the text stays close to the way data is handled.

Payment mapping

We map JazzCash, Easypaisa, SadaPay and Raast records to the data categories in this policy, including trace IDs, time stamps, status flags and reconciliation fields.

Access control

Staff access to personal data is limited by role. Support can see what is needed for your request, while sensitive verification material is kept in restricted tools.

Change tracking

When we alter privacy wording, we keep an internal record of what changed, why it changed and which account process or supplier update made the change necessary.

Security testing

Login protection, session behaviour and device signals are checked against this policy, so we explain why certain data points are collected for account safety.

Supplier checks

Where vendors help with hosting, verification, analytics or support, we assess whether they need the data shared with them and restrict use to the agreed purpose.

Privacy Across Our Legal Pages

Our Privacy Policy connects with other legal pages, but it has its own job. Terms explain account rules, cookie wording explains browser storage, and this page explains personal...

Terms alignment
Terms may explain account duties, while this policy explains the data behind those duties, such as identity checks, login records, wallet history and support interactions.
Cookie wording
Cookie text deals with browser storage and tracking choices. This policy connects that storage to account security, session recognition and measurement where you allow it.
Payment records
Wallet rules describe how transactions move. This policy explains the personal data attached to those transactions, including names, phone references, trace IDs and status records.
Security pages
Security wording may describe account protection. This policy explains why we collect device, login, IP and verification signals when protecting your account from misuse.
Support wording
Support pages explain how to reach us. This policy explains what support messages, attachments and chat records we keep when solving a privacy or account issue.
Promo rules
Promotional terms may describe eligibility. This policy explains how account data is checked for eligibility, misuse prevention and records tied to offers you choose to view.
Update consistency
When one legal page changes, we check connected pages for mismatched data language, so your account rights and our data practices remain consistent across o99.

Privacy Page Signals You Can See

The layout of this page is built to make privacy choices easier to scan. We place core data categories, request routes and account-security explanations near the...

Clear data groups

We group account, device, transaction, verification and support data separately, so you can see which part of your o99 activity creates each privacy record.

Local context chips

Short chips mention Pakistan rails such as JazzCash, Easypaisa, SadaPay and Raast only as privacy context, showing where transaction references may enter records.

Plain request routes

Contact routes appear with the type of privacy request they handle, helping you choose email, chat handoff or account-centre edits with less confusion.

Purpose labels

Each data use is tied to a purpose, such as login protection, wallet reconciliation, withdrawal verification, support handling or legal record keeping in supported regions.

Retention cues

Where we keep data for account safety, disputes or legal records, the policy explains the reason instead of hiding retention behind vague internal wording.

Update markers

When this policy changes, the page structure helps us place material updates near the relevant subject, so you can find the changed privacy area quickly.

Privacy Policy Questions Answered

We collect account details, login records, device signals, payment references, verification material and support messages. The exact data depends on what you do in your account and which privacy request you make.

These rails can create transaction references tied to your account. We use those records for reconciliation, withdrawal checks, dispute handling and security controls, not for selling your personal data.

Yes, you can contact us to correct eligible account details. For sensitive changes, such as phone, wallet or identity data, we may verify ownership before making the update.

We use login history, device signals and session records to detect unusual access and protect your account. Access to these records is limited to teams that need them.

We share data only where needed for hosting, payments, verification, support, analytics or security. Each sharing path is tied to account operation, legal records or protection of your account.

Use the privacy email, logged-in chat handoff or account-centre route. Include enough account detail for identification, but avoid sending extra documents unless our team asks.