LEGAL REFERENCE

Privacy Policy for your xm360 account

xm360 puts your account data, login records and Pakistan payment references into one clear Privacy Policy before you open your account. We explain what we collect, why it...

Account data usePakistan privacy contextJazzCash and Easypaisa referencesSecurity checks explained
Explore Lobby Read FAQ
xm360 Privacy Policy for your xm360 account

How we handle your account data

This Privacy Policy explains how xm360 handles data connected with your account in supported regions of Pakistan, where local law permits access. We collect the details needed to create and protect your account, process wallet references, manage verification checks, answer support requests, and keep service records accurate. When you use JazzCash, Easypaisa, SadaPay or Raast, we may store reference numbers, status markers,

timestamps and matching account details, not your full wallet PIN. We also record device, session and security signals so we can detect unusual access and help you recover your account. We keep data only for operational, legal, security and dispute-handling purposes, then reduce or remove it when retention is no longer needed.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY CONTACT

How to reach us about privacy

If you have a privacy question, contact us through the same account channels you use with xm360. Keeping the request inside your account helps us match the question to the right record while reducing extra data sharing.

Team online

Email privacy request

Send us the email linked in the footer and include your account name, registered mobile number, and the privacy question. We use those details only to locate the case and reply.

Chat from your account

Open chat from your account when you need quick clarification about collected data, payment references, or login records. Chat agents can raise a privacy ticket without asking for your full wallet PIN.

Account ticket trail

Use an account ticket for changes such as access correction or data removal requests. Tickets keep messages, dates and replies in one place so your privacy case stays traceable.

POLICY CARE

How we keep this policy accurate

Our Privacy Policy is written from our operating flow, not copied from a template. We check it against the data we actually collect across account access, wallet references...

Version date control

We attach a current date to policy changes so you can see when the wording last changed. Older wording is...

Payment field checks

We compare the policy against JazzCash, Easypaisa, SadaPay and Raast flows to confirm the wording matches stored references, transaction status...

Security wording checks

Our security team checks sections on login records, device signals and suspicious access alerts. That keeps the policy aligned with...

Support feedback loop

Privacy questions raised through chat, email and account tickets help us improve wording. When a recurring question appears, we clarify...

Pakistan wording

We write for Pakistani English and supported regions, with references to local payment rails and account verification steps that fit...

Plain language checks

Before publishing, we remove legal clutter where possible and keep the text readable. The aim is that you understand data...

How this page stays consistent

The Privacy Policy connects with other legal pages without repeating every clause. Each page has its own role, while this page stays focused on data collection, storage, sharing...

Terms page link
Our Terms page covers account rules, while this Privacy Policy explains the data used to apply those rules, including verification records, account status and security flags.
Cookie notice link
The Cookie notice deals with browser storage and similar tools. This page explains how those signals may connect with your session, device and account safety records.
Security page link
Security content explains account protection steps. This Privacy Policy adds what data supports those steps, such as login attempts, device changes and alerts from unusual access.
Payment help link
Payment help explains transaction steps. This policy explains the privacy side, including wallet reference numbers, confirmation status, account matching and records needed for dispute checks.
Promotion rules link
Promotion rules explain offer terms. This policy explains any account data used to check eligibility, prevent duplicate entries and record communication preferences connected with offers.
Contact page link
The Contact page shows how to reach us. This policy explains how we store support messages, attachments and identity checks when your request involves account data.
Access page link
Account access content explains login steps. This Privacy Policy explains the records behind access checks, including device signals, session timestamps and recovery request handling.
VISIBLE CUES

Privacy cues you can see

We designed this page so you can scan the privacy essentials without leaving the flow. Clear labels, short sections and visible contact routes help you understand what happens...

Current date marker A visible date marker tells you when the policy was...
Data category blocks We group account details, payment references, device signals and support...
Pakistan rail labels JazzCash, Easypaisa, SadaPay and Raast appear as context labels because...
Contact strip The privacy contact strip points you toward email, chat and...
Choice language Where choices exist, we explain them in direct language, including...
Short answer layout The question section uses direct answers for common privacy concerns...

Privacy Policy questions we answer

We collect account details, contact data, verification records, device signals, session activity and payment references. This helps us create your account, protect access, process requests and keep records accurate.

No. For JazzCash, Easypaisa, SadaPay and Raast, we may store reference numbers, confirmation status and timestamps. We do not ask for or store your full wallet PIN.

Device and login records help us spot unusual access, protect your account, support recovery requests and investigate disputes. These records can include timestamps, browser type, IP signals and session status.

Yes. Contact us through account chat, email or a ticket and tell us what needs correction. We may ask for verification before changing data linked to security or payment records.

You can ask us to erase data linked to your account. Some records may stay for legal, security, dispute or accounting reasons, and we will explain the response in your case.

We share only what is needed to process or confirm payment activity, resolve disputes, meet legal duties and protect accounts. Payment partners may receive reference details, status data and matching account fields.