Terms wording
The Terms page covers account rules, while this policy covers personal data. We keep shared phrases consistent so account access and privacy duties do not conflict.
LEGAL REFERENCE
How We Protect Your Account Privacy
1xbad keeps your Pakistan account data, login checks and lobby activity under one clear Privacy Policy before you open your account. This page explains what we collect, why...
Account dataLogin checksPakistan privacySupport contact
Our Privacy Position for Pakistan
We collect the details needed to run your 1xbad account, confirm access, process account funding context and protect the lobby from misuse in supported regions. This can include your name, phone number, email address, device details, IP address, login time, transaction reference and support messages. Where local law permits, we also keep records linked to JazzCash, Easypaisa, SadaPay and Raast so we
can match your account activity with your funding or withdrawal request. We do not sell your personal data. We share limited data only with service partners who help us operate security checks, customer support, payment rail matching, fraud screening and technical hosting. We keep data for as long as needed for account operation, legal duties, dispute handling and security monitoring.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CHECK CYCLE
How We Keep Policy Text Current
Our Privacy Policy is maintained by the 1xbad team that handles account access, security checks and Pakistan support. We update wording when our data flow changes, when a payment rail adds a...
Data map upkeep
We map account fields to real screens, including registration, login, profile edits and withdrawal requests. That keeps the policy tied to what you actually see inside 1xbad.
Security wording
Login alerts, device fingerprints and IP checks are described in plain terms. We avoid vague phrasing so you know which privacy signals support account safety.
Payment rail checks
JazzCash, Easypaisa, SadaPay and Raast references are checked against our account flow. We explain them as matching records, not as public account details.
Support script checks
Privacy answers used by support are checked against this page. That reduces mixed messages when you ask about stored data, access logs or correction steps.
Retention logic
We explain why some records stay after account closure requests, such as dispute handling, fraud screening and legal duties. Retention is tied to function, not idle storage.
Change dates
When the Privacy Policy changes, we use dates and plain wording so you can spot what moved. Major changes are written for quick reading on mobile.
PAGE ALIGNMENT
Matching Privacy Terms Across Our Pages
Your privacy rights should not change because you read a different 1xbad page first. We keep account, security and cookie wording aligned across our legal pages, lobby notices and support replies. This...
Cookie wording
Cookie text explains browser storage, session tokens and preference settings. This policy links that data to account security and fraud checks in a broader privacy frame.
Security wording
Security notices mention device checks and unusual login alerts. Here, we explain how those checks create data records and why they support private account access.
Withdrawal wording
Withdrawal pages ask for matching account references. This policy explains why those references are stored, who can see them and how they support dispute handling.
Support wording
Support pages tell you how to reach us. This policy explains what happens to your message, account identifiers and any attachments after you submit them.
Regional wording
Access wording uses supported regions and local law permits language. The Privacy Policy follows the same approach when describing Pakistan account handling and data requests.
Promo wording
Promo board text may create account activity records. This policy explains the privacy side of those records without turning them into public profile details.
LAYOUT MARKERS
Privacy Layout You Can See
We built this page so privacy details are easy to scan before you open an account. The layout separates collection, use, sharing, retention and contact routes instead of...
Plain labels
Each policy block uses direct labels such as account data...
Short chips
Local chips show where Pakistan rails appear in privacy context...
Contact markers
Privacy contact routes sit near the policy details so you...
Retention cues
Storage periods are explained beside the reasons we keep records...
Security cues
Device and login checks are grouped with privacy wording, not...
Choice cues
Correction, access and deletion routes are written as actions you...
Privacy Questions Before You Join
We collect account details, contact data, login records, device signals, transaction references and support messages. We use them to run your account, confirm access and keep private records linked to the right person.
We mention local rails because transaction references may be stored with your account. Those records help us match funding or withdrawal activity, handle disputes and answer privacy requests tied to Pakistan account access.
No. We do not sell your personal data. We share limited records only with partners needed for hosting, security checks, support handling, payment rail matching and legal duties where local law permits.
Yes. Contact us from your registered details and explain what needs correction. We may run extra checks before changing phone numbers, email addresses or records tied to withdrawals and account access.
We keep records while your account is active and longer when needed for disputes, fraud screening, accounting records or legal duties. Storage periods depend on the record type and the reason it exists.
We assess the request, confirm account identity and remove data where we can. Some records may remain if needed for legal duties, security investigations, unpaid disputes or withdrawal records.