Privacy terms for your account
8 com sets out how we collect, use and protect the data linked to your account, lobby activity and payment checks in Pakistan. Read this Privacy Policy before...
How we handle privacy in Pakistan
This Privacy Policy explains the way 8 com handles personal data when you create an account, verify access, use our lobby and request account help from Pakistan, where local law permits. We collect only the details needed to run your account flow, check security, process payment references and keep service records accurate. Payment names such as JazzCash, Easypaisa, SadaPay and Raast may
appear in transaction checks, but we do not publish your account data on public pages. We may share limited records with verification, payment, hosting or safety partners when that is needed to operate the service or respond to lawful requests. You can ask us about access, correction or deletion, and we will assess each request against security, account history and legal record
needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach us about privacy requests
If you have a privacy question, send it through the account help area or the contact email shown on 8com.app. Include the email or mobile number linked to your account so we can match the request without asking for extra data.
Account help
Use the help area after login for questions about stored profile details, device sessions or payment reference records. We can confirm what is held and explain the next privacy step.
Email privacy desk
Email us when you need a written privacy request, correction query or deletion assessment. Keep screenshots limited to the issue so your message does not include extra private data.
Security handoff
If a privacy request involves unusual access or account takeover concern, our support team can move it into a security check before any data change is made.
How we keep wording accurate
Our Privacy Policy is written around the account journey we operate: joining, verification, lobby use, payments, withdrawals and support. We check the wording when a data flow changes, so the page reflects...
Service mapping
We map each data point to a service reason, such as account access, wallet matching, fraud checks or support handling, instead of placing broad wording without a clear purpose.
Pakistan context
The policy names Pakistan access and local payment references because your cash-in or withdrawal check may involve JazzCash, Easypaisa, SadaPay or Raast confirmation records.
Access records
Login times, device type and session signals help us protect accounts and trace support issues. We describe these records so you know why technical data may be kept.
Retention logic
We do not keep every record for the same period. Payment references, support tickets and security logs may need different retention windows based on account safety and legal needs.
Partner limits
When we work with hosting, verification or payment partners, we limit shared data to the task involved. The Privacy Policy explains that sharing is tied to operation, not resale.
Plain language
We avoid hiding privacy points behind legal shorthand. Each clause aims to show what we collect, why it matters and how you can contact us about your account data.
Consistency across our policy pages
This Privacy Policy sits beside our account terms and cookie wording. Each page has a separate role, but we keep the same account language, local payment naming and...
| Account terms | The account terms explain service rules, while this Privacy Policy explains data handling. When both pages mention verification, the wording should point to the same account checks. |
|---|---|
| Cookie wording | Cookie wording covers browser storage and measurement tags. This Privacy Policy connects those signals to privacy rights, retention and your account-level data choices. |
| Payment references | Payment pages may name JazzCash, Easypaisa, SadaPay and Raast for account funding. This Privacy Policy explains the related records, checks and limited partner sharing. |
| Support language | Support pages ask for account identifiers so we can help you. The Privacy Policy explains why we request them and how we avoid collecting unrelated personal details. |
| Security wording | Security messages may refer to device checks or login alerts. This Privacy Policy sets out how those signals are used for account protection and suspicious activity handling. |
| Regional wording | When access is described, we use supported regions and where local law permits. The same phrasing keeps privacy rights and service availability clear for Pakistan. |
| Change handling | If we update privacy wording, the date and affected clauses should make the change easy to spot. We avoid mixing unrelated service edits into privacy updates. |
Privacy layout cues you can scan
We design this page so you can locate privacy points quickly before opening an account. Section headings, short chips and contact cards separate collection, use, sharing, retention and...