How 18xx protects your data
18xx keeps your account, wallet checks and lobby activity under one Privacy Policy, so you can see what we collect before you open an account. We explain how...
Our privacy position for Pakistan
Our Privacy Policy applies to the account details you give us, the security logs created when you access 18xx, and the transaction references linked to supported regions in Pakistan. We collect only what we need to run your account, check wallet activity, answer support requests and meet lawful record duties. When you use JazzCash, Easypaisa, SadaPay or Raast, we may receive reference
numbers, timestamps, sender labels and status messages rather than full banking files. We use those details to match your account action, protect access and handle queries. Access to personal data is limited to trained operational staff, and we keep records only for business, security and legal needs where local law permits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we maintain privacy accuracy
We write this Privacy Policy from our own account workflow, not from a template. The points below show how our team keeps privacy wording aligned with everyday handling...
Named data owners
Privacy tasks are assigned within our operations team, so requests do not float between unrelated queues. That structure helps us...
Access control
Staff access is separated by task, so support, wallet checks and security checks do not all expose the same personal...
Payment rail mapping
We map JazzCash, Easypaisa, SadaPay and Raast references to your account action without asking for extra wallet screenshots unless a...
Device record handling
Login device records help us spot account access issues and keep sessions stable. We connect those records to privacy requests...
Change tracking
Policy changes are checked by operations, support and security staff before publication. That process keeps the wording close to how...
Retention schedule
We keep account and transaction records for defined business or legal needs, then reduce or remove data when it no...
How this policy fits other pages
This Privacy Policy connects with our account terms, cookie wording and support rules. Each page has a different job, but the privacy meaning stays consistent across your 18xx...
Policy layout points you can see
We designed this page so privacy points are easy to scan before you create or manage an account. Each visible element points to a real handling...
Plain data categories
We separate account details, payment references, device records and support messages so you can understand each privacy category without reading one long mixed paragraph.
Local rail labels
JazzCash, Easypaisa, SadaPay and Raast are named because their reference formats differ. Clear labels help you see which privacy point applies to your transaction record.
Request path cards
Contact cards show where to ask for correction, access checks or deletion assessment. We also state when identity confirmation is needed before sharing personal records.
Security context
Privacy and security are kept together where they overlap. Login timestamps, device signals and session records are explained as account protection tools, not hidden extras.
Retention cues
Retention wording explains why some records stay for account, security or legal needs. We avoid vague storage language so you know the reason behind continued holding.
Update markers
When privacy wording changes, we keep the page aligned with support practice and wallet handling. You can check this page again before changing account settings.