Collection
This page describes the categories of personal data we receive from you, your device, service partners and account activity when those records are needed for a stated purpose.
LEGAL REFERENCE
Privacy Policy For sart88 Accounts
This Privacy Policy explains how sart88 handles personal data when you open an account, contact our team or use our services from Pakistan or another supported region. We...
Clear data purposesAccount securityPakistan privacy contextContact choices
How We Handle Personal Data
We collect details you provide when creating or maintaining an account, including your name, contact details, date of birth, identity checks, login credentials and messages sent to support. Technical records may include device type, browser data, IP address, session events and security signals used to protect access. Payment records can include method, reference, amount, status and verification results for JazzCash, Easypaisa, SadaPay,
NayaPay or Raast, without storing payment credentials that we do not need. We use this data to provide account services, process requests, detect misuse, meet applicable legal duties and improve reliability. Where local law permits, we may share limited records with service providers, payment partners, auditors or public authorities when required. We apply access controls and retain records only for as long
as a stated purpose, legal duty or dispute requires.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA SAFEGUARDS
Practical Controls Behind This Policy
Privacy depends on everyday controls rather than broad promises. We limit staff access by role, record material account actions, separate payment references from login secrets and use security...
Access controls
Account records are available to authorised personnel according to their work role. We use permission boundaries so a support task...
Sign-in signals
We assess device, session and network signals to identify unusual access. These checks can prompt an extra confirmation and help...
Payment records
For JazzCash, Easypaisa, SadaPay, NayaPay and Raast, we retain operational references needed to match a request. Payment credentials remain with...
Withdrawal checks
A withdrawal may be checked against account ownership, transaction history and security signals. This process helps prevent misdirected funds and...
Retention rules
We keep records for the period needed to provide services, resolve disputes, meet legal duties and protect system integrity. When...
Policy changes
If our data practices change materially, we will update this page and show the revised date or a clear notice...
CONSISTENT STANDARDS
How This Policy Fits Account Handling
This page works alongside the account terms and security notices that apply to sart88 services. Its purpose is narrow: it explains personal data handling rather than setting out account conduct or transaction...
Use
We explain why data supports account access, security, payment matching, service messages, dispute handling and legal duties, while avoiding use that is unrelated to those purposes.
Sharing
Any sharing is limited to service providers, payment partners, professional advisers or authorities where their role or a legal requirement makes access necessary.
Choice
You can ask about your records, request correction or raise a concern through the available contact route. Some records may need to remain for legal or security reasons.
Security
Account permissions, sign-in checks, transaction matching and protected communications form part of our controls for reducing unauthorised access to personal data.
Retention
Retention depends on the purpose, account status, dispute position and applicable duty. We do not keep identifiable records indefinitely without a reason connected to those factors.
Regional access
Access and processing may differ by jurisdiction. Where local law permits, we apply this policy to supported regions and adapt requests to applicable local requirements.
PAGE FEATURES
What This Privacy Page Makes Clear
We have arranged this policy so the points most relevant to an account holder are visible without searching through dense legal wording. The page separates collection, use, safeguards...
Purpose labels
Each policy area connects a category of data with a...
Local context
References to Pakistan and local payment services show where regional...
Plain contact route
The support section identifies practical ways to ask about records...
Security focus
Device signals, permission controls and withdrawal checks are described as...
Retention view
The policy explains why some records may remain after a...
Change visibility
Material updates are tied to this page and its published...
Privacy Answers For Your Account
We may collect account details, contact records, identity check results, device and session signals, payment references, support messages and security events when those records are needed for service delivery or protection.
Identity details can help confirm account ownership, protect access, assess unusual transactions, process certain requests and meet applicable duties. The exact checks can vary by account activity and supported region.
We do not need to store payment credentials that remain with the relevant payment service. We may retain a method name, reference, amount, status and verification result to match an account transaction.
Yes. Contact the account desk or send a privacy request describing the record that needs correction. We may ask for reasonable proof that you control the relevant account before changing it.
Retention depends on the reason for collection, account status, legal duties, dispute needs and security requirements. When a record no longer serves a valid purpose, we delete or de-identify it.
We use role-based permissions, sign-in signals, transaction checks and protected communications. These measures can trigger extra confirmation when activity appears unusual and help reduce unauthorised account use.
This policy is intended for sart88 activity in Pakistan and other supported regions, where local law permits. Regional requirements may affect available services, data requests and the way records are retained.