LEGAL REFERENCE

Privacy Policy for 777i Accounts

777i keeps this Privacy Policy focused on what we collect, why we use it and how your choices work when you open an account in Pakistan. Read it...

Pakistan privacy contextAccount data explainedPayment records coveredChoice paths included
777i Privacy Policy for 777i Accounts

How We Handle Your Data

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

CONTACT ROUTES

Privacy Questions and Request Paths

If you want to ask about your personal data, correction, access, deletion or account privacy settings, contact us through the paths below. We may ask you to confirm account ownership before changing records, because privacy requests can expose sensitive account and payment details.

Team online

Privacy email

Send your request from the email linked to your 777i account. Include the issue type, your account ID if available and whether the matter involves profile data, payment records or support chat history.

Live chat handoff

Ask live chat to route a privacy request to the account team. The chat agent may confirm basic details first, then move the case away from open chat if sensitive records are involved.

Account security queue

Use this route if you think another person accessed your account or changed privacy settings. We check login signals, device history and recent payment references before adjusting account access.

POLICY CHECKS

How We Keep Policy Content Clear

Our Privacy Policy is written by the team that handles account records, payments and support requests. We keep the language direct, connect each data use to a practical...

Operational input

The same teams that manage account checks and payment references help shape this policy. That keeps the privacy wording aligned...

Plain wording

We avoid vague legal phrases where a direct explanation works better. If we collect a device signal, wallet reference or...

Payment context

Pakistan rails create specific records, such as wallet labels, transfer status and transaction references. Our policy separates those records from...

Access control

Internal access to personal data is limited by work need. Support staff, payment handlers and security staff see different record...

Change tracking

When we update this policy, we check whether new wording changes your rights, our retention period or the way payment...

Request handling

Privacy requests are logged with date, channel and account reference. That helps us answer consistently, confirm identity before disclosure and...

How This Policy Fits Other Pages

This Privacy Policy should be read with our related account pages, because each page covers a different part of your relationship with 777i. We keep boundaries clear so...

Terms page
The terms page explains account rules and service conditions. This Privacy Policy only explains personal data, why we process it and how privacy requests are handled through 777i channels.
Cookie page
The cookie page covers browser storage, tags and similar tools. This policy connects those signals to account security, session management and privacy choices across supported 777i access points.
Payments page
Payment pages explain how you move funds through local rails. This policy explains the personal data linked to those rails, including transaction references, wallet labels and status records.
Security page
Security content describes safeguards around account access. This policy explains what personal data may be checked when we investigate account risk, login changes or unusual payment activity.
Promotions page
Promotion pages describe current account offers. This policy explains how preference settings, eligibility checks and service messages use your data without turning privacy terms into sales copy.
Support page
Support pages show where to contact us. This policy explains how support messages, attachments and identity checks are handled once you ask us to solve a privacy or account matter.
Account page
Your account page shows profile fields and settings. This policy explains why those fields exist, how updates are recorded and when we may retain older records for audit needs.
LAYOUT SIGNALS

Visible Cues Inside This Policy

We design this page so privacy details are easy to scan without hiding important limits. Headings, chips and short cards separate account data, payment records, support routes and...

Short badges The badges near the hero show the main privacy areas...
Context chips Payment chips name JazzCash, Easypaisa, SadaPay and Raast only where...
Card labels Each card starts with a plain label so you know...
Direct answers FAQ answers use direct language rather than legal padding. Each...
Local wording We use Pakistani English and familiar rail names because privacy...
No mixed purpose This layout keeps privacy separate from game, offer and lobby...

Common Privacy Policy Questions

We collect account details, contact data, login signals, device data, payment references and support messages. The exact set depends on how you use your account and which local payment rail you choose.

Payment records help us match account activity with JazzCash, Easypaisa, SadaPay or Raast status updates. We use references, timestamps and wallet labels to confirm requests, resolve disputes and keep finance records accurate.

No. We do not sell your personal data. We use it to operate your account, process requests, secure access, send service messages and meet record keeping duties that apply to our work.

Contact us through the privacy email or support handoff using the contact linked to your account. We may ask for identity checks before changing profile fields or payment-linked records.

We keep records while they are needed for account operation, payment reconciliation, dispute handling, security checks or legal retention. When a record is no longer needed, we remove it or anonymise it.

Access is limited by work need. Support, payments and security teams see only the record types required for their tasks, and sensitive requests may be moved away from open chat.