LEGAL REFERENCE

Privacy Policy for your account

Our Privacy Policy explains what 3o game collects when you open your account, enter the lobby, use local rails and contact our team. We keep the wording practical...

Pakistan account dataJazzCash contextDevice checksSupport contact
Browse Lobby Read FAQ
3o game Privacy Policy for your account

How we handle your privacy

This Privacy Policy applies when you use 3o game from supported regions where local law permits. We collect details needed to create your account, keep access secure, process wallet activity, respond to support messages and meet record keeping duties. That can include your name, mobile number, login data, device signals, session activity and payment references from Pakistan rails. We do not ask

for more than we need for the account flow, and we separate sensitive checks from ordinary service messages where our systems allow it. If a data request involves verification, we may ask for extra proof before making any change.

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

CONTACT PATHS

Ask us about your data

Privacy questions should reach the team that can connect your request with the right account record. Tell us which email or mobile number is linked to 3o game, then describe the privacy request clearly. We may verify you first, because changing or sharing account data without proof can put your balance and identity at risk.

Team online

Email privacy request

Use email when you need a written trail for access, correction or deletion queries. Include your registered mobile number, the date of your request and only the documents we ask for.

Live help routing

Use live help for basic privacy questions while you are signed in. Our team can route the case, confirm needed proof and avoid exposing account details in open chat.

Security escalation

If you think your account was accessed by another person, contact us quickly. We may pause sensitive changes while we check login signals, device data and recent payment references.

CHECK CYCLE

Policy checks behind this page

We keep this Privacy Policy close to the systems you actually use. Account, wallet, security and support teams help us keep the wording aligned with live workflows. When a form, verification step...

Account data mapping

We map each account field to a reason, such as login access, identity checks or support handling. This helps us remove unclear wording and explain why each field exists.

Local rail context

JazzCash, Easypaisa, SadaPay and Raast records are treated as transaction references, not public profile details. We use them to match requests, trace errors and support withdrawals.

Device signal checks

We use device and session signals to help spot unusual access. The policy separates these security checks from ordinary browsing data so you understand their different purposes.

Support record control

Support messages may contain sensitive details, so we limit who can open them and use case history only to answer your request or investigate account activity.

Retention schedule

We keep records for the time needed to run accounts, resolve disputes and meet legal duties. When retention is no longer needed, deletion or masking may apply.

Policy wording checks

We check privacy wording against product changes, contact routes and local account flows. If wording becomes unclear, we update it so your choices stay understandable.

How this policy stays consistent

This Privacy Policy sits beside our other legal pages, but it has a different job. It explains data collection, use, sharing, storage and your request routes. We keep...

Terms alignment
Our Terms explain account use, while this page explains data use. Where both mention verification, this policy focuses on what personal data may be checked and why.
Cookie alignment
Cookie wording connects with this policy when browser storage affects login, analytics or security. This page explains the broader data purpose beyond cookie placement.
Security alignment
Security wording covers account protection steps. This Privacy Policy explains the personal data behind those steps, including device signals and unusual access checks.
Support alignment
Support pages explain how to contact us. This policy explains how support messages are stored, who may handle them and why identity proof may be requested.
Wallet alignment
Wallet rules describe transaction handling. This policy explains how payment references from JazzCash, Easypaisa, SadaPay and Raast are used for matching and records.
Offer alignment
Offer rules may refer to eligibility checks. This privacy page explains the data side of those checks, including account status and activity records.
Change alignment
When another legal page changes, we check whether privacy wording must change as well. This keeps your account data rights readable across the site.
LAYOUT SIGNALS

What you see on this policy

We designed this privacy page so you can scan the areas that affect your account first. The layout separates collection, security, sharing and contact routes instead of burying...

Clear section labels Each heading names the privacy issue it covers, such as...
Local examples We mention Pakistan account flows and local rails where they...
Plain wording We avoid dense legal phrasing where a clearer sentence works...
Action routes Contact routes are placed near the privacy rights they support...
Security cues We mark where verification may happen before data is shared...
Update awareness Policy updates are handled with the same page structure, so...

Privacy Policy questions answered

We may collect your name, mobile number, login details, device signals, session activity, support messages and payment references. The exact data depends on how you open and use your account.

Device data helps us recognise normal access and detect unusual account activity. It may include browser type, device markers, IP signals and session timing used for security checks.

We use local payment references to match wallet activity, trace failed requests and answer support cases. These records are treated as account data and are not shown publicly.

Yes, you can ask us to correct account data that is wrong or out of date. We may verify your identity before changing details tied to access or payments.

We may share limited data with service providers that help run hosting, security, support, analytics or payment processing. They receive only what is needed for that task.

We keep data while your account is active and for periods needed for disputes, security checks and legal duties. After that, records may be deleted or masked.

Contact support from your registered email or signed-in account and describe the request. We may ask for proof before giving access, making corrections or deleting eligible data.