Account terms
Our account terms explain access duties, while this Privacy Policy explains the data behind them. Both pages use the same approach to verification, account status and communication records.
LEGAL REFERENCE
Privacy Policy for your 1xx account
1xx keeps your account data, payment records and session details under one Privacy Policy written for Pakistan access where local law permits. Open your account knowing what we...
Account dataPayment recordsSecurity checksPakistan support
How we handle your personal data
Our Privacy Policy explains how 1xx collects the data you give us when you create an account, verify access, contact support or use payment rails available in supported regions. We process details such as name, contact data, device signals, session logs, payment references and security checks so your account can be opened, protected and serviced. Where local law permits, we also use
limited technical data to detect misuse, resolve disputes and keep transaction records accurate. We do not sell your personal data. When we share data with service providers, it is limited to what they need for identity checks, payment handling, fraud control, hosting or customer care.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Reach us about privacy requests
If you want to ask about stored data, account access records or a privacy correction, use a contact route tied to your 1xx account. We may ask for limited verification before answering, because privacy requests can expose sensitive records if handled through the wrong channel.
Team online
Privacy inbox
Write to our privacy team from the email linked to your 1xx account. We use that match to discuss access, correction or deletion steps without exposing your data to another person.
Live chat handoff
Start in chat when you are signed in, then ask for privacy help. Our agent records the request type and moves sensitive matters to a protected channel if documents are needed.
Payment data queries
For JazzCash, Easypaisa, SadaPay or Raast record questions, send the transaction reference and account email. We check the privacy impact before sharing any payment-linked response.
CARE SIGNALS
Privacy checks behind the page
We write this Privacy Policy from the way 1xx actually runs account access, payment matching and support handling. The page is checked when we change data flows, add service providers or adjust...
Account verification
Before we answer a privacy request, we compare the contact route with your account record. That keeps personal data from being released through a phone number or email we cannot match.
Payment reference care
JazzCash, Easypaisa, SadaPay and Raast records are treated as financial data. We store only the references needed to confirm status, investigate errors and meet retention duties.
Session log limits
We keep technical logs such as sign-in time, device type and IP signals for security checks. The logs help us detect unusual access without turning them into public profile data.
Provider access controls
When external service providers help with hosting, verification or support tools, we limit their access by role. They receive only the data required for the assigned privacy-safe task.
Policy change checks
When a privacy wording change is needed, we compare it with account, payment and support workflows. We keep older wording internally so we can trace what changed and why.
Pakistan language fit
We use clear Pakistani English for privacy terms, payment names and support steps. That helps you understand how local account activity is handled without legal wording becoming unclear.
PAGE CONSISTENCY
Same privacy care across pages
Your privacy rights should not change from one legal page to another. We align this Privacy Policy with account terms, cookie wording, payment help and security messages, so every page points to...
Cookie wording
Cookie language connects to this Privacy Policy by naming device data and session signals. We keep the split clear so browser settings and account data are not mixed together.
Payment help
Payment help pages may mention JazzCash, Easypaisa, SadaPay and Raast, but privacy wording controls how related records are stored, checked and shared for support purposes.
Security messages
Security notices explain protective steps such as sign-in checks. This Privacy Policy explains what data those checks may create, how long it may be needed and who can access it.
Support scripts
Support replies are written to avoid asking for extra personal data. If a request moves beyond basic help, our privacy process decides what proof is enough.
Promo board
If you check the promo board, we may record eligibility and interaction data. This page explains that handling without changing the privacy rights attached to your account.
Archive trail
When wording changes, we keep an internal archive of past policy text. That helps us answer dated privacy questions with the wording that applied at the time.
VISIBLE MARKERS
Privacy layout you can scan
We design the Privacy Policy page so you can find key privacy points quickly: data categories, reasons for use, sharing limits, retention, rights and contact steps. These visible...
Date marker
The policy date shows when this wording was last updated...
Data categories
We separate account data, payment references, device signals and support...
Use reasons
Each data category links back to a reason, such as...
Sharing limits
The sharing section explains when service providers may receive data...
Retention windows
Retention wording explains why some records must remain after account...
Rights route
The request route tells you how to ask for access...
Questions about the 1xx policy
We collect data you provide during account setup, verification, support contact and payment activity. This can include contact details, account identifiers, device signals, session logs and payment references linked to JazzCash, Easypaisa, SadaPay or Raast.
Payment references help us match your account with a transaction, resolve failed or delayed activity and answer support questions. We keep them separate from public profile details and use them only for operational and legal needs.
Yes. Contact us from the email or signed-in account route linked to your 1xx account. We verify the request first, then provide the data we can share under applicable law and security limits.
We use access controls, verification checks and limited staff permissions around account records. Technical logs help us detect unusual sign-ins, but they are handled as security data rather than public account content.
Yes, only when needed for tasks such as hosting, identity checks, payment processing, support tools or fraud control. Providers receive limited data for assigned work and must handle it under privacy and security duties.
We keep data for as long as needed for account service, payment queries, security checks, dispute handling and legal duties. When a record is no longer required, we delete it or reduce the personal detail.
Send the correction request through your account email or signed-in support route. Tell us which detail is wrong, and we will verify the account before updating records or explaining why a change cannot be made.