LEGAL REFERENCE

Your 8zz Privacy Policy

8zz sets out this Privacy Policy so you can see how we collect, use and protect your account, lobby and transaction data before you open an account. We...

Account data usePakistan payment contextSupport privacy routesClear data choices
8zz Your 8zz Privacy Policy

How We Handle Your Data

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT ROUTES

Privacy Contact Paths For You

If you have a privacy question, we want you to reach the right inbox without sharing extra details in public chat. Keep your account ID, registered email and a short request summary ready. Our support team may ask identity-check questions before making changes, because privacy requests should not expose your account to another person.

Team online

Account privacy inbox

Use our privacy contact route for access, correction or deletion requests. We confirm your identity first, then explain what data we hold and which records must stay for legal or security reasons.

Live chat handoff

Chat can collect the starting detail for a privacy matter, but deeper requests move to a secure channel. This keeps documents, account references and answers away from shared screens.

Payment query link

For JazzCash, Easypaisa, SadaPay or Raast references, we can check the 8zz transaction record. Wallet credentials, app passwords and bank-level details remain outside our support view.

POLICY CHECKS

Checks Behind This Policy

We write this policy from the way our account systems actually work, not from a generic template. Each update checks registration fields, verification steps, payment references, support scripts and security logging. When...

Field mapping

We map each account field to a purpose before it is requested. If a detail is only useful for verification, support or security, the policy describes that narrower use.

Access controls

Staff access is limited by role, so support, payments and security teams see only the data needed for their task. Internal activity can be logged for audit checks.

Device signals

We may process IP address, browser type, session time and device markers. These help detect account takeover attempts, unusual access and technical errors affecting your session.

Payment references

When a cash-in or cash-out is checked, we use reference IDs, timestamps and account matching data. We do not need your JazzCash or Easypaisa app login details.

Retention checks

Retention periods are tied to account operation, legal duties, disputes and fraud prevention. After the need ends, we remove or anonymise records where our systems allow.

Policy updates

When wording changes, we keep the privacy meaning aligned with account screens and support answers. Material changes are shown on the page so you can read them before continuing.

Same Rules Across 8zz Pages

Your privacy rights should not change depending on which 8zz page you open. We keep this Privacy Policy aligned with account terms, cookie controls, security notices and support...

Account terms
The terms explain account duties, while this policy explains the data used to manage those duties. Together, they show why identity, access and transaction records may be needed.
Cookie controls
Cookie messages cover browser storage and preference tools. This policy adds the wider context, including session security, analytics limits and how those signals connect to your account.
Security notices
Security pages describe access protection in plain language. The Privacy Policy explains the related data processing, such as login history, device markers and unusual activity checks.
Support scripts
Support answers are matched with this policy so agents do not ask for unnecessary private details. Sensitive requests are moved to safer channels after the first contact.
Transaction screens
Cash-in and cash-out pages may show JazzCash, Easypaisa, SadaPay or Raast labels. This policy explains how transaction references are recorded without taking wallet login data.
Promo board
If the promo board uses account status, this policy explains the data categories involved. It does not allow unrelated reuse beyond account management and permitted communications.
Data requests
Request forms and emails follow the same identity-check standard. We answer in a way that protects your account from disclosure to anyone who cannot prove access rights.
PRIVACY LAYOUT

Privacy Layout Highlights You See

This page is arranged to help you scan privacy details before you join or continue using 8zz. The visible layout separates collection, use, sharing, retention and choices. We...

Plain section labels Headings name the data practice being explained, such as collection...
Local context chips Short chips mention JazzCash, Easypaisa, SadaPay and Raast only as...
Choice markers Where you have a choice, the page explains how to...
Security callouts Callouts describe how login records, device signals and verification checks...
Sharing limits The layout separates internal use from service-provider access. We explain...
Update markers When privacy wording changes, we mark the page so you...

Privacy Questions Before You Join

We collect registration details, account credentials, verification records, device signals and activity logs needed to run your account. We may also record transaction references connected with supported Pakistan payment options.

No. We may store transaction references, status updates and account matching data, but wallet app passwords and full login credentials remain with your provider, not inside our platform systems.

Device and session data helps us protect account access, detect unusual behaviour, fix errors and keep your session working. It can include IP address, browser type and login timestamps.

Yes. Send a correction request through our privacy contact route. We verify your identity first, then update eligible account details or explain why a record must remain unchanged.

Access is limited by work role. Support, payments and security teams see only the data needed for their task, and service providers receive limited data under processing arrangements.

Retention depends on account operation, legal duties, dispute handling and security needs. When a record is no longer required, we delete it or remove direct identifiers where practical.