How 888gi Handles Your Data
888gi keeps account identity, login activity and transaction context under one Privacy Policy, so you can see what we collect before you open your account. The policy also...
Privacy Terms For Pakistan Access
This Privacy Policy explains how we collect, use, store and share data when you access 888gi.app from supported regions in Pakistan where local law permits. We process account details you provide, technical logs from your device, payment context from local rails, and security records created during login or withdrawal checks. We use that data to keep your account reachable, confirm payment references,
detect misuse, answer privacy requests and meet legal record duties that may apply to us. We do not sell your personal data. When a service partner helps us with hosting, analytics, payment routing or customer care, we limit access to the data needed for that task and require handling aligned with this Privacy Policy.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ways To Reach Our Privacy Team
Your privacy questions should not feel hidden behind account menus. We keep contact routes tied to the Privacy Policy, so you can ask about data access, correction, deletion, cookie controls or payment records without repeating your issue across channels. Each route asks for enough detail to locate your account securely.
Account inbox
Use the account inbox for privacy questions linked to your profile. We can match your request to login records, device checks and payment references without asking you to send sensitive details again.
Email privacy route
Email works for formal requests about access, correction or deletion. Include your registered phone or email, but never send passwords, card data or one-time codes in the message body.
Live chat handoff
Chat can start a privacy case when you are signed in. Our team records the case reason, confirms account ownership, then moves complex data requests to the privacy queue.
How We Keep Policy Wording Accountable
We write this Privacy Policy from the systems we operate, not from generic legal wording. That means the clauses reflect account creation, wallet checks, device logs, cookie tools, support records and security...
Data map checks
We map each policy section to a real account event, such as registration, login, wallet reference, support case or withdrawal check, so collection language stays tied to actual processing.
Limited access
Internal access to personal data is role based. A support agent, risk checker and technical operator see different fields, depending on the privacy purpose behind the task.
Payment context only
For JazzCash, Easypaisa, SadaPay and Raast, we handle references, status messages and reconciliation data. We do not ask you to share wallet passwords or one-time codes.
Cookie clarity
Our cookie wording separates essential session tools from analytics signals. You can see why a browser cookie exists before deciding which optional settings to keep enabled.
Retention controls
We keep records only for account operation, dispute handling, security checks and legal duties. When retention is no longer needed, data is removed or reduced where practical.
Change checks
Before policy wording changes, we compare it with sign-in, support, wallet and device flows. Material changes are presented clearly so you can read what shifted.
Consistent Privacy Across Related Pages
Your privacy rights should read consistently wherever you enter the site. We align this page with cookie text, account notices, wallet screens and support forms, while keeping this...
| Cookie page alignment | Cookie choices use the same categories described here. Essential login cookies, analytics tags and preference records are explained with matching purpose language across browser and mobile web flows. |
|---|---|
| Account form wording | Registration fields are matched to this policy, including phone, email and identity checks. The form should not ask for data without a privacy purpose described here. |
| Wallet screen wording | Wallet screens mention that payment references may be stored for reconciliation and dispute handling. This page explains the privacy reason behind those records in fuller language. |
| Support form wording | Support forms ask for details needed to solve your case. The privacy wording here explains why chat transcripts, screenshots and account markers may be retained. |
| Security alert wording | When we send login or device alerts, those alerts rely on security processing described here. Location signals, device type and timing are treated as account protection data. |
| Partner references | Where service partners appear in shorter notices, this policy explains the categories involved. Hosting, analytics, payment routing and care tools are separated by privacy purpose. |
| Update messages | If wording changes materially, short page messages point back to this policy. We keep the fuller explanation here so you can check the complete position. |
Privacy Layout You Can Read Quickly
We designed the Privacy Policy page to make key data points easy to find without turning it into a legal wall. The visible layout separates what...
Quick scope badges
The badges near the hero summarise the policy scope: account data, cookies, security and Pakistan access context. They help you decide which section to read first.
Purpose blocks
Purpose blocks separate account operation, fraud prevention, support handling and legal record keeping. Each block connects the data type to the reason we process it.
Sharing table
The sharing area lists partner categories rather than vague labels. It distinguishes hosting, analytics, payment routing and customer care, with limits on what each partner can access.
Retention cues
Retention cues explain why some records remain longer than others. Payment disputes, security checks and legal duties may need different periods from ordinary preference settings.
Rights panel
The rights panel sets out how to ask for access, correction or deletion. It also explains when we may need to keep limited records for legal or security reasons.
Plain language
We avoid unnecessary legal phrasing where a clear sentence works. Defined terms are kept close to the section that uses them, so the policy stays readable.