LEGAL REFERENCE

Privacy Policy for your x00 account

x00 keeps your privacy terms clear before you open an account, verify access, or use supported Pakistan payment rails. This page explains what we collect, why we need...

Account dataPayment recordsSecurity checksSupport requests
Explore lobby Read FAQ
x00 Privacy Policy for your x00 account

How we handle your personal data

Our Privacy Policy applies when you use x00 in supported regions where local law permits. We collect only the account, device, security, support, and transaction details needed to run your account, protect access, process requests, and meet record duties. For Pakistan payment flows, we may receive reference numbers, sender names, wallet identifiers, bank routing fields, and time stamps linked to JazzCash, Easypaisa,

SadaPay, or Raast activity. We do not sell your personal data. We share it only with service providers that help operate account access, fraud checks, payment handling, hosting, analytics, and customer support under controlled access rules.

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

CONTACT ROUTES

Privacy questions reach our support team

If you want to ask about your privacy rights, contact details, verification records, or a correction request, start with our support team...

Account inbox Send privacy questions from the inbox inside your...
Live chat handoff Our chat team can collect the first details...
Email contact If you cannot reach your account, email support...
POLICY CHECKS

Signals behind our privacy wording

We write this Privacy Policy from how x00 actually operates, not from generic legal copy. Each statement is tied to account creation, login protection, payment matching, support handling, record retention, or security...

Operational ownership

Privacy wording is checked against the same account flows you use, including login alerts, profile edits, payment matching, withdrawal verification, and support ticket handling.

Local payment context

We name JazzCash, Easypaisa, SadaPay, and Raast because privacy questions often depend on reference numbers, transfer tags, wallet names, and matching records.

Access controls

Internal access is separated by work need, so support, payments, and risk checks do not all see the same account fields by default.

Retention checks

We keep records only for account service, legal, security, and dispute reasons, then apply deletion or masking when those reasons no longer apply.

Device security

Device and session data help us spot account takeover attempts, unusual location changes, repeated failed logins, and access patterns that may need extra checks.

Plain wording

We aim to explain privacy choices in clear Pakistani English, with direct examples from account use rather than abstract legal language alone.

How this policy stays consistent

Your privacy rights should not change because you move between pages on x00. We align this Privacy Policy with our account terms, cookie wording, promotion rules, and support...

Account terms
When account rules mention verification, this Privacy Policy explains the data behind that step, including identity checks, contact confirmation, and activity records.
Cookie wording
Cookie choices connect with privacy rights, so we keep tracking explanations linked to analytics, session protection, preference storage, and fraud prevention.
Payment help
Payment support may discuss receipts or transfer references, while this Privacy Policy explains how those records are stored, used, shared, and retained.
Security messages
If we ask for extra login confirmation, the privacy reason is account protection, unusual activity detection, and safer handling of sensitive profile changes.
Support scripts
Support responses follow privacy rules by asking only for needed details and avoiding repeated requests when account records already confirm the issue.
Promo records
When promotions create account entries, this policy explains how eligibility checks, timestamps, and reward records are tied to your profile.
Regional access
Where access depends on supported regions, privacy handling still follows the same account, security, retention, and request principles described here.
LAYOUT CUES

Policy layout signals you can scan

We design the Privacy Policy page so you can find practical answers without reading unrelated platform copy. The layout separates collection, use, sharing, storage, security, and contact routes...

Clear collection blocks Each data category is separated so you can see whether...
Purpose labels We pair each data type with its purpose, so a...
Sharing boundaries The page explains when service providers may handle data for...
Retention markers Retention wording tells you why certain records stay for service...
Rights requests Contact steps are written around real requests, such as access...
Security language Security sections explain encryption, restricted staff access, monitoring, and verification...

Privacy Policy questions from x00

We collect account details, contact fields, verification records, device data, session logs, payment references, support messages, and settings needed to operate your x00 account and protect access.

Payment references help us match JazzCash, Easypaisa, SadaPay, and Raast activity to your account, resolve delays, check disputes, and maintain records required for security and service.

No. We do not sell your personal data. We share it only with providers that help run hosting, payments, analytics, security checks, communication tools, and support.

Yes. Contact support from your account inbox or registered email. We will verify that the request comes from you before sharing account-linked personal records.

We use session monitoring, restricted staff access, encryption, login checks, and activity flags to reduce unauthorised access and protect sensitive account and payment records.

Retention depends on the record type. We keep data for account service, disputes, legal duties, tax records, fraud prevention, and security, then delete or mask it when appropriate.