How x 17 Handles Your Data
x 17 gives you a clear Privacy Policy before you open your account, so you know what data we ask for, why we need it, and how it...
Privacy Policy Scope In Pakistan
Our Privacy Policy applies when you create or use an x 17 account in supported regions where local law permits. We collect the details needed to run your account, confirm access, process account requests, keep payment references aligned, and respond when you contact us. This can include your name, phone number, email, login records, device type, IP region, session activity, and transaction
references from supported Pakistani rails. We do not use this page to ask for extra data outside the account flow. We keep records only for operational, legal, safety and dispute-handling needs, then restrict or remove them according to our retention schedule.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Questions And Account Help
If you want to ask about your data, update account details, or raise a privacy concern, contact us from the account area or support chat. We may ask you to confirm access before discussing records, because privacy requests must be handled through the same identity checks that protect your account.
Account inbox
Use the message area inside your x 17 account for privacy requests tied to your profile. It keeps the conversation linked to your login and helps us confirm that the request came from you.
Live chat
Start a chat when you need quick direction on privacy choices, correction requests, or data access steps. Our team can route the case without asking you to repeat sensitive details in public channels.
Verification follow-up
For account data requests, we may send a follow-up prompt inside your account. This reduces impersonation risk and lets us respond only after access has been checked through our internal process.
How We Keep Privacy Accurate
We maintain this Privacy Policy as an operating document, not a generic legal page. When account screens, payment references, support forms, or device checks change, we check whether the policy still matches...
Account mapping
We compare policy wording with the account fields you actually complete, such as phone, email and profile details. If a field is removed or added, the privacy wording is checked against that change.
Payment reference checks
JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction context, not open-ended personal records. We check that our policy explains why those references are needed for account handling.
Device data wording
Login security can involve device type, browser, IP region and session timing. We describe these signals plainly so you understand how they help us detect unusual account access.
Retention schedule
We keep account records for operational, legal and dispute needs, then restrict or remove them when they are no longer required. The policy is checked against those internal retention rules.
Access control
Only assigned team roles can handle privacy requests or view account records needed for a case. We keep staff access narrow, recorded and connected to the reason for the request.
Pakistan language fit
We write privacy wording in clear Pakistani English, with local payment names and support paths you recognise. That helps you understand the policy before you share account details with us.
Consistency Across Our Policy Pages
Our Privacy Policy is written to stay consistent with related account pages, support terms and security messages. If another page asks you to share data, this page should...
| Account terms | Where account terms mention registration details, the Privacy Policy explains how those details are collected, checked and stored. Both pages should describe the same account flow without conflicting wording. |
|---|---|
| Cookie choices | Cookie wording should match this Privacy Policy when it refers to device signals, session activity and preference storage. That keeps browser data explanations aligned across the site. |
| Security prompts | When you see an account security prompt, the privacy wording should explain why login signals or confirmation steps may be used. We connect safety checks with clear data purposes. |
| Support scripts | Our support replies should reflect the same privacy positions as this page. If you ask about access, correction or retention, the answer should follow this policy rather than ad hoc wording. |
| Payment screens | Payment screens may show JazzCash, Easypaisa, SadaPay or Raast references. This policy explains that those references are used to match account activity and handle queries. |
| Update messages | When we change privacy wording, related account messages are checked for the same meaning. We aim to avoid one page saying more or less than another about your data. |
| Region wording | Access wording across x 17 should use supported regions and where local law permits. The Privacy Policy follows that same approach when describing availability and account handling. |
Visible Privacy Page Elements
This page is arranged so you can quickly see what data we collect, why we use it, how long we keep it, and how to contact...
Plain section headings
Each privacy section uses direct headings, so you can move from collection to retention and support without decoding legal phrasing. The structure is designed for quick reading on mobile screens.
Local context chips
Short chips mention Pakistan and supported payment references only where they help explain privacy handling. They are context markers, not extra requests for personal details.
Request pathways
Contact routes are placed near privacy explanations so you know where to ask about access, correction or account data handling. We keep the route tied to account verification.
Security language
Security-related wording is kept close to login and device data explanations. This helps you see why certain technical signals are collected when your account is accessed.
Retention cues
Retention wording explains why some records must be kept for account operations, legal needs or disputes. It also makes clear that records should not be kept without a reason.
Change clarity
When privacy wording changes, the page should make the updated meaning easy to follow. We focus on clear changes rather than dense wording that hides practical impact.