Your Privacy Policy at s66
s66 puts this Privacy Policy close to the account flow so you can see how we collect, use and protect your details before you open your account. It...
How We Handle Your Account Data
We collect only the data needed to run your s66 account, protect access and process activity where local law permits. That can include your name, mobile number, login records, device type, location signals, transaction references and chat messages you send to us. When you use JazzCash, Easypaisa, SadaPay or Raast, we keep payment reference data so we can match credits, verify withdrawals
and answer account questions. We do not sell your personal data. We share limited details only with service partners that help with security, payment routing, identity checks, hosting, analytics or customer care. We keep records for as long as needed for account safety, legal duties and dispute handling, then remove or anonymise them when they are no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths for You
Privacy questions need clear routes, not hidden forms. If you want to correct account details, ask how a payout record is stored or raise a concern about device access, contact us through the same support paths linked from your s66 account area.
Account chat
Use in-account chat when you are logged in and need help tied to your profile. We can see the account reference, reduce repeated identity questions and keep the privacy request attached to the right case.
Email privacy desk
Send privacy requests by email when you need a written trail. Include your s66 username, Pakistan mobile number and the issue type, but do not send card images or passwords in the message.
Payment query route
For JazzCash, Easypaisa, SadaPay or Raast privacy questions, share the transaction reference only. Our team checks the matching record without asking for wallet PINs or private banking codes.
How We Keep This Policy Current
This policy is written from our operating process, not copied from a generic template. We check it when we change account fields, payment handling, support tools or fraud...
Operator written
The wording reflects how s66 handles account creation, login checks, wallet references and support records. We connect each policy promise...
Local payment context
Pakistan wallet and bank rails create transaction references that must be stored carefully. Our policy explains why JazzCash, Easypaisa, SadaPay...
Access controls
Support staff see only the details needed for their task. Sensitive account actions require extra checks, and internal access is...
Retention checks
We separate active account records from older case files. Data kept for disputes, security checks or legal duties is not...
Change tracking
When privacy wording changes, we keep the update tied to the operational change behind it. That helps you understand whether...
Plain language
We avoid legal fog where a direct answer works better. The policy names the data category, the reason we use...
One Privacy Standard Across Legal Pages
Your account should not face different privacy meanings across separate legal pages. We align this Privacy Policy with our terms, cookie wording and support processes so the same...
| Terms alignment | Our terms explain account rules, while this policy explains the data behind those rules. Where an account action needs verification, both pages point to the same basic handling standard. |
|---|---|
| Cookie alignment | Cookie wording covers browser storage and session tools. This Privacy Policy connects those signals to account security, fraud checks and your ability to stay logged in safely. |
| Support alignment | Support scripts follow the same data boundaries stated here. You should not be asked for passwords, wallet PINs or unrelated identity material during a normal privacy request. |
| Payment alignment | Wallet and Raast references appear in finance records, not public account areas. The policy explains that link so JazzCash or Easypaisa queries can be handled without exposing private codes. |
| Security alignment | Login alerts, device checks and session controls all rely on data described here. We use those signals to protect access, not to create unnecessary profile detail. |
| Correction alignment | If your mobile number or account detail is wrong, the correction path follows this policy. We verify the request first so another person cannot alter your profile. |
| Deletion alignment | Removal requests are handled against security, dispute and legal needs. Some records may need to remain for a period, but we restrict their use once the account issue is closed. |
Policy Layout You Can Scan Fast
We design the privacy page so you can find the point that matters before opening an account or sending a support request. The layout highlights data...
Data category blocks
Account, device, payment reference and support data are separated into clear blocks. That makes it easier to see which detail is collected and why it appears in your s66 record.
Purpose labels
Each data use is tied to a purpose such as access protection, payout verification, support handling or legal compliance. We avoid vague wording when a simple reason can be named.
Sharing limits
Partner sharing is described by service role, not hidden behind broad phrases. Payment processors, hosting tools and fraud controls receive only the data needed for their assigned task.
Choice prompts
Where you can ask for correction, access or removal, the page points to the relevant contact path. We also explain when security or legal records may limit a request.
Pakistan context
The page names JazzCash, Easypaisa, SadaPay and Raast because those rails create local references. You can understand how wallet activity connects with s66 account records.
Update marker
Policy changes are kept visible near the page content. When we adjust wording after a tool or process change, you can see that the page has been refreshed.