Terms page
The account terms explain service rules, while this Privacy Policy explains the data behind those rules, such as identity checks, access logs, wallet references, and support records.
LEGAL REFERENCE
Privacy Policy for your capri game account
capri game keeps account, wallet, device and support data in separate privacy records so you can see what is collected before you open your account. This Privacy Policy...
Account data scopeWallet privacy contextSupport contact routePakistan region wording
How our Privacy Policy handles data
We collect the data needed to run your account, secure access, process wallet actions, answer support requests, and meet checks that apply in supported regions of Pakistan. That can include your name, phone number, email address, login details, device signals, session records, wallet references, and messages you send to us. We use this data to confirm account ownership, monitor access attempts, trace
payment status, keep service records, and respond when you ask us to correct or delete eligible data. We keep records for lawful business, security, and dispute needs, then remove or anonymise them when retention is no longer required. Where local law permits, you can ask how your data is held and request changes through our support paths.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT PATHS
Contact us about Privacy Policy matters
Privacy requests work better when we can match your message to the correct account record without asking for extra details. Use the same phone or email linked to your capri game account when you contact us. Our team checks identity first, then routes correction, access, deletion, or wallet-data questions to the privacy queue for a written reply.
Team online
Email privacy desk
Send your privacy question with your account ID, phone ending, and event date. We use the message to trace data handling and reply through the same contact path.
Live chat handoff
Open chat from your logged-in account when your privacy request is urgent. The agent confirms ownership, records your request, and moves detailed data questions to the privacy queue.
Wallet record query
For JazzCash, Easypaisa, SadaPay or Raast concerns, share the transaction reference only. We compare it with internal wallet logs before giving any account-level reply.
POLICY CARE
How we keep the policy accurate
Our Privacy Policy is written from the way capri game actually handles your account, not from generic legal wording. We align it with account access, wallet tracing, game-session records, device checks, and...
Operational wording
Policy text is checked against real account flows, including login, wallet updates, support tickets, and device checks, so the wording matches how your data moves inside capri game.
Local payment context
We name JazzCash, Easypaisa, SadaPay and Raast where wallet records may appear, helping you understand why payment references are stored with account security logs.
Access control
Only authorised staff can view account-level privacy records, and each access is tied to a support, security, wallet, or compliance reason connected to your request.
Retention checks
We review retention needs for identity, wallet, support, and session records, then remove or mask data when business, security, or legal reasons no longer require it.
Plain language
We avoid legal padding where a direct sentence works. The policy explains what we collect, why we collect it, and how you can ask us about it.
Change tracking
When privacy wording changes, we keep the effective date visible and align related account pages so your choices and contact routes remain easy to follow.
PAGE ALIGNMENT
How privacy terms align across pages
Your privacy rights should not change because you read a different capri game page first. We keep this Privacy Policy aligned with account terms, cookie wording, wallet text, support scripts, and security...
Cookie page
Cookie wording covers browser storage and similar tools, while this Privacy Policy connects those signals with device security, session protection, and account preference handling.
Wallet page
Wallet text describes transaction flow, while this policy explains why reference numbers, status changes, and provider names may be linked to your account record.
Account access
Login prompts focus on getting you into the account, while this Privacy Policy explains how device checks and access history help protect your personal data.
Support page
Support pages show how to reach us, while this policy explains how your messages, attachments, and account details are stored and used for replies.
Security page
Security text covers protection steps, while this Privacy Policy explains the personal data used for monitoring, account recovery, suspicious activity checks, and verification.
Offer pages
Offer pages may ask you to log in, while this policy explains how account status, eligibility checks, and related records are handled with privacy controls.
LAYOUT CUES
Visible cues inside this Privacy Policy
We design this Privacy Policy so you can scan it without losing the legal meaning. Labels, dates, section headings, contact cards, and short chips help you spot the...
Scope labels
Short labels separate account data, wallet references, device signals, support...
Effective date
The policy date sits near the start so you can...
Contact cards
Dedicated contact cards keep privacy requests apart from normal account...
Local context chips
Pakistan-specific chips identify where JazzCash, Easypaisa, SadaPay and Raast records...
Choice prompts
Where a section mentions access, correction, or deletion requests, the...
Retention markers
Retention markers explain why some records stay longer for security...
Privacy Policy questions from Pakistan
We collect account details, contact data, device signals, login history, support messages, and wallet references needed to run your account, protect access, process requests, and meet lawful record duties.
JazzCash, Easypaisa, SadaPay and Raast references help us trace payment status, confirm ownership, investigate disputes, and keep wallet activity connected to the right account record.
Yes. Contact us from your linked phone or email, describe the data that needs correction, and provide proof if needed. We verify ownership before making changes.
We keep records for account operation, security, wallet tracing, support history, and lawful duties. When those reasons no longer apply, we delete, mask, or anonymise eligible data.
We share data only where needed for account operation, payment processing, security checks, support tools, or legal duties. Partners receive the data required for that task.
Use the privacy contact route from your linked account details. Include your account ID, request type, and any relevant wallet or support reference so we can locate records.