How x44 Handles Your Data
x44 gives you one Privacy Policy for account data, device records, wallet checks and support chats in supported regions of Pakistan. Before you open an account, read how...
Our Privacy Policy Scope
This Privacy Policy explains how x44 handles data when you access our site, open an account, verify your profile, contact support or use wallet rails where local law permits. We collect only the data needed to run your account flow, keep access secure, process wallet requests, answer privacy questions and meet record keeping duties that apply to supported regions. Some checks may
involve device signals, login history, payment reference IDs and support messages, but we keep each use tied to a clear purpose. We also explain how you can ask for access, correction or deletion where those rights apply. When the policy changes, we update this page rather than hiding privacy changes inside general site copy.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Routes For Privacy Requests
Privacy questions need a clear path, not a maze. We separate account help from privacy requests so your message reaches the team that can check identity, locate the right records and respond without exposing data through the wrong channel.
Privacy email
Email our privacy desk with your registered phone number, x44 username and a short request. We use that detail only to locate your account record and reply through a channel linked to you.
Live chat handoff
If you start in chat, our agents can move your privacy request into a secure queue. We avoid asking for wallet PINs, full CNIC images or extra screenshots that are not needed.
Account ticket
Inside your account, a privacy ticket lets us match your request with login history and past support contact. That reduces back and forth while keeping the answer tied to your verified profile.
How We Keep Policy Claims Clear
We write this Privacy Policy from our own operating process. The wording is checked against account creation, wallet handling, cookie tools and support records so the page reflects how x44 actually handles...
Account data mapping
We map each account field to a purpose, such as login access, wallet checks or support replies. If a field no longer serves a clear need, we assess whether it should remain in active records.
Wallet reference handling
JazzCash, Easypaisa, SadaPay and Raast references may be stored with account activity to confirm requests and resolve disputes. We do not ask you to share wallet passwords or private app codes.
Cookie purpose labels
Our cookie labels separate required site functions from analytics and preference tools. That helps you understand why a browser tag exists before you continue using x44 on your chosen device.
Support access controls
Support staff see the account fields needed for your case, not every internal record. Privacy requests are escalated when correction, deletion or access rights need a closer identity check.
Change tracking
When privacy wording changes, we keep an internal record of what changed and why. This helps our team answer questions about older wording without relying on memory or informal chat.
Region wording
We use supported regions and where local law permits when access is discussed. That phrasing keeps privacy language tied to local availability without making broad claims about every location.
Consistency Across x44 Policy Pages
Your privacy rights should not change just because you move between legal pages. We align this page with related x44 policy pages so account data, cookies, security checks...
Privacy Layout You Can Read
We design the policy page so you can see the parts that matter before contacting us. The layout separates collection, use, sharing, storage, cookies and your...
Plain section labels
Each privacy section uses direct labels, so you can move from account data to cookies or support records without decoding legal phrasing. Short labels also help when reading on a phone.
Request path blocks
Contact routes are placed near rights wording, not hidden at the end. That way you can move from reading about access or correction to sending a request with fewer steps.
Local context chips
Where wallet data is discussed, we name Pakistan rails such as JazzCash, Easypaisa, SadaPay and Raast. The policy then links privacy wording to records you may recognise.
Cookie choice area
Cookie wording points you toward browser and site controls that affect tracking and preferences. Required security cookies are separated from tools used for measurement or saved settings.
Update stamp
The policy layout keeps change timing close to the main legal text. If we adjust wording, the date marker helps you know whether you are reading the current version.
Short rights summary
Rights wording is summarised before deeper legal detail, so you can see access, correction and deletion routes quickly. We still keep the full explanation available on the same page.