Privacy Policy for your ss98 account
ss98 keeps your account data, session records and transaction references tied to clear purposes: access, security checks, wallet reconciliation and support. Read this Privacy Policy before you open...
How we handle account data
Our Privacy Policy is written for ss98 account activity in Pakistan and supported regions where local law permits. We collect only the details needed to create and protect your account, process wallet requests, confirm device sessions, respond to support messages and meet record keeping duties that apply to our service. This may include your name, contact number, login events, payment reference codes,
balance movements, IP data and documents requested for verification. We do not sell your personal data. We share it only with service partners who help run access, fraud checks, payment reconciliation or customer care, and we require those partners to use it for the agreed task. You can ask us to correct stored details or explain how your data is held.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ask us about privacy
Privacy questions need a clear route, not a maze. Use the account help area, email contact or live chat to ask about stored data, correction requests, verification records or security concerns. We may ask for account proof before discussing personal details, because that keeps your privacy request separate from ordinary lobby chat.
Account help
Open the help area after login and choose the privacy subject. We can link your request to the correct account record without asking you to repeat private details in multiple messages.
Email contact
Send privacy questions by email if you need a written reply. Include your registered contact number, but leave out passwords, card images or unrelated documents until we ask securely.
Live chat
Use chat for quick privacy routing, such as finding the correct request form or checking whether a document is still needed. Sensitive changes move to a verified channel.
How we keep this page accurate
We maintain this page as a live policy document for ss98, not as a generic template. The wording is checked against how our account, wallet, support and verification systems actually work. When...
Plain wording
We explain data use in direct language so you can see what is collected, where it is used and which choices you may raise through support.
Update trail
When a material change is made, the page date changes and the affected clause is rewritten, so older wording is not left beside new account processes.
Local context
The policy names Pakistan payment rails where references may appear, including JazzCash, Easypaisa, SadaPay and Raast, without mixing in rails from other markets.
Access controls
Account, wallet and document areas are separated by permission level, so support staff only see the data needed to handle the request in front of them.
Data minimisation
We ask for documents only when needed for account checks, wallet reconciliation or security questions, and we avoid collecting extra files that do not support that purpose.
Partner limits
Service partners receive data only for tasks they perform for ss98, such as hosting, verification, payment matching or support tooling, under limits tied to that task.
Aligned wording across legal pages
Your privacy rights should not change from one ss98 legal page to another. We keep this Privacy Policy aligned with related terms, cookie wording, account rules and security...
| Cookie Policy | Cookie wording matches this Privacy Policy by separating essential session tools from analytics tags, so you can understand browser data without reading conflicting descriptions. |
|---|---|
| Terms page | Our terms describe account duties, while this policy explains data handling behind those duties, including identity checks, wallet records and support request history. |
| Security wording | Security pages and privacy clauses use the same account protection language, covering login checks, device signals and alerts without adding separate promises elsewhere. |
| Account rules | Account rules explain what you must keep accurate; this policy explains how we store, correct and use those details after you provide them. |
| Wallet records | Wallet wording stays consistent by treating JazzCash, Easypaisa, SadaPay and Raast references as transaction records used for matching, checks and support. |
| Support page | Support contact text points back to the same privacy routes listed here, so correction requests and data questions are not split across unclear inboxes. |
| Regional wording | Where access depends on supported regions, related legal pages use the same local-law phrasing, keeping account access and privacy handling in one frame. |
Privacy cues you can see
This page is built so the important privacy points are visible before you open an account. We place purpose labels, contact routes, update cues and account-data...
Date stamp
A visible date helps you see when the Privacy Policy was last changed, so you can decide whether to reread clauses after a process update.
Purpose labels
Short labels group data by purpose, such as account access, security checks, wallet matching and support, making each privacy clause easier to scan.
Local examples
Pakistan examples appear where they matter, including payment reference handling for JazzCash, Easypaisa, SadaPay and Raast, without turning the policy into a sales page.
Request route
Contact options sit beside privacy rights language, so you can move from reading the policy to asking for correction or access help without searching.
Security language
Security clauses use practical terms like login events, device checks and verification files, so you can connect the wording to real account activity.
Mobile layout
Privacy sections stay readable on small screens, with short paragraphs and clear item blocks, so you can check account-data terms before joining.