LEGAL REFERENCE

How sas3 Handles Your Data

sas3 sets out this Privacy Policy so you know what account, wallet, device and lobby records we collect when you open your account where local law permits. Read...

Account data useWallet record contextDevice security logsPakistan privacy contact
sas3 How sas3 Handles Your Data

Our Privacy Policy Commitments

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY HELP

Contact Routes For Privacy Requests

If you want to ask about your sas3 data, start with the contact route that matches your need. We separate privacy requests...

Privacy inbox Use our privacy email route for access, correction...
Live chat handoff Chat can receive your first message and pass...
Account centre Your profile area lets you check basic account...
DATA CHECKS

How We Keep This Policy Accurate

We write this policy from the way sas3 actually handles account data, not as a generic statement. Each update is checked against our sign-in flow, wallet records, security...

Policy owner

A named internal owner keeps the Privacy Policy aligned with account forms, verification steps and support scripts, so the wording...

Local wording check

We use clear Pakistani English and name local rails only where they matter to privacy records, including JazzCash, Easypaisa, SadaPay...

Wallet record mapping

Our privacy wording is matched against ledger fields such as transaction status, reference number and time stamp, helping you see...

Security log controls

Sign-in alerts, device fingerprints and IP records are described because they help us protect account access and investigate unusual activity...

Retention calendar

We track retention by data category, such as account identity, wallet records, support chats and security logs, then remove or...

Provider limits

When service providers handle hosting, chat or payment routing, we restrict their role to assigned tasks and require safeguards for...

How Privacy Fits Other Pages

Our Privacy Policy connects with other sas3 legal pages, but it does not replace them. This section shows how each page stays in its lane, so you can...

Terms of UseThe terms explain account rules and service access. This Privacy Policy explains the personal data behind those actions, such as sign-in records, verification checks and wallet references.
Cookie noticeThe cookie page deals with browser storage and tracking choices. Here, we explain how those signals may connect with device security and account session records.
KYC noticeIdentity checks may involve documents, selfie checks or account matching. This Privacy Policy explains why those records are collected and how access is limited internally.
Security pageSecurity content explains tools such as passwords and device checks. The Privacy Policy explains the related logs we keep when protecting your sas3 account.
Wallet termsWallet terms cover transaction handling. This policy explains the personal data attached to JazzCash, Easypaisa, SadaPay or Raast records inside your account history.
Contact pageThe contact page helps you reach us. This policy explains what data we may keep from support messages, chat transcripts and email exchanges.
Account closure pageClosure steps explain how you ask to end account access. This policy explains which records may remain afterward for legal, security or dispute reasons.

Privacy Layout You Can Scan

We designed this Privacy Policy to be readable before you open an account and useful after you join. The layout breaks privacy points into visible blocks...

Data category cards

Each category explains what we collect, such as account details, wallet references, device signals or chat records, and why it may be needed for sas3 operations.

Wallet context chips

Short chips show where local rails connect with privacy records, including JazzCash, Easypaisa, SadaPay and Raast, without turning the policy into a wallet page.

Choice prompts

Where a privacy choice is available, we state what you can ask for and what identity checks may be needed before we act on your request.

Retention markers

Retention markers explain whether data is kept for account service, security, legal duties or dispute handling, so you understand why deletion may not be instant.

Contact routes

We keep privacy contact routes visible near the policy text, making it easier to ask about access, correction or deletion without searching across the site.

Change stamp

When we update the Privacy Policy, we mark the change area clearly so returning account holders can see what has shifted in our data handling.

Privacy Policy Questions Answered

We collect account details, contact data, sign-in records, device signals, wallet references and support messages. The exact data depends on what you use, what verification is required and which privacy choices you make.

Wallet records help match JazzCash, Easypaisa, SadaPay and Raast activity with your sas3 account ledger. We keep references, status updates and timestamps for reconciliation, security checks, dispute handling and legal record duties.

Yes. Send a privacy request through our stated contact route, and we will verify account ownership before responding. We may provide account data, wallet references and support records that apply to your request.

You can ask us to correct details that are outdated or inaccurate. We may request proof before changing identity, contact or wallet-linked fields, because corrections must protect your account and other records.

We share limited data with providers that help run hosting, security, chat, verification and payment routing. They may use your data only for assigned services connected with your sas3 account.

Retention depends on the data type and reason for keeping it. Account, wallet, support and security records may be retained for legal duties, fraud prevention, dispute checks or ongoing account service.