LEGAL REFERENCE

Privacy Policy for Your c63 Account

Our Privacy Policy explains what c63 collects when you create an account, verify access, use local payment rails, or ask us for help. Open your account with a...

Account data useJazzCash and Easypaisa contextDevice safety checksSupport record handling
Explore Lobby Read FAQ
c63 Privacy Policy for Your c63 Account

How We Handle Your Data

This Privacy Policy describes how c63 handles personal data connected with account access, identity checks, session activity, payment references, and support conversations. We collect only the data needed to run your account, protect access, confirm transaction status, answer your requests, and meet duties that apply where local law permits. Payment rail details are used as reference markers rather than as open banking

access; for example, a JazzCash or Easypaisa status record helps us match your request to the correct account event. We keep records for limited operational, security, and legal purposes, then remove or anonymise them when retention is no longer needed. If policy wording changes, we update this page so you can read the current version before you continue.

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

CONTACT ROUTES

Privacy Help When You Need It

You can contact us about this Privacy Policy without explaining your whole account history again. Send the detail you want checked, the...

Privacy email Email us about correction, access, deletion, or retention...
Live chat path Use chat when you need a quick privacy...
Account centre Inside your account area, you can check profile...
POLICY CARE

How Our Policy Stays Accurate

We maintain this Privacy Policy as an operating document, not a placeholder. The wording is checked against account flows, payment reference handling, support scripts, and security controls used by c63. When a...

Account flow checks

We compare the policy against the fields you see during account creation and verification. If a field becomes unnecessary, we remove it from the flow or clarify its purpose.

Payment rail mapping

JazzCash, Easypaisa, SadaPay, and Raast references are mapped to privacy categories. That keeps payment status data separate from profile data, support chat records, and security logs.

Security log limits

Device, IP, and session records are used to protect account access and investigate unusual activity. We limit who can view those logs and keep access tied to work duties.

Support script alignment

Support replies are aligned with this Privacy Policy so you receive consistent explanations. If a privacy request needs deeper handling, the case is moved away from public chat.

Retention checks

We check whether account, payment, and security records still serve a valid purpose. When a retention reason ends, records are removed, reduced, or anonymised according to our process.

Change tracking

Policy edits are tracked internally with the reason for each change. This helps us explain what changed and keeps privacy wording connected to the way c63 actually operates.

Policy Consistency Across c63 Pages

Your privacy rights should not depend on which c63 page you read first. We keep wording aligned across legal pages, account screens, help replies, and security prompts. This...

Terms page link
Our terms explain account rules, while this Privacy Policy explains data handling. Where the two connect, we use matching wording so your rights and duties stay clear.
Cookie page link
Cookie wording describes browser storage and similar tools. This Privacy Policy connects that activity to account privacy, device checks, security monitoring, and your choices where settings are available.
Security prompts
Login alerts, verification screens, and password reset flows use short messages. We keep those messages consistent with this Privacy Policy so security data use is not hidden.
Payment screens
Payment screens show rail names and transaction status. This Privacy Policy explains how those status records are matched, protected, and retained without turning payment references into profile profiling.
Support replies
When support answers a privacy question, the reply should reflect this page. We avoid casual promises in chat and keep the response tied to the policy wording.
Promo board privacy
If you check the promo board, c63 may record eligibility and account interaction data. This Privacy Policy explains that handling without treating promotional display data as unrelated.
Account closure
If your account is closed, some records may remain for security, dispute, or legal reasons. This Privacy Policy explains those limits before data is deleted or anonymised.
LAYOUT SIGNALS

Privacy Layout Built for Clarity

The Privacy Policy page is arranged so you can find practical privacy points without hunting through unrelated copy. We surface account data, payment references, device records, support handling...

Readable sections Each part of the page covers one privacy subject, such...
Local context chips Short chips name JazzCash, Easypaisa, SadaPay, and Raast where payment...
Plain language We explain collection, use, sharing, and retention in direct English...
Account-first framing The page follows your account journey from creation to verification...
Rights placement Access, correction, deletion, and objection routes are placed near contact...
Update visibility When policy wording changes, the current page carries the active...

Privacy Questions from Pakistan Accounts

We collect account details, contact data, verification records, device signals, session logs, payment references, and support messages. Each category is tied to account operation, security, transaction matching, or help you request from us.

They are named because payment status records can contain personal data. The policy explains how we match JazzCash and Easypaisa references to your account without asking for unnecessary wallet access.

Device and login data helps us detect unusual access, maintain sessions, and protect your account. We use these records for security and operational checks, not to create unrelated personal profiles.

Yes. Send us the detail you believe is wrong and the account contact linked to c63. We verify the request before changing records, especially when payment or security data is involved.

Retention depends on the record type and the reason it was collected. Account, payment, support, and security records are kept only while needed for operational, dispute, security, or legal purposes.

We share data only where needed for account operation, payment processing, security checks, support handling, or legal duties. Service providers must handle the data according to the purpose we assign.

Use privacy email, live chat handoff, or your account centre to raise a request. Include your account contact and the privacy issue so we can locate the correct record securely.