Cookie page
Our cookie wording matches this privacy policy by naming session, security and analytics markers. It explains browser storage in more detail without changing our wider handling of account data.
LEGAL REFERENCE
How s88 handles your privacy
s88 gives you one clear privacy path for account records, verification checks, lobby activity and Pakistan payment receipts, so you know what we collect before you open your...
Pakistan data contextCookie choicesAccount recordsPayment receipt care
Privacy posture for Pakistan accounts
This privacy policy applies when you access s88 in supported regions, create an account, confirm your identity, use the lobby, contact support, or send payment receipts linked to JazzCash, Easypaisa, SadaPay or Raast. We collect only the data needed to run your account, protect access, process service requests and meet record duties where local law permits. We separate identity files from routine
activity logs where possible, restrict staff access by role, and remove data when it is no longer needed for account, security or legal reasons. If a law, bank request or security check requires a longer hold, we keep the record in a limited folder with access controls.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How we keep this policy accurate
Our privacy wording is maintained by the team that runs s88 account operations, not by a third party. We update the policy when data flows change, such as...
Operations owned
The same team that handles account verification, access recovery and local receipt checks confirms the wording. That keeps the policy...
Role-based access
Staff access to identity files, support tickets and payment receipt records is limited by job role. We log internal access...
Cookie mapping
Cookies are grouped by purpose, including session security, language settings, analytics and service tuning. The policy explains these groups so...
Verification separation
Identity images and account activity logs are handled as separate record sets where our systems allow it. That reduces unnecessary...
Pakistan fit
We mention JazzCash, Easypaisa, SadaPay and Raast because privacy questions often involve receipt records. Naming them helps you recognise what...
Change record
When policy wording changes, we keep an internal change record showing the reason, date and affected section. This helps our...
PAGE MATCH
Aligned privacy pages across s88
Privacy is connected to several s88 pages, so we keep the wording consistent across account, cookie, security and terms pages. This page explains personal data handling, while related pages explain narrower areas...
Terms page
The terms page explains account conditions, while this policy explains personal data handling. We avoid mixing those topics so you can separate service rules from privacy rights.
Security page
Security wording covers passwords, device checks and account recovery. This policy connects those controls to the data we collect when we protect your s88 account from unauthorised access.
KYC wording
Verification text appears where identity checks are requested, but this policy explains how those files are stored, who can access them and when removal may be possible.
Support records
Support pages explain response routes, while this policy explains how ticket content, attachments and chat transcripts are handled. We keep sensitive replies away from public channels.
Payment receipts
Cash-in and withdrawal pages may ask for receipt references. This policy explains how those references connect to JazzCash, Easypaisa, SadaPay and Raast account records.
Promo settings
Account preference pages let you manage service messages. This policy explains what contact details we use, why messages are sent and how preference changes are recorded.
Policy layout you can inspect
We designed this privacy page so you can scan the parts that affect your account before you join s88. The layout separates collection, use, sharing, storage...
Plain section names
Each section uses direct wording, such as account data, cookies and support records. That helps you find the privacy topic that matches your concern without reading unrelated service copy.
Short badges
The badges near the hero highlight privacy areas you are likely to check first. They point to data categories, not sales claims, so the page stays focused.
Request paths
Contact items show where to send access, correction and removal questions. We include the route because privacy requests need controlled handling and identity confirmation before changes are made.
Local labels
Pakistan labels appear where they affect privacy, such as receipt references and support context. We name them so your account records are easier to recognise in policy wording.
Storage clarity
Where retention matters, the policy explains why a record may be kept and when removal can be requested. We avoid vague storage language that leaves you unsure.
Action wording
The page uses practical verbs such as ask, correct, remove and contact. Those words show what you can do with your privacy rights while using s88.
Privacy questions from s88 account holders
We collect account contact details, login records, verification files, lobby activity needed for account history, support messages and payment receipt references. We use these records to operate your account and protect access.
Receipt references are linked to your s88 account so we can match cash-in or withdrawal requests. We store only the details needed for checking, support and record duties where local law permits.
Yes. Send the correction request through the privacy contact route with your account email and the field that needs changing. We may confirm identity before updating sensitive records.
We share limited data only when needed for service operation, security checks, payment processing, technical hosting or legal requests. Partners receive the minimum record set required for that specific purpose.
We keep records while your account is active and for limited periods after closure when required for security, payment checks or legal duties. Unneeded records are removed or restricted.
We use cookies for login sessions, account safety, language settings, analytics and service performance. Some are necessary for access, while others help us understand page behaviour and improve privacy controls.
Use the privacy desk and include your account email, request type and any receipt reference involved. We will confirm identity, check legal retention needs and then explain the action taken.