Account terms
Account terms explain how your account may be used. This Privacy Policy explains what data sits behind that account, why it is collected and how privacy requests are checked.
444x keeps account details, device checks and Pakistan wallet records under one Privacy Policy, so you can see how your data is collected, used and protected before you...
This Privacy Policy describes how 444x collects and uses data when you create an account, verify access, contact support, use the lobby or send wallet transfer details where local law permits. We collect only the account, security, device, payment reference and contact data needed to run your account flow, protect access and respond to your requests. Some records are kept to meet
fraud checks, transaction tracing and service obligations in supported regions. We do not sell your personal data. When third-party tools help with hosting, analytics, payments or support, they receive only the data needed for that task. You can ask us to update, correct or remove eligible data, subject to records we must retain for account safety and transaction history.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We write this policy from the way 444x actually runs account, support and wallet workflows. Each privacy control below connects to a real action: login checks, payment reference...
When you log in, we check device signals, session data and saved contact details. This helps us detect unusual access...
JazzCash, Easypaisa, SadaPay and Raast records are stored as transaction references, timestamps and account links. We avoid collecting wallet PINs...
Support chats and emails are saved with your account so we can follow up on privacy requests without making you...
When you update your email, phone or name, we keep a change trail. That trail helps confirm whether the update...
We keep account and transaction data only for business, security and legal needs. Records that are no longer required are...
Hosting, analytics, support and payment service partners receive only the data needed for their task. We do not give them...
Our Privacy Policy works beside other 444x legal pages, but it has a separate job. It explains data handling, not game rules, promotions or account terms. The points below show how privacy...
Account terms explain how your account may be used. This Privacy Policy explains what data sits behind that account, why it is collected and how privacy requests are checked.
Cookie wording covers browser storage and session tools. This policy connects those tools to wider account privacy, including login sessions, analytics checks and device safety signals.
Wallet rules describe how transfer records are matched. This policy adds how those records are stored, who may access them and how you can ask questions about them.
Security wording focuses on access protection. The privacy section explains the personal data used for those checks, such as device details, contact records and session history.
Promotion terms may set out offer rules. This policy only covers the data involved, such as eligibility checks, message preferences and account records linked to promo activity.
Support pages explain how to reach us. The privacy wording explains how support messages are stored, connected to your account and handled when you request data changes.
Access wording may refer to supported regions. The privacy policy uses the same regional approach while explaining how data is handled where local law permits.
We designed this privacy page so you can scan it without losing the legal meaning. The layout separates collection, use, sharing, retention and contact steps. Each...
The badge row near the headline highlights account data, wallet records and support contact routes. It gives you a quick privacy snapshot before the longer legal wording begins.
Each label uses direct wording so you can move from scope to contacts, checks and questions without decoding legal jargon. The goal is clarity, not hidden small print.
JazzCash, Easypaisa, SadaPay and Raast appear as context chips because wallet references can carry personal data. Their placement shows exactly where payment records meet privacy handling.
The contact cards separate data copies, wallet record checks and security access issues. That separation helps you send the right privacy request with fewer delays and fewer extra details.
Retention cues explain why some records stay after an account action. They also show that older data may be removed, masked or separated when active use no longer needs it.
The questions section answers practical privacy concerns in direct language. It focuses on account data, wallet references, cookies, requests and regional access rather than broad platform claims.