Terms of Use
The Terms explain account rules, while this Privacy Policy explains the data behind those rules. When account checks are needed, both pages point toward safe identity confirmation and clear record handling.
LEGAL REFERENCE
4v4.com Privacy Policy for Pakistan
We keep privacy choices beside your 4v4.com account flow, so you can see how data is collected before you open an account. This Privacy Policy explains the records...
Account dataDevice signalsPayment recordsSupport privacy
How We Handle Your Account Data
This Privacy Policy applies when you use 4v4.com where local law permits, including account creation, lobby access, verification, wallet activity and help requests. We collect the details needed to run your account, secure your session, match payment references and respond when you contact us. For Pakistan, that can include mobile number checks, device data, IP records, account name matching, transaction references and
support chat content. We keep collection narrow, use access controls inside our operations, and retain records only for account, legal, fraud-control and service reasons. If you ask about your data, we use your account and payment context to confirm we are speaking with you before sharing or changing records.
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 through the support paths connected to your account. We may ask for account identifiers, payment reference digits or recent access details so we can confirm the request safely before acting on data.
Team online
Account chat
Use the chat link inside your account for privacy questions tied to profile data, session access or wallet records. We can see the account context there, which helps us confirm your request before making changes.
Email request
Send email when you need a written privacy request, such as asking for a copy, correction or deletion assessment. Include your account email or mobile number, but keep payment PINs and passwords out.
Payment privacy query
If your question relates to JazzCash, Easypaisa, SadaPay or Raast records, share only the reference code and date. We compare that with internal wallet logs before replying about any payment data.
POLICY CARE
How We Keep Policy Checks Grounded
Our privacy wording is maintained by people who work with account access, wallet checks, support queues and site security. We keep the page practical, so you can connect each privacy point with...
Operational input
Privacy wording is checked against the way our account screens, wallet records and support tools actually work. That keeps the policy aligned with the data you share during normal account activity.
Security access
Internal access is limited by work role, so account, device and payment records are not open to every staff desk. We log sensitive actions and separate routine help from deeper account checks.
Payment matching
When a withdrawal or wallet query is checked, we compare account name, reference code, timing and rail used. This supports privacy by reducing the need to ask you for extra personal details.
Session records
We use device and IP signals to protect account access and investigate unusual activity. These records help us understand whether a login came from your usual pattern or needs extra checking.
Policy changes
When we change this Privacy Policy, we update the page date and keep the wording connected to our current account flow. Material changes are surfaced through account or site messages where suitable.
Pakistan context
Our privacy examples reflect Pakistan account use, including mobile wallets, local bank rails and English support wording. We avoid vague data language when a practical account example explains the point better.
LEGAL ALIGNMENT
Consistency Across Our Legal Pages
This Privacy Policy is written to sit cleanly beside our other account pages. Each page has its own purpose, but data handling stays consistent so your privacy rights, records and account duties...
Cookie Policy
The cookie page focuses on browser storage and site measurement. This Privacy Policy connects those signals with wider account data, including security logs, device checks and privacy choices available to you.
Wallet rules
Wallet wording explains transaction handling, while this page explains the personal data linked to JazzCash, Easypaisa, SadaPay and Raast records. We keep those references narrow and tied to account needs.
Support standards
Support pages explain how to reach us. This Privacy Policy explains what we collect during that contact, why we may ask verification questions, and how support records are handled after your case closes.
Security wording
Security pages focus on account access controls. This Privacy Policy adds how device data, IP records and unusual activity signals are processed when we protect your account from unauthorised access.
Promotion terms
Promotion wording may describe eligibility checks. This Privacy Policy explains the data used for those checks, such as account status, wallet activity and location signals in supported regions.
Account closure
Closure wording explains how access ends. This Privacy Policy explains which records may remain afterward for legal, fraud-control, payment reconciliation and support history purposes before scheduled removal.
Privacy Layout At A Glance
We designed this Privacy Policy to be easy to scan without turning it into a legal maze. The visible layout points you to the data type...
Clear account labels
Each privacy section uses account wording you already see on 4v4.com, such as profile, wallet, session and support. That helps you connect policy language with the screen where the data is created.
Pakistan examples
Where a privacy point needs context, we use Pakistan examples such as mobile wallet references, Raast traces and local support contact. This keeps the policy close to your actual account experience.
Short data lists
Data categories are grouped into short lists instead of long legal blocks. You can quickly see whether a paragraph relates to identity, device signals, wallet records, support messages or site preferences.
Action cues
Privacy actions are phrased around what you can ask us to do, such as access, correction or deletion assessment. We also explain when we need identity checks before acting on a request.
Retention markers
Retention wording is placed near the relevant data category, so you can see why certain records may stay for account security, legal needs, payment reconciliation or support history before removal.
Contact placement
Contact paths appear near privacy rights rather than hidden at the end. This makes it easier to move from reading the policy to sending a clear request through chat or email.
Privacy Questions From Your Account
We collect data needed to create, secure and operate your account, including contact details, login records, device signals, wallet references and support messages. We avoid asking for extra details that are not needed for the account task.
Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity with your 4v4.com wallet. They also help us answer disputes, trace failed transactions and reduce the need to request full personal payment details.
We use device and IP data to protect account access, detect unusual logins and keep site functions stable. These signals also help us apply access rules for supported regions where local law permits.
Yes. Contact support from your account or email us with the data you believe is incorrect. We may ask identity questions first, then update eligible records or explain why a record must remain unchanged.
We share only what is needed to process, trace or confirm a transaction through the relevant rail. For Pakistan activity, that can include reference details linked to JazzCash, Easypaisa, SadaPay or Raast checks.
Retention depends on the record type and legal or operational need. Some support messages may be removed sooner, while payment, security and fraud-control records can be kept longer before scheduled deletion.
Use account chat for logged-in requests or email us if you need a written record. Please include your account identifier, but never send passwords, payment PINs or full wallet credentials.