How as8 Handles Your Data
as8 collects only the account, device and transaction details needed to open your access, protect your balance and process requests where local law permits. Read this Privacy Policy...
What This Privacy Policy Covers
This Privacy Policy explains how as8 collects, uses, shares and protects personal data when you access our brand home, create an account, verify your profile, contact support or request a withdrawal in supported regions of Pakistan. We may collect your name, mobile number, login details, device signals, payment references and messages you send to us. We use that data to operate your
account, secure sessions, check transaction status, respond to requests and meet record-keeping duties where local law permits. We do not sell your personal data. Limited details may be shared with payment processors, identity checks, security tools and service partners that help us run the account flow.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Policy Records Accurate
Our privacy wording is maintained from the same operational flow that handles sign-in, verification, payments and support. When a process changes, we check the policy text against the data fields collected on...
Field mapping
We map each account field to a purpose, such as login security, withdrawal verification or support handling. If a field is no longer needed, it is flagged for removal from active collection.
Payment trace control
JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction records, not public profile details. Access is limited to staff handling payments, disputes or account safety checks.
Device security signals
We use device, browser and IP signals to detect unusual access patterns. These signals help protect your account, but they are not used to publish personal activity outside as8.
Support record handling
When you contact us, chat and inbox records are kept with your account history. This lets us answer privacy questions consistently while reducing repeated requests for the same details.
Policy change checks
Before we update this Privacy Policy, we compare the wording with live account screens, wallet prompts and verification steps. The aim is simple: the policy should match what you see.
Access limits
Staff access to personal data is role based. Teams see the records needed for their work, such as verification status or support history, rather than full account data by default.
How This Page Stays Consistent
Our Privacy Policy sits beside other legal pages, but its subject is personal data only. We keep it separate from account rules, promotional wording and payment instructions so...
| Privacy Policy | This page focuses on personal data: account details, device signals, verification records, messages and payment references. It explains why we collect them and how you can contact us about them. |
|---|---|
| Terms page | Terms explain account use and service conditions. When terms mention verification or payments, this policy explains the data handling behind those actions, including retention and access controls. |
| Cookie wording | Cookie wording covers browser storage, session tags and analytics settings. This policy connects that browser activity to the wider personal data picture for your as8 account. |
| Payment wording | Payment pages may describe JazzCash, Easypaisa, SadaPay or Raast steps. This policy explains which references may be stored when those steps are completed or checked by support. |
| Support wording | Support pages explain how to reach us. This policy explains how the messages, attachments and identity checks connected to those support requests are stored and handled. |
| Security wording | Security copy may mention login protection and session checks. This policy explains the personal data used for those checks, including device signals and unusual-access markers. |
| Update notices | When privacy wording changes, we update the date or page content so you can see the current approach. Major changes may also be flagged through account messages. |
Visible Cues In Our Policy Layout
We design the Privacy Policy page so you can scan the data points before opening an account. Section labels, short chips and contact cards are meant...
Short scope badges
The badges near the hero name the data areas covered by the policy, including Pakistan account details and payment references. They help you spot relevance before reading every paragraph.
Plain contact cards
Support cards show where to send privacy requests and what to include. We separate account inbox, chat and email so you can choose the route that fits your access situation.
Purpose-based wording
Policy sections are written around purpose, such as security, verification and support. That structure helps you understand why data is collected, rather than only listing technical labels.
Local context chips
JazzCash, Easypaisa, SadaPay and Raast appear as context chips because transaction references can become personal data. The chips do not ask for wallet secrets or extra access.
Actionable answers
FAQ answers explain what you can ask us to do with your data, including correction or access questions. We keep the wording direct so support can act on your request.
Update visibility
When the policy changes, the page content is adjusted to reflect current handling. You should not need to compare unrelated pages to understand our privacy position.