LEGAL REFERENCE

Privacy Policy for your caapk account

caapk keeps account details, lobby activity and transaction privacy rules in one clear Privacy Policy for Pakistan access where local law permits. Open your account with a clear...

Account data usePakistan privacy contextJazzCash record handlingSupport request access
caapk Privacy Policy for your caapk account

How we handle your privacy

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

PRIVACY CONTACT

Ways to reach our privacy team

You can contact us about this Privacy Policy through the same support routes used for account help, but privacy requests are handled as a separate queue. Include the email or phone number linked to your account, the request type and any transaction reference if the question relates to a payment record. We may ask you to confirm control of the account before sharing or changing personal details.

Team online

Live chat privacy queue

Use live chat when you need a quick privacy status check. Our team can log access, correction or deletion requests, then move the case to the privacy queue for identity confirmation.

Email request record

Send privacy questions by email when you want a written trail. Mention caapk, your account contact detail and the exact data request so we can route it without extra back and forth.

Payment reference help

If your privacy question involves JazzCash, Easypaisa, SadaPay or Raast records, include the reference shown on your receipt. We use it only to locate the related account transaction.

POLICY CHECKS

How we keep this policy accurate

We maintain this Privacy Policy as an operating document, not as a static legal page. Product, support, security and wallet teams check it when we change account flows...

Account flow checks

Before we change account creation or login fields, we check whether the Privacy Policy explains the data being requested, the...

Wallet record checks

Our wallet team checks privacy wording against JazzCash, Easypaisa, SadaPay and Raast handling, including reference storage, withdrawal verification and the...

Security wording checks

Security staff confirm that policy wording matches our actual controls, including session monitoring, unusual login flags, device checks and internal...

Support script checks

Support responses are checked against this Privacy Policy so privacy requests are not treated like ordinary account questions. That keeps...

Retention checks

We check retention wording when record periods change for account, transaction or dispute files. The goal is to avoid keeping...

Change log control

When this page changes, we track the reason internally and make the wording clearer for you. Material changes are reflected...

PAGE CONSISTENCY

How this policy fits nearby pages

This Privacy Policy sits beside our account terms, cookie wording and contact pages, but it has a narrower role. It explains data collection, use, storage, sharing and request rights connected with caapk...

01

Account terms link

The account terms describe service rules, while this Privacy Policy explains what account details we collect to apply those rules, verify access and keep records of service decisions.

02

Cookie wording link

Cookie wording explains browser storage and tracking choices. This Privacy Policy explains how those signals may connect with login security, session continuity and account protection inside caapk.

03

Support page link

The support page helps you contact us, while this Privacy Policy explains what details may be collected during that contact and how the conversation record is handled.

04

Payment page link

Payment pages explain transaction routes. This Privacy Policy explains how references from JazzCash, Easypaisa, SadaPay and Raast are stored, matched and used for account verification.

05

Promotion page link

Offer pages may ask you to open or check account areas. This Privacy Policy explains how any related account activity is recorded and used for service handling.

06

Security page link

Security wording describes account protection steps. This Privacy Policy explains the data behind those steps, including device checks, login patterns and restricted internal access.

07

Contact page link

The contact page gives routes to reach us. This Privacy Policy explains how we handle your name, contact detail, message content and identity checks after you reach out.

LAYOUT MARKERS

What you see on this policy page

We have laid out this Privacy Policy so the main privacy choices are visible without making you search through dense wording. The page separates account data, transaction records...

Plain summary blocks Short summary blocks explain the purpose of each privacy area...
Data category labels We label categories such as contact details, account activity, device...
Request route panel A visible request panel points you toward privacy contact routes...
Retention marker row Retention markers explain why some records are kept for service...
Sharing explanation cards Sharing cards separate internal teams, payment processing support and service...
Update notice area An update area tells you when policy wording changes. We...

Privacy Policy questions from Pakistan

We collect details needed to create and operate your account, such as contact data, login records, device signals, wallet references and support messages. The Privacy Policy explains each use and the reason behind it.

We store transaction references, status logs and matching account details so payments can be confirmed and disputes checked. We do not publish your wallet record, and access is limited to relevant staff.

We share data only where needed for service operation, security checks, payment handling, support, legal requests or business administration. The Privacy Policy explains the categories involved rather than selling your personal details.

Yes. Contact support with the account detail you want corrected and proof that you control the account. We may keep some prior records where they are needed for disputes or legal duties.

Retention depends on the record type. Account, transaction, security and support records may be kept while needed for service, dispute handling or legal duties, then removed or anonymised when no longer required.

The Privacy Policy covers device signals, login patterns and session activity used to protect your account. These checks help us detect unusual access and keep internal viewing of account data controlled.

We update the wording on this page when privacy handling changes. For material updates, we aim to make the change visible in your account area or through a suitable contact route.