Privacy Policy for your sx111 account
sx111 puts privacy terms beside account access, so you can see what data we collect before you join. Open your account after reading how we handle identity checks...
How we treat your account data
Our Privacy Policy describes the data we need to create and protect your sx111 account, including identity checks, login records, device signals and transaction references tied to supported regions in Pakistan. We collect only what helps us run access, verify requests, prevent account misuse and meet legal duties where local law permits. Payment names such as JazzCash, Easypaisa, SadaPay and Raast appear
here as context because those rails create receipts, timestamps and reference numbers. We keep privacy wording separate from promotional pages, so you can read our data practices before you join, update your profile or ask us to remove eligible records. If a rule changes, we amend this page and keep an internal record so your request can be checked against the policy
that applied at the time.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach us about privacy requests
Privacy requests work better when they arrive through a channel we can match to your sx111 account. We may ask for a short verification step before sharing, correcting or removing eligible data. That check protects your profile from unauthorised changes while keeping the request tied to the Privacy Policy you are reading.
Logged-in help drawer
Send a privacy request from the help drawer after logging in. We attach your account ID, current email and device marker so the privacy team can answer without asking you to expose extra data.
Email privacy route
Use the privacy email route when you cannot access your account. Include your registered phone number, last login date and request type, then wait for verification before we discuss stored account data.
Transaction query link
For JazzCash, Easypaisa, SadaPay or Raast references, share only the transaction ID shown on your receipt. We use it to locate records without asking for wallet PINs or banking secrets.
How our policy stays accurate
We maintain this Privacy Policy as an operating document, not a generic legal page. The wording reflects account creation, login security, local transaction references and support checks used...
Named data categories
We separate identity data, device signals, login records, support chats and transaction references so you can understand why each category...
Access verification
Before we answer account-specific privacy requests, we match your request to email, phone or session signals already held on the...
Local rails context
JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction records. We store the receipt details needed for reconciliation, not...
Retention checks
Records are kept for operational, security and legal reasons, then assessed for removal when those reasons no longer apply. Your...
Policy update markers
When wording changes, we update the date on the page and record what changed internally. This helps us answer requests...
Staff access rules
Only authorised sx111 staff can handle privacy tickets or account records needed for a case. Access is logged, limited by...
Consistent privacy wording across sx111
Your privacy rights should not change from one sx111 legal page to another. We keep this page aligned with account terms, cookie wording, verification language and support scripts...
Policy cues you can see
The Privacy Policy page is built so you can scan the parts that affect your account before you proceed. We surface update dates, data categories, request channels and...