Terms page
Our terms explain account rules, access conditions and service use. This Privacy Policy explains the personal data connected to those actions, including registration details, verification checks and login records.
LEGAL REFERENCE
Privacy Policy for Your 4 game Account
4 game keeps its Privacy Policy clear so you know what account data we collect, why we use it and how it supports access in Pakistan where local...
Pakistan privacy scopeAccount data useSecurity checksPayment record care
How We Handle Your Privacy Data
This Privacy Policy applies when you access 4 game from supported regions, create an account, verify details, contact us or use local payment rails. We collect only the data needed to run your account, protect access, process transactions and respond to privacy requests. That may include your name, phone number, login records, device signals, payment references and messages sent to support. We
do not sell your personal data. We may share limited records with payment processors, verification partners, fraud-prevention vendors and technical providers when that sharing is required to operate your account or meet lawful duties. Records are kept for as long as needed for account, security, transaction and legal reasons, then deleted or made anonymous when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How We Keep This Policy Accurate
Our Privacy Policy is maintained around the account journey we operate every day: opening, verification, login security, transaction checks and support contact. We keep the wording practical, so...
Operational wording
Policy text is written from the systems we use for account access, wallet matching and verification. That helps each privacy...
Local payment mapping
We map privacy wording to Pakistan payment flows, including JazzCash, Easypaisa, SadaPay and Raast. Each rail creates references that may...
Security team input
Our security checks cover login attempts, device changes and unusual account activity. The Privacy Policy explains these records because they...
Support record handling
Support conversations can contain identity details, payment references or account concerns. We explain how those records are used so you...
Retention checks
Data retention is tied to account status, transaction history, dispute timelines and legal requirements. We remove or anonymise records when...
Change visibility
When this Privacy Policy changes in a meaningful way, we update the page wording and date markers. You can return...
POLICY MATCH
Consistency Across Our Legal Pages
This Privacy Policy works beside our terms and cookie text, but it has a separate job. It focuses on data collection, use, sharing, security and your control requests, not promotion rules or...
Cookie text
Cookie wording covers browser storage, session tools and analytics signals. This Privacy Policy links those signals to broader account privacy, especially where device checks support security and fraud prevention.
Promotion terms
Promotion terms set out campaign conditions when available. Privacy wording stays separate, explaining how account eligibility, message delivery and consent records may be processed when you interact with a campaign.
Payment terms
Transaction rules explain processing steps for local rails. Privacy wording explains the data created by those steps, such as wallet references, transfer IDs, reconciliation logs and support attachments.
Security wording
Security pages may describe account protection in practical terms. This Privacy Policy explains the data side, including device signals, login timestamps and alerts used to identify unsafe access attempts.
Contact page
The contact page gives you service channels. This Privacy Policy explains how messages sent through those channels are stored, routed and used to resolve data, access or transaction concerns.
Update alignment
When one legal page changes, we check related wording for alignment. Privacy clauses stay focused on data practices, so you can read them without mixing in unrelated service rules.
Visible Privacy Cues on This Page
We built this page to make privacy checks easier before you create or use your 4 game account. Each visible element is meant to show what...
Plain headings
Section headings describe the privacy issue directly, such as data scope, contact routes and retention. That structure helps you move to the exact account-data concern without reading unrelated service copy.
Short context chips
The chips under the privacy notice show common Pakistan payment references that may appear in account records. They are reminders of data categories, not requests to share private wallet credentials.
Request pathways
Contact cards separate email, chat routing and transaction queries. This keeps privacy requests cleaner, reduces repeated identity checks and helps us send your concern to the correct internal queue.
Data purpose labels
Policy sections connect each data type with a purpose, such as account access, verification, transaction reconciliation or security. We avoid collecting details that do not support those stated needs.
Retention language
Retention wording explains that records are not kept forever by default. The time period depends on account status, transaction needs, dispute handling and lawful record duties in supported regions.
Control reminders
The FAQ repeats your options for access, correction and deletion requests. We include those reminders because privacy rights are easier to use when the next step is visible.
Questions About 4 game Privacy
We collect account details, contact data, login records, device signals, support messages and transaction references. The exact data depends on how you use your account and which verification or payment steps apply.
Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity to your account. They support reconciliation, withdrawal checks, dispute handling and security monitoring without requiring wallet passwords.
Yes. Send a request through the privacy contact route using the email or phone number linked to your account. We may verify your identity before sharing records to protect your privacy.
We monitor login timestamps, device patterns and unusual access signals. These records help us spot account activity that may not come from you, and they are handled under the security purposes stated here.
We share limited data only when needed for account operation, verification, payment processing, fraud prevention, technical hosting or lawful duties. We do not sell your personal data to outside advertisers.
Contact support with the detail that needs correction and the account identifier you normally use. We may request verification before changing names, phone numbers or records linked to payment checks.
Retention depends on the record type and purpose. Account, security, transaction and support records may be kept while needed for service operation, dispute handling or legal duties, then deleted or anonymised.