LEGAL REFERENCE

How 1xbe Handles Your Privacy

1xbe sets out this Privacy Policy so you can see what data we collect, why we need it, and how we protect it before you open your account...

Account data useDevice securityPakistan accessPayment records
1xbe How 1xbe Handles Your Privacy

Policy Posture for Pakistan Accounts

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

PRIVACY HELP

Contact Us About Privacy

If you want to ask about your data, correct account details or raise a privacy concern, contact us through the privacy paths...

Privacy email Send your privacy request through the contact address...
Live chat handoff Use live chat to reach support, then ask...
Account area request When you are logged in, your account area...
POLICY CHECKS

How We Keep This Policy Current

We treat this Privacy Policy as an operating document, not a decorative page. Our team checks it when account flows, security tools, payment references or support channels change...

Account flow mapping

We map each account step against the data it asks from you. If a field is added or removed in...

Payment reference control

JazzCash, Easypaisa, SadaPay and Raast references are handled as account records. We keep them tied to transaction matching, support checks...

Device security signals

We use device and session signals to help detect unusual access. The policy explains this because protecting your account often...

Support case logging

Messages you send to support can become case records. We keep those records so we can answer follow-up questions, track...

Retention checks

We keep records only for clear purposes such as account security, payment matching, legal duties and dispute handling. When those...

Plain language edits

When the policy changes, we write the update in direct Pakistani English. We avoid legal padding where simpler wording can...

Consistent Privacy Across Legal Pages

Our Privacy Policy connects with other legal pages, but it has a different job. It explains data handling, while related pages explain account rules, cookies or promotions. We...

Terms page link
Our Terms describe account rules, while this Privacy Policy explains data handling behind those rules. When account checks are mentioned in both places, we keep the wording aligned.
Cookie page link
Cookie wording covers browser storage and tracking choices. This Privacy Policy gives the broader context, including how session data supports account security and service reliability.
Promotion terms link
Promotion terms may require eligibility checks, but privacy wording explains what data supports those checks. We avoid mixing reward copy with privacy rights or retention duties.
Security wording link
Where security pages mention login checks, this policy explains the related data use. That keeps device signals, failed access attempts and account protection wording consistent.
Payment wording link
Wallet pages may show JazzCash, Easypaisa, SadaPay and Raast. This policy explains the privacy side: reference matching, record keeping and support checks linked to those rails.
Support wording link
Support pages tell you how to reach us. This policy explains how your messages, attachments and case history are stored, accessed and used to answer your request.
Update wording link
When any legal page changes in a way that affects data handling, we check this Privacy Policy too. That helps keep account, payment and support wording in sync.

Policy Layout You Can Scan

We designed this policy page so the privacy points are visible without making you search through unrelated copy. The layout separates collection, use, sharing, retention and...

Clear opening promise

The first section states the purpose of the Privacy Policy before any legal detail appears. You can quickly see that the page is about data collection, use and protection.

Local context chips

Short chips identify Pakistan-specific context such as JazzCash, Easypaisa, SadaPay and Raast. They show where local account activity may create records without turning the policy into wallet copy.

Request paths grouped

Privacy contact options sit together, so you can choose the route that fits your request. Each path explains what proof may be needed before account records are changed.

Security sections separated

Device signals, login checks and session records are explained as security topics. Keeping them separate helps you understand why those details matter for account protection.

Retention wording visible

Retention wording is placed near data-use explanations, not hidden at the end. You can see why records may be kept and when deletion or anonymisation may apply.

FAQ closeout

The questions section answers common privacy concerns in plain language. It gives quick answers on access, correction, sharing, payment references and how to contact us.

Privacy Policy Questions for You

We collect account details you provide, such as name, mobile number and login credentials, plus security records from your device and session. We use this data to create, protect and manage your account.

When you use JazzCash, Easypaisa, SadaPay or Raast, we keep transaction references needed to match wallet activity, answer support questions and handle disputes. We do not control those outside payment services.

Yes. Contact us through the account area or privacy contact path and explain what needs correction. We may ask for proof before making changes so another person cannot alter your records.

We share data only when needed for account operation, security checks, payment matching, support handling or legal duties. Any service provider we use must handle the data for the agreed purpose.

Retention depends on the record type and purpose. Security logs, payment references and support cases may be kept for dispute handling, fraud checks or legal duties, then deleted or anonymised when no longer needed.

Use the privacy contact option shown in your account area or ask live chat to route your request. Give enough detail for us to find the record, but avoid unnecessary attachments.