LEGAL REFERENCE

Privacy Policy For Your coco92 Account

coco92 keeps your privacy choices, account details and Pakistan payment records in one clear policy, so you know what we collect before you open an account. Read how...

Pakistan account dataJazzCash contextEasypaisa recordsPrivacy request paths
Explore the Lobby Read FAQ
coco92 Privacy Policy For Your coco92 Account

How We Handle Your Privacy Data

Under this Privacy Policy, we explain the account data coco92 collects when you create access, verify your profile, enter the lobby or ask for a payout in supported regions of Pakistan. We may collect your name, mobile number, login activity, device signals, transaction references and messages you send to our team. When JazzCash, Easypaisa, SadaPay or Raast appears in your account flow,

we keep only the records needed to match the request, protect the account and answer lawful requests where local law permits. We do not sell your personal data. We restrict internal access, keep audit trails for sensitive actions and remove or anonymise records when they are no longer needed for the stated purpose.

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

PRIVACY CONTACT

Reach Us About Privacy Requests

If you want to ask about stored data, correction, access, deletion or account security records, contact us through the paths below. We...

Live Chat Request Start live chat from this page when you...
Email Privacy Desk Send your request by email with the account...
Account Panel Form Use the account panel to request copies, corrections...
POLICY CHECKS

How This Policy Stays Accurate

We maintain this Privacy Policy from the way coco92 actually handles account records, not from generic wording. Our team checks collection points, wallet matching, login security, support replies and retention periods so...

Collection Points

We map each data field to a purpose, such as account access, wallet matching, fraud prevention or support response. If a field has no clear reason, it should not stay in the flow.

Local Rail Context

JazzCash, Easypaisa, SadaPay and Raast references are treated as financial context, not public profile data. We use them to match requests, reconcile records and resolve account queries.

Access Controls

Only staff roles that need privacy data for support, checks or account safety can access it. Sensitive actions are recorded so unusual access can be traced internally.

Retention Windows

We keep account and transaction records for operational, legal and security reasons, then reduce or remove them when the purpose ends. Exact timing may vary by record type.

Change Checks

When account screens, wallet flows or support forms change, we check whether this Privacy Policy needs an update. The aim is simple wording that matches real handling.

Human Replies

Privacy requests are not left to automated messages alone. A support teammate checks the request, confirms ownership and sends the response through the safest available contact path.

Policy Pages Kept In Sync

Your privacy rights connect with other legal pages, account screens and help messages on coco92. We keep wording aligned so you do not see one promise in this...

Account Terms
Our account terms describe eligibility, account control and platform access. This Privacy Policy explains the data handling behind those checks, including mobile number use, verification records and login protection.
Cookie Page
Cookie wording covers browser storage and device signals. This Privacy Policy connects those signals to account security, session handling and preference choices, so the two pages read consistently.
Promotion Rules
Where promotions require account checks, the matching rules must respect this Privacy Policy. We only use the data needed to confirm eligibility, prevent abuse and manage your account record.
Security Page
Security wording explains how we protect access. This Privacy Policy explains what data may be used for that protection, such as device signals, login attempts and support verification steps.
Contact Page
The contact page gives support paths; this policy explains privacy handling once you use them. Messages, attachments and identity checks are stored only for support, safety and lawful needs.
Verification Prompts
Verification prompts may request documents or wallet context. This Privacy Policy explains why those records are collected, who can access them and how long they may be retained.
App Screens
Mobile screens may ask for login, device or notification choices. This policy keeps those prompts tied to clear purposes, rather than collecting hidden data without account relevance.
POLICY MARKERS

Privacy Layout You Can Scan

We shaped this Privacy Policy so you can find the parts that matter before you open, manage or close an account. The layout uses short markers, request links...

Quick Summary The opening section states what data we collect and why...
Data Map Each privacy area connects data types with purposes, such as...
Choice Panel Where choices are available, the policy points you toward account...
Request Buttons Privacy request links sit near relevant wording, so you do...
Retention Tags Retention wording appears beside the records it concerns, including account...
Update Banner When the Privacy Policy changes in a meaningful way, we...

Privacy Policy Questions Answered

We collect account details such as your name, mobile number, login activity, device signals, wallet references and support messages. Each record must connect to account access, safety, transactions or service response.

Wallet references help us match JazzCash, Easypaisa, SadaPay or Raast activity to the correct account. We use them for reconciliation, payout checks, dispute handling and lawful record keeping.

Yes, you can request access to personal data connected to your account. We first confirm ownership, then provide the available record in a safe format or explain any lawful restriction.

Contact support with the account phone number and the detail that needs correction. We may request proof before changing identity, wallet or security records, especially where the change affects access.

Access is limited to staff roles that need the data for support, verification, transaction matching or account protection. Sensitive access is recorded, and staff should not open records without a valid task.

Retention depends on the record type and purpose. Account, transaction and security records may be kept for operational or lawful needs, then reduced, anonymised or removed when no longer required.

If we make a meaningful Privacy Policy change, we may show a notice on the site, account area or contact channel. The updated wording will explain the new handling clearly.