Privacy Policy For 1234app
This Privacy Policy explains how we collect, use, protect and retain information connected with your 1234app account in Pakistan. We keep the policy focused on practical details, from...
How Our Privacy Duties Apply
We process account details, contact data, verification material, technical signals and activity records to operate 1234app, protect account access and meet legal duties in supported regions. Where local law permits access, Pakistani customers may use JazzCash, Easypaisa, SadaPay or Raast; related transaction references can be retained to reconcile balances, investigate disputes and confirm withdrawals. We do not ask for data unrelated to
these purposes. Access may depend on location, age requirements under applicable law and successful checks. Our service providers may process limited data for hosting, fraud screening, payment routing, customer support and security monitoring. We require them to handle data only for assigned purposes. This policy applies to the website, account area and related support channels, while a specific third-party service remains subject
to its own privacy terms.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact Us About Your Data
We want privacy questions to reach the right team without unnecessary sharing. Use the account support channel for access and correction requests, or contact us through the privacy route shown on 1234app. Tell us the email or phone linked to your account, describe the request clearly and avoid sending passwords or full payment credentials. We may verify ownership before making changes or releasing account-related details.
Account support
Ask about account records, login details or a correction through the signed-in support channel. We use account verification before discussing personal data, helping prevent a third party from receiving private account details.
Privacy request
Send a request about access, deletion, restriction or data use through our privacy contact route. Include enough detail for us to locate the record, but remove passwords, one-time codes and complete payment numbers.
Security concern
If you notice an unfamiliar login, message or account change, contact support promptly through the available channel. We can review access signals, protect the account and explain the next verification step.
Practical Signals Behind This Policy
Our privacy approach is shaped by the records needed to run a Pakistan-facing account service rather than by broad promises. We separate identity material from routine activity where...
Account identity
We may collect your name, contact details, date of birth, location signals and verification documents when required. These details help...
Device signals
Browser type, operating system, IP address, language and security events may be recorded when you connect. We use these signals...
Payment matching
For JazzCash, Easypaisa, SadaPay and Raast transactions, we may retain provider references, amount, status and timing. These records support reconciliation...
Access controls
Our team uses role-based permissions, authentication controls and monitored administrative access. Staff receive only the data needed for a task...
Retention logic
We keep records for as long as needed for account operation, dispute handling, security analysis, legal duties and financial reconciliation...
Policy updates
If our processing changes materially, we will update this page and identify the effective date. Continued account access after an...
How This Policy Relates Elsewhere
Privacy wording should remain consistent wherever we describe account handling. This page sets the central rules for collection, use, sharing, retention and your choices. Other policy pages may...
What This Policy Page Shows
We designed this page so the privacy details are easy to scan before you use your account. The layout separates policy scope, contact routes, practical safeguards...
Plain language
Key privacy duties are expressed in direct Pakistani English, with technical terms explained through account examples. This makes it easier to understand collection, storage, sharing and request procedures.
Scope markers
The opening policy section identifies the website, account area and support channels covered here. It also explains when regional law and supported-region checks can affect access.
Request routes
Dedicated contact cards distinguish ordinary account help, privacy requests and urgent security concerns. Choosing the right route can reduce delays and prevent unnecessary disclosure in a message.
Record examples
Examples include identity details, device signals, payment references and support history. They show the types of records involved without asking you to publish private credentials on the page.
Retention view
The page explains why some records remain after an account event, including legal duties, reconciliation and disputes. Retention is linked to purpose rather than an open-ended promise.
Update visibility
Material wording changes are handled through this page and its effective date. Checking the page periodically helps you see whether our processing explanation has changed.