LEGAL REFERENCE

Privacy Policy for your o00o account

o00o keeps casino, sportsbook and payment privacy terms in one clear policy for Pakistan, so you know what data we ask for before you open your account. Read...

Pakistan account dataJazzCash contextEasypaisa contextSadaPay checks
o00o Privacy Policy for your o00o account

How we handle account data

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

CONTACT PATHS

Privacy support when you need us

You can ask us about privacy through the same support routes used for account help, but mark your message as a privacy request. Add your account ID, the email or mobile number linked to your profile, and the concern you want checked. We may ask extra questions before sharing or changing data, because privacy requests must match the real account holder.

Team online

Live chat request

Use live chat when you need a quick privacy status check. We can confirm whether your request is logged, what proof is needed, and which team will handle the next step.

Email privacy desk

Email suits requests that need documents, longer explanations or account history checks. Keep attachments clear, avoid sending card secrets, and use the email address already linked to your o00o profile.

Account page message

Your account page lets you raise a privacy message after login. This helps us connect the request with your profile while reducing the amount of personal data repeated in chat.

POLICY CARE

How we keep policy text current

Our privacy text is maintained by the team that handles account access, payment records and support workflows for o00o. We update wording when a data route changes, when a service partner is...

Account data mapping

We map sign-in, profile and device records against the account features that use them. This keeps the Privacy Policy tied to real screens rather than vague wording about data handling.

Payment record checks

JazzCash, Easypaisa, SadaPay and Raast references are treated as payment records, not public profile content. We keep them for matching, support, reconciliation and legal record needs.

Access controls

Only trained staff with a work need can open sensitive account records. Internal tools log access, and permission levels are adjusted when roles change or support tasks end.

Retention schedule

We keep records for the period needed for account service, dispute handling, security checks and legal duties. When data no longer has a valid purpose, deletion or masking steps apply.

Change log discipline

Policy edits are tracked internally so we can see what changed and why. If a material privacy change affects your account, we aim to place the update where you can see it.

Pakistan wording

We write this page in clear Pakistani English and use local payment names you recognise. That helps you connect the policy text with the account actions you take on o00o.

Same privacy language across key pages

Privacy wording should not change tone from one legal page to another. We align this Privacy Policy with our account terms, cookie text and support scripts so your...

Privacy Policy
This page explains the full account data cycle: collection, use, sharing, security, retention and your request paths. It is the main privacy reference for your o00o profile.
Terms page
Our terms describe account rules, while this Privacy Policy explains the data used to support those rules. Both pages use the same account identity and support contact approach.
Cookie text
Cookie wording covers browser storage, analytics tags and session signals. This policy connects those signals to account security, remembered settings and the choices available on your device.
Support scripts
Support replies follow the same privacy boundaries shown here. Our team can discuss your own account after verification, but cannot disclose another account holder’s data.
Payment screens
Payment pages ask for only the details needed to route and match a request. The privacy wording here explains why transaction references may be stored after processing.
Security prompts
Login alerts, device checks and password resets use data for account protection. This policy explains those signals without turning them into public profile details.
Promo board
If you check what is running this week, we may use account status to show eligible content. This policy explains that data use and related messaging controls.

Privacy layout built for Pakistan

This page is arranged so you can scan the Privacy Policy before opening an account or updating your profile. We place the main data themes near...

Plain section labels

Each section title tells you which privacy topic is being covered, from account data to request handling. You should not need legal training to find the part that matters.

Local wallet context

We name JazzCash, Easypaisa, SadaPay and Raast where they affect privacy. That makes the policy easier to connect with real transaction references on your account.

Short action cues

When a privacy action is available, we explain what to send and where to send it. Clear cues reduce back-and-forth and help us verify the request faster.

Security callouts

Privacy and account security meet at login, device and withdrawal checks. The page highlights those areas so you understand why some records are kept after a session ends.

Retention clarity

We separate active account data from records kept for disputes, audits or legal duties. This helps you see why deletion may not happen instantly for every record.

Mobile reading

The policy is written for phone screens as well as desktop. You can scan sections, then return later to read specific privacy points before changing account settings.

Privacy Policy questions answered

We collect details needed to create and run your account, such as contact data, login records, device signals, payment references and support messages. We use them for access, security, service and legal record needs.

We use JazzCash and Easypaisa references to match top-ups, withdrawals, reversals and support queries to your account. These records help resolve payment questions and are kept under retention rules described in this policy.

No. We do not sell your personal data. Limited sharing may happen with service partners that support hosting, security checks, payments, analytics or customer help, and only for defined account service purposes.

Yes, you can ask us to correct account details that are incomplete or wrong. We may ask for verification first, especially where the change affects login access, identity checks or payment records.

Some records must be kept for dispute handling, security checks, accounting, fraud prevention and legal duties. When the reason for keeping a record ends, we apply deletion, masking or reduced-access controls.

Send your request through live chat, email or the account page after login. Include your account ID and the specific privacy action you want, so we can route and verify it correctly.