Privacy Policy for Your 8 b Account
8 b keeps your Privacy Policy easy to read: what we collect, why we need it, how long we keep it, and how you can reach us. Open...
How We Handle Your Data
Our Privacy Policy explains the data 8 b processes when you create an account, verify access, move through casino or sportsbook pages, contact support, or use Pakistan payment rails. We collect only records needed to run the account flow, protect balances, confirm transactions, answer requests, and meet legal duties that apply in supported regions. Payment data is handled as transaction evidence, not
as open profile content. JazzCash, Easypaisa, SadaPay and Raast references may include receipt numbers, timestamps, account-name checks, status messages, and support correspondence. We separate security logs from support messages where practical, restrict staff access by role, and remove or anonymise records when retention is no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Talk To Us About Privacy
Privacy questions should not get buried inside general account chat. We keep specific routes for access requests, correction requests, retention questions, and payment-record queries. When you contact us, include the email or phone linked to your 8 b account, but do not send card images or unrelated documents unless our team asks for them securely.
Privacy email
Send us the email linked to your 8 b account and describe the privacy request clearly. We check identity before sharing account records, payment references, or security log extracts.
Live chat referral
If you start in live chat, ask for the privacy queue. The agent records your request type, confirms account ownership, and moves sensitive follow-up away from open chat where needed.
Account centre
Your account centre shows editable profile fields and login-security settings. Some payment and verification records cannot be changed there, so we explain the next step through support.
How We Keep Policy Evidence Clear
We write our Privacy Policy from the way 8 b is operated, not from a generic template. The policy team checks account screens, payment flows, chat transcripts, cookies, device logs, and security...
Flow checks
Before changing privacy wording, we compare it with account creation, login, verification, withdrawal, and support flows, so each data category matches a screen or process you can recognise.
Payment evidence
JazzCash, Easypaisa, SadaPay and Raast records are treated as transaction evidence. We track reference codes, processing status, and support actions without turning them into public profile material.
Access control
Staff access is separated by task. Support can see case history, finance can handle transaction checks, and technical teams use logs mainly to investigate account security or page faults.
Device logs
Device and browser data help us recognise suspicious access, failed logins, session clashes, and page errors. The policy names these uses so you understand why technical logs exist.
Retention checks
We do not keep every record for the same period. Financial evidence, identity checks, chat content, and security logs follow different retention needs, which we summarise in the policy.
Change control
When privacy wording changes, we compare the old and new text, record why the change was made, and place key updates where you can read them before continuing.
Aligned Privacy Pages Across 8 b
Privacy wording should stay consistent wherever you read it on 8 b. We align this page with our cookie, account, transaction, and support text so you are not...
| Cookie text | Cookie labels on 8 b use short wording, while this Privacy Policy explains why we use browser storage for login sessions, fraud checks, preferences, and performance measurement. |
|---|---|
| Account terms | Account pages may ask for profile details quickly. This policy explains the reason behind those fields, how we use them, and when support may ask for correction. |
| Transaction screens | Payment screens show status messages for JazzCash, Easypaisa, SadaPay and Raast. The policy connects those messages to stored references, reconciliation checks, and support case history. |
| Security prompts | Login alerts, password resets, and device checks can feel technical. This policy explains how security data is created, who can access it, and why it matters. |
| Support scripts | Support agents use approved wording for privacy requests, identity checks, and correction cases. This keeps chat replies aligned with the policy rather than improvised from memory. |
| Promo board labels | If a promotion area asks for eligibility checks, this policy explains the data behind that check, including account status, region support, and transaction confirmation where relevant. |
| Regional wording | Access language across 8 b uses supported regions and where local law permits. The same wording appears here so privacy expectations match account availability. |
Policy Page Signals You Can See
This page is laid out to help you scan privacy rights without losing context. Headings separate collection, use, sharing, retention, security, cookies, and contact routes. Short chips point...