Terms page boundary
Our terms explain account use and service rules, while this page explains personal data handling. If a topic involves both account conduct and data records, each page covers its own part.
LEGAL REFERENCE
Privacy Policy for Pakistan Account Data
Our Privacy Policy explains what account, device, location and transaction data we collect when you open or manage your 7878 game account in supported regions of Pakistan. Read...
Pakistan data careAccount privacy termsPayment data contextSupport contact routes
How We Handle Your Privacy Rights
This Privacy Policy describes how 7878 game collects and uses your personal data where local law permits access to our brand home and account services. We collect details you provide during account creation, login checks, wallet actions, support chats and security checks. We may also process device data, IP address, approximate location, browser type and session records so we can protect your
account, detect unusual access and keep payment records accurate. Pakistani payment activity may involve JazzCash, Easypaisa, SadaPay, NayaPay or Raast references, but we do not ask you to share wallet passwords or banking PINs with our support team. When service partners help with hosting, fraud screening, messaging or payment routing, they receive only the data needed for that task. You may contact
us to ask about access, correction or removal options tied to your account, subject to legal and security record duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY CONTACTS
Where To Ask Privacy Questions
If anything in this Privacy Policy feels unclear, contact us before sending sensitive documents or payment screenshots. We separate privacy requests from routine lobby questions so your data access, correction or deletion request reaches the right team. Include your account ID, registered mobile number and a short reason, but never include wallet PINs or one-time codes.
Team online
Account privacy email
Use the privacy email listed inside your account area for data access, correction or removal requests. We may ask for account identifiers so we can confirm the request without exposing records to another person.
Live chat handoff
Our chat team can route privacy questions to the data team after basic account checks. Share only the minimum details needed, and avoid sending payment passwords, one-time codes or full identity images.
Payment data queries
For JazzCash, Easypaisa, SadaPay, NayaPay or Raast records, tell us the transaction date and reference number. We use those details to locate records while keeping unrelated account activity out of view.
POLICY CHECKS
How We Keep Policy Text Accurate
We write this Privacy Policy from the way our account, security and payment flows actually work. When a process changes, we check the wording against the screens you see, the records we...
Account flow matched
Policy wording is aligned with account creation, login checks and profile updates. When a field is added or removed, we reassess whether the policy still explains why that data is collected.
Payment routing checked
JazzCash, Easypaisa, SadaPay, NayaPay and Raast references are treated as payment context, not open banking access. We describe records we may store without asking for wallet passwords or PINs.
Security logs explained
Login time, device signals and IP data are covered because they help us recognise suspicious account activity. The policy states these purposes clearly so you understand why technical records matter.
Partner access limited
Service partners may support hosting, messaging, payment routing or fraud checks. We describe that sharing as limited to a clear task rather than broad reuse of your account data.
Request handling recorded
When you ask for access, correction or removal, we keep a request trail so our reply is traceable. That record helps prevent duplicate action and protects your account from false requests.
Plain wording maintained
We avoid dense legal phrasing where a clear sentence will work. The Privacy Policy is written so you can understand collection, use, storage and sharing before you open an account.
POLICY LINKS
How This Policy Fits Other Pages
This Privacy Policy sits beside our terms, cookie wording and account rules, but it has a separate purpose. It focuses on personal data: what we collect, why we need it, how long...
Cookie wording link
Cookie wording deals with browser storage and tracking choices. This Privacy Policy connects that technical data to wider account records, including device signals used for security and session stability.
Payment rule separation
Payment rules cover transaction steps, timing and verification. This policy covers the data side, such as reference numbers, wallet names and records connected with JazzCash, Easypaisa or Raast activity.
Support record scope
Support pages tell you how to contact us. This policy explains how chat transcripts, email messages and attached files may be stored, used and restricted inside your privacy request history.
Security page alignment
Security wording explains account protection habits. This Privacy Policy states which security-related data, such as login time or device type, may be processed to protect access to your account.
Promotion message limits
If you receive account messages, this policy explains how contact details may be used and how preference changes can be requested. We treat message choices as part of privacy control.
Regional access wording
Where local law permits, our account services may be accessed from supported regions. This policy explains how location and access signals may be used to apply those regional checks.
Visible Privacy Cues On This Page
The layout of this Privacy Policy is built to make important data topics easy to spot. You can scan for collection, payment context, sharing, storage, request...
Clear section order
We place collection, use, sharing and contact topics in a logical order. That way you can see how your account data moves from signup through payment checks and support requests.
Local data markers
Pakistan wallet names appear only where payment records are relevant to privacy. This helps you connect JazzCash, Easypaisa, SadaPay, NayaPay and Raast references with data handling duties.
Short badges
Badges near the hero summarise policy themes without replacing the full text. They point to account privacy, payment data context and contact routes you may need later.
Request language
Privacy request wording uses action terms such as access, correction and removal. We explain that some records may remain where security, payment tracing or legal duties require retention.
Safety reminders
Repeated reminders about PINs and one-time codes are included because privacy protection also depends on what you share. Our team does not need secret wallet credentials for support.
Policy focus
Each card is written around data handling, not broad lobby promotion. That focus helps you decide whether you are comfortable opening an account under these privacy terms.
Common Privacy Policy Questions
We collect account details you provide, such as your mobile number, login records and profile data. We may also process device signals, IP address and approximate location for access checks and account security.
We may store payment references, timing, amount records and wallet labels needed to trace a transaction. We do not ask for your JazzCash or Easypaisa PIN, password or one-time code.
Device and location signals help us recognise unusual logins, apply supported-region checks and protect your account. These records are used for security and service operation, not for public display.
Yes, you can contact us to request correction of account data that is inaccurate. We may need identity checks before making changes, especially where payment or security records are involved.
Some partners may process limited data for hosting, messaging, fraud checks or payment routing. We share only what is needed for the task and keep account control with 7878 game.
We keep privacy request records long enough to answer you, track actions taken and protect your account from false requests. Some transaction or security records may remain for legal duties.
Do not send wallet passwords, PINs, one-time codes or full card details. For payment questions, a transaction date, amount and reference number are usually enough for us to locate records.