LEGAL REFERENCE

Privacy Policy for your cu club account

cu club keeps account details, lobby activity and Pakistan payment records under one clear Privacy Policy, so you know what we collect before you open an account. Read...

Account data useJazzCash contextEasypaisa contextSadaPay recordsRaast references
Explore Lobby Read FAQ
cu club Privacy Policy for your cu club account

How we handle privacy in Pakistan

This Privacy Policy explains how cu club collects, uses, stores and protects data connected with your account, device access, live casino sessions, slot-room activity, sportsbook entries and support contact. We ask for details needed to run the account flow, check access where local law permits, verify payment records and respond to privacy requests. Payment references from JazzCash, Easypaisa, SadaPay and Raast may

be used to match transactions with your account, but wallet PINs and private app passwords are not requested by us. We limit staff access, keep security logs, and remove or restrict records when our legal, security and account duties allow. If wording changes, this page is the place where we publish the current policy.

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

PRIVACY CONTACTS

Ask us about privacy handling

Privacy questions need a clear path, not a generic inbox. Use the contact route linked to your account when you want to ask about stored data, correction requests, access records or a payment reference attached to your profile. We may ask for account identifiers so we can find the right file, but we will not ask for wallet PINs or private app passwords.

Team online

Account email

Send us the email linked to your account and state which privacy point you want checked. We match the address before discussing records, so your request stays tied to you.

Live chat handoff

Live chat is open inside the account area for quick privacy questions about login alerts, session records or device changes. We may move detailed requests to email for a clearer written trail.

Payment reference help

For payment-data questions, include the reference from JazzCash, Easypaisa, SadaPay or Raast. We check only the record needed for privacy tracing and do not ask for wallet PINs.

POLICY CHECKS

Privacy checks built into operations

Our privacy work sits inside the daily account process, not apart from it. The same operational teams that handle login security, payment matching and support queues also follow written limits on what...

Separated records

We separate account profile data, payment references and support conversations where our systems allow it. That reduces unnecessary exposure and helps staff look only at the record connected with your request.

Access controls

Staff access is role based, with payment matching, account support and technical checks treated differently. Before anyone handles sensitive records, we require an internal reason linked to your account or request.

Security logs

Login activity, device signals and system alerts are logged to help protect accounts and investigate unusual access. These logs support privacy controls by showing when records were touched or changed.

Policy checks

We check the Privacy Policy when account screens, payment rails or support scripts change. The aim is simple: this page should reflect how cu club actually handles your data.

Local context

Pakistan payment references can look different across JazzCash, Easypaisa, SadaPay and Raast. Our policy names these rails so you understand why a transaction code may appear in account checks.

Request trail

When you ask about privacy, we keep a short trail of the request, our response and any action taken. That helps us avoid repeating identity checks and keeps answers consistent.

How this policy stays consistent

This page works with our other legal pages, but it has one job: explaining privacy. Terms pages explain account rules, cookie pages explain browser storage, and this page...

With account terms
Account terms describe what you agree to when using cu club; this Privacy Policy describes what data supports that account. If both pages mention verification, this page explains the data side.
With cookie wording
Cookie wording covers browser storage, session tags and device signals. This Privacy Policy connects those signals to account protection, support checks and your choices where settings are available.
With payment screens
Payment screens may show JazzCash, Easypaisa, SadaPay or Raast references. This policy explains why those references can be stored for matching, support handling and account-security checks.
With support replies
Support replies should match this policy when we answer privacy questions. If you ask about access, correction or stored records, the response should follow the language published here.
With login alerts
Login alerts and device checks are security features, but they also create records. This policy explains the privacy side: what may be logged and why it may be retained.
With withdrawal checks
Withdrawal checks can require account and payment matching. This policy explains how related data is handled, who may see it, and why a reference can be connected with your profile.
With future wording
When a related page changes, we check whether this policy also needs an update. We keep the privacy explanation focused on data rather than general account promotion.
LAYOUT SIGNALS

Policy layout cues on this page

A privacy page should be easy to scan before you create or use an account. We place the main policy statement first, contact options next, then operational checks...

Short badges The badges under the hero mark the data areas most...
Plain section order We start with the policy posture, then show contact routes...
Local names JazzCash, Easypaisa, SadaPay and Raast are named directly because payment...
Request wording Contact cards use practical language so you know what to...
Operational signals The policy check cards show how privacy connects to login...
Question block The final questions answer likely privacy concerns without sending you...

Privacy questions before you join

We collect account details needed to create and secure your profile, such as contact data, login records and verification details. We also store support messages when you contact us about privacy or account access.

JazzCash, Easypaisa, SadaPay and Raast references help us match transactions with your account and answer support questions. We use the reference record, not your wallet PIN or private app password.

We may record activity linked to your account, including session timing, game or market entries and settlement records. This supports account history, security checks and support handling where local law permits.

Yes. Contact us through the account-linked route and explain what should be corrected. We may ask for proof before changing records so the update is accurate and tied to your profile.

Retention depends on the record type, legal duties, security needs and account history. We keep data only for purposes described in this policy, then delete, restrict or anonymise it when allowed.

Access is limited by role. Support, payment matching and technical teams see different record types, and staff should only handle data when there is an account reason, security need or privacy request.

We publish the current wording on this page. When changes affect how we collect, use or store your data, we update the page so you can read the latest privacy position.