Account Terms
Account conditions explain access and usage arrangements; this Privacy Policy explains how personal data connected with those arrangements is collected, used, secured and retained.
LEGAL REFERENCE
Privacy Policy For Your salot888 Account
This Privacy Policy explains how salot888 handles personal data when you open, access or maintain an account from Pakistan. We describe the details we collect, why we use...
Clear data purposesAccount securityPakistan support
How We Handle Personal Data
We collect details you provide when creating an account, contacting support or requesting an account action, including your name, contact details, date of birth where required, login credentials and identity material requested for verification. We also record technical details such as device type, browser, IP address, access time and security events. Transaction records may include JazzCash, Easypaisa, SadaPay, NayaPay or Raast references,
but we do not receive your full wallet password or private authentication code. We use this data to operate accounts, confirm requests, protect the service, meet applicable legal duties and resolve disputes. Where local law permits, data may be processed by vetted service providers acting on our instructions. We retain records only for as long as needed for these purposes, legal obligations,
fraud prevention and account support. You may contact us to request access, correction or deletion where applicable.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA SAFEGUARDS
Controls Behind This Policy
We wrote this policy around the account events that actually create data: registration, sign-in, wallet activity, verification, support conversations and withdrawal handling. Access to sensitive records is restricted by role, while security...
Purpose Limitation
We connect each data field to a stated operational, security, legal or support purpose. If a detail is no longer needed for that purpose, our retention process considers its removal or anonymisation.
Access Controls
Account and transaction records are available only to authorised personnel whose work requires them. Permission changes and unusual access patterns can be checked through internal security records.
Payment References
JazzCash, Easypaisa, SadaPay, NayaPay and Raast activity is matched using transaction references and status details. We do not ask you to share wallet passwords or private codes with us.
Verification Checks
When identity confirmation is needed for an account action, we compare submitted material with existing account details and the request context. This helps reduce mistaken or unauthorised changes.
Security Events
We may record device, browser, IP and session signals to identify suspicious access, protect sign-in flows and investigate disputes. These records are handled for security rather than public display.
Policy Updates
If our data practices change, we will update this page and show the revised date or notice where appropriate. You should check the policy before continuing to use your account.
CONSISTENT TERMS
How This Policy Relates Elsewhere
Privacy commitments should remain understandable wherever you encounter our account services. This section separates data handling from other legal subjects, so you can see which questions belong here and which require another...
Payment Records
Transaction records are part of our data handling because they identify account activity. This page covers their privacy treatment, not wallet provider rules or processing times.
Security Notices
A security alert may describe an immediate account event, while this policy explains the wider categories of technical and account data used to protect access.
Support Requests
Support conversations can contain personal data when you ask for help. We use the details needed to resolve your request and restrict access to the relevant support staff.
Regional Access
Where local law permits access, regional requirements may change how requests are verified, fulfilled or retained. Our team will explain the applicable process for your location.
Policy Version
The page version and update date help you identify which wording applied when you used the service or submitted a privacy request.
Your Choices
Depending on applicable law, you may ask for access, correction, deletion or processing clarification. We may need account verification before responding.
PAGE FEATURES
What Makes This Policy Easy To Use
We have arranged this privacy page around practical questions rather than abstract legal language. You can move from the policy scope to contact routes, operational safeguards, related terms...
Plain Sections
The page divides collection, use, retention, security and rights into...
Local Context
References to Pakistan and local wallet records show how the...
Direct Requests
The contact section gives you practical routes for access, correction...
Security Focus
Device signals, session records, role-based access and verification checks are...
Version Awareness
Policy update wording helps you recognise when our processing explanation...
Question Support
The final question set addresses common concerns about collection, sharing...
Questions About Your Personal Data
We may collect registration details, contact data, login records, device and session signals, support messages, payment references and verification material requested for a specific account action or legal requirement.
Verification can help confirm account ownership, protect withdrawals or investigate unusual activity. We request only material relevant to the action, and you should use the secure route provided rather than chat.
No. We may receive a transaction reference, status or account-related payment detail from supported rails, but you should never send us a JazzCash, Easypaisa, SadaPay, NayaPay or Raast secret code.
You may request deletion where applicable law allows it. Some records may need to remain for legal duties, dispute handling, security investigations or financial recordkeeping, and we will explain the outcome.
We may use service providers for hosting, security, verification, communications or payment processing. They receive data needed for their assigned task and are expected to handle it under our instructions.
Retention depends on the record type, its purpose, legal duties, security needs and unresolved disputes. When those needs end, we assess deletion, restriction or anonymisation under our internal process.
Contact the signed-in account desk or published privacy route with the detail that needs correction. We may verify ownership before updating the record, especially where the change affects access or withdrawals.