LEGAL REFERENCE

How fun4 handles your data

Our Privacy Policy explains what account, device, payment and support data we collect when you use fun4 in supported regions of Pakistan. Open your account only after you...

Pakistan account dataJazzCash contextEasypaisa contextRaast records

Browse lobby Read FAQ

Privacy terms for Pakistan access

This Privacy Policy applies when you access fun4.net, create an account, use our casino or sportsbook areas where local law permits, contact support, or use Pakistan payment rails linked to your account. We collect only the data needed to run the account flow, confirm payments, secure access, resolve service issues, and meet record duties that apply to our operation. This can include

your name, phone number, login activity, device signals, wallet references, transaction status, and messages sent to our team. We do not sell your personal data. We may share limited records with payment partners, verification services, hosting providers, fraud-control tools, or legal contacts when needed for the purposes described here. You can ask us to access, correct, or remove eligible data, subject to

account safety, pending transactions, and lawful retention needs.

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

CONTACT ROUTES

Where to send privacy requests

If you have a privacy question, use a contact path that lets us confirm the account before sharing or changing records. Include...

CARE CHECKS

How we keep this policy accurate

We maintain this Privacy Policy alongside the systems that hold your records, so the wording matches the account flow you actually use. When a data field, payment partner, support tool, or security...

Data mapping

We map account fields to their purpose, such as login security, payment matching, support handling, or fraud control. This helps us remove unnecessary collection points before they become part of the flow.

Payment matching

JazzCash, Easypaisa, SadaPay and Raast references are handled as account records, not public profile details. We keep them tied to transaction checks and support tracing only.

Access controls

Internal access is limited by work role. Support can see what is needed to help you, while sensitive payment or security records require stronger permission and logged handling.

Device security

We use device and session signals to spot unusual account access. These signals help us protect your account without asking for more personal details than the security check needs.

Retention checks

Some records must stay while payments, disputes, or legal duties remain open. When retention is no longer needed, we aim to delete, anonymise, or separate records from account use.

Change log

When we amend this Privacy Policy, we update the page date and adjust affected wording. Major changes are surfaced through account or site messages where a clear notice is needed.

How this page stays consistent

Your privacy rights should not change just because you move between account pages, support pages, casino areas, or sportsbook screens. We use one privacy position across fun4.net, then...

Account terms

Our account terms explain service rules, while this Privacy Policy explains data handling. Where both pages mention verification, this page focuses on what data is used and why.

Cookie page

Cookie wording covers browser storage, analytics and session tools. This Privacy Policy links that activity to account security, site performance, and choices you can manage through your browser.

Payment wording

Payment pages describe JazzCash, Easypaisa, SadaPay and Raast steps. This page explains the linked records, such as wallet reference, payment status, account match, and support trace.

Support content

Support pages help you solve account issues. This Privacy Policy explains how chat transcripts, email threads, screenshots, and verification replies are stored and used for follow-up.

Security messages

Security prompts may ask you to confirm a code, reset a password, or recheck a device. This policy explains the related data signals and their account-protection purpose.

Promo board

If you view a promotion area, we may record eligibility, opt-in state, and account status. This Privacy Policy explains that handling without turning it into public profile data.

Regional wording

Access wording may refer to supported regions and where local law permits. The privacy commitments on data purpose, security handling, and request routes remain aligned across the site.

Privacy layout cues you can use

We designed this page so you can scan the privacy position before opening or continuing your account. Headings separate collection, use, sharing, storage, and request routes...

Plain headings

Each heading names the privacy topic directly, so you can move from collection to sharing to requests without guessing which account record is being discussed.

Local context chips

Short chips mention JazzCash, Easypaisa, SadaPay and Raast where those names help explain wallet references, receipt checks, and account matching for Pakistan.

Action wording

Request wording tells you what to send and what never to share, including wallet PINs and passwords. This keeps privacy support clear and safer.

Record examples

Examples such as login activity, device signals, wallet references, and support messages show the data types in context rather than leaving the policy abstract.

Sharing boundaries

Partner sharing is described by purpose, such as payment matching, hosting, verification, or legal response. We avoid broad wording that would make the boundary unclear.

Update cues

The policy explains when changes may appear and how important updates may be surfaced. That helps you connect page changes with account notices.

Common questions about this policy

We collect account details, login records, device signals, payment references, support messages, and verification responses needed to run your account, protect access, process transactions, and answer privacy or service requests.

Wallet references help us match a transaction to your fun4 account, trace failed or delayed payments, handle support queries, and meet record duties. We do not place wallet details on public profile pages.

Yes. Send a privacy request through email or support routing with your username and linked phone number. We verify ownership before sharing eligible records or explaining why a record must be retained.

We use session records, device signals, password controls, and restricted internal access to reduce account misuse. Staff access is tied to work role, and sensitive actions may require extra checks.

We share limited data only when needed for hosting, payment matching, verification, security checks, support tools, or legal response. Each sharing route is linked to a purpose described in this Privacy Policy.

Some details can be changed in your account area. For linked phone numbers, transaction records, or support history, contact us so we can verify ownership and apply the correction safely.