Account terms
Where account terms discuss registration details, this policy explains the privacy side: what we collect, why we need it and how long it may remain in records.
888c sets out exactly how we collect, use, protect and retain your account data before you open an account. Your privacy rights, JazzCash and Easypaisa payment records, device...
This Privacy Policy applies when you access 888c, create an account, contact us, complete verification, use supported payment rails or manage your account settings. We collect only the data needed to run account access, security checks, payment reconciliation, support handling, fraud prevention and legal record keeping where local law permits. Pakistan payment names such as JazzCash, Easypaisa, SadaPay and Raast may appear
in transaction records because they help us match deposits, withdrawals and account ownership. We do not sell your personal data. We share limited data with service providers only when they help us secure accounts, process payments, host systems, respond to support requests or meet lawful obligations in supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you have a privacy request, contact us through the channel that matches the urgency and detail needed. We may ask for account identifiers before discussing personal data, because privacy replies should reach the right person only. Keep payment screenshots, phone numbers and account emails ready if your question involves JazzCash, Easypaisa, SadaPay or Raast records.
Write to [email protected] when you want access, correction or deletion of account data. Include the phone or email tied to your 888c account so we can match the request safely.
Start with chat if your privacy question is linked to a current login, payment receipt or verification prompt. Our support team can route the case without exposing sensitive details in the chat thread.
Use your account centre for basic profile changes before sending a formal privacy request. Updating your own mobile number or email first can shorten identity checks when we reply.
We treat the Privacy Policy as an operational document, not a loose promise. The wording is checked against how our account forms, verification tools, payment logs and support...
One internal privacy owner checks each update before it appears on 888c, making sure the wording matches our account forms...
Our policy mapping separates JazzCash, Easypaisa, SadaPay and Raast records from general account activity, so payment reconciliation data is described...
We explain device signals as security data, not personal profiling for unrelated use. Login location, browser type and session checks...
We write policy changes in clear Pakistani English so you can understand what data is collected, why it is needed...
Material privacy changes are dated internally before release, with the affected section identified. This helps support teams answer your questions...
Only authorised staff and service providers can reach personal data needed for their task. Access is logged, limited by role...
Our Privacy Policy sits beside our other legal pages and keeps the same account facts, support routes and payment context. That consistency matters because your data may be mentioned in several places...
Where account terms discuss registration details, this policy explains the privacy side: what we collect, why we need it and how long it may remain in records.
Cookie wording aligns with this policy by separating essential login cookies from analytics tools, so browser tracking is not mixed with payment or identity data.
Security language across 888c matches this policy by linking login alerts, device checks and unusual activity checks to account protection rather than unrelated data use.
Transaction wording stays consistent by naming JazzCash, Easypaisa, SadaPay and Raast as payment context, while this policy explains the personal data attached to receipts.
Support responses follow the same privacy boundaries, including identity checks before we discuss account data, payment references or verification outcomes with you.
If offers require account status checks, this policy explains the data handling behind eligibility, communication choices and account messages without changing the offer terms.
Retention wording is kept aligned across legal text, so payment, verification, chat and login records are not described with conflicting timelines or purposes.
Privacy is easier to judge when the account screen shows what is happening. We place policy links, consent prompts, security labels and help routes near the actions that...