Terms page boundary
Our terms describe account rules and service access. This Privacy Policy instead explains what personal data we collect, how it supports your account, and when sharing may occur.
LEGAL REFERENCE
How 7k7k handles your privacy
7k7k keeps your account, device, session, and transaction data within a clear Privacy Policy built for Pakistan access where local law permits. Before you open your account, you...
Pakistan privacy scopeAccount data usePayment record careSupport contact routes
Privacy terms for supported regions
This Privacy Policy explains how 7k7k collects, stores, uses, and shares personal data connected to your account, lobby sessions, support requests, and payment activity in supported regions of Pakistan where local law permits. We use data to create account access, protect sign-ins, process withdrawals, confirm payment references, answer your messages, and keep records required for service integrity. We do not sell your
personal data as a mailing list. Some checks involve payment partners, identity verification providers, hosting systems, analytics tools, and fraud-prevention services, but those parties receive only the data needed for their role. If our policy changes, we update this page so you can read the current privacy position before continuing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Ask us about your data
If you have a privacy question, we want the request to reach the right queue without making you repeat the same issue. Use the contact path linked to your account when possible, because it helps us verify that the request belongs to you before we discuss personal records. For payment-related privacy queries, include the payment rail name and reference time, not your full wallet credentials.
Team online
Account privacy inbox
Use the account-linked contact form for access, correction, or deletion requests. We verify your identity first, then route the case to our privacy handling queue with a dated record of your request.
Live chat privacy handoff
Chat support can receive a privacy concern and move it to the correct team. We may ask for account identifiers, but we will not ask for your Easypaisa or JazzCash wallet PIN.
Payment record queries
For JazzCash, Easypaisa, SadaPay, or Raast record questions, share only the transaction reference, amount, and approximate time. That lets us locate internal logs without exposing private wallet access data.
POLICY CHECKS
How we keep the policy current
Our Privacy Policy is maintained by the people who operate the account, security, support, and payment flows behind 7k7k. We check it against the data we actually collect, rather than writing broad...
Operational ownership
Privacy wording is checked against the account screens, support forms, and payment flows we run. That helps keep the policy tied to real data events, not vague platform claims.
Payment rail alignment
When JazzCash, Easypaisa, SadaPay, or Raast records pass through our systems, we map what is stored, why it is needed, and how long it supports reconciliation or security checks.
Security review points
Sign-in alerts, device markers, IP checks, and session records are covered because they protect account access. The policy explains these uses without turning security monitoring into unrelated marketing copy.
Support evidence trail
Messages sent to us may include screenshots, transaction references, or account details. We keep the handling route clear so your privacy request can be traced and answered by the correct team.
Change tracking
When we revise the Privacy Policy, we update the visible page text and keep internal change records. That makes it easier to answer what changed if you ask later.
Access control
Internal access to personal data is limited by role. Support, payment, and security staff see the records needed for their task, rather than broad account data by default.
PAGE CONSISTENCY
How this policy fits our legal pages
Our legal pages work together, but this page stays focused on privacy. The terms page explains account use, while this Privacy Policy explains personal data handling. Cookie wording covers browser storage, and...
Cookie wording link
Cookie content covers browser storage, analytics tags, and session tools. We connect it back to privacy because these tools can affect device recognition and account security.
Payments section split
Payment rules explain processing steps and timing. This page focuses on the personal records behind those steps, including references, verification signals, and reconciliation logs.
Support content split
Support pages explain how to contact us. This policy explains how we use support messages, attachments, chat transcripts, and identity checks connected to privacy requests.
Security page overlap
Security wording may discuss account protection tools. Here, we explain the privacy side of those tools, including device markers, access logs, and fraud-prevention checks.
Promotion page separation
Promotional pages may show current account offers. This Privacy Policy does not describe offer value; it explains how related account eligibility records may be handled.
Region wording
Access language refers to supported regions where local law permits. Privacy wording follows that scope, so data handling is described in the same regional context.
LAYOUT SIGNALS
Privacy cues you can spot
We place privacy cues where they matter: account creation, login checks, wallet reference handling, support forms, and legal page links. These visible elements help you understand when personal...
Clear form labels
Account and support forms label required fields so you can...
Legal page access
Privacy wording is linked from account and footer areas, making...
Session prompts
When security checks involve device or session signals, the policy...
Payment reference care
Where JazzCash, Easypaisa, SadaPay, or Raast references are used, we...
Support upload caution
If you send screenshots, our teams handle them as support...
Policy date visibility
A visible update date helps you confirm you are reading...
Common questions about your privacy
We collect account details, login records, device signals, payment references, support messages, and verification data needed to run your account. The exact data depends on the actions you take with us.
Payment references help us match JazzCash, Easypaisa, SadaPay, and Raast activity to your account, resolve delays, check withdrawals, and investigate mismatches without asking for private wallet access credentials.
Yes. Send a request through the account-linked contact route and explain what should be corrected. We may verify your identity before changing records, especially where payment or security data is involved.
We share data only where needed for hosting, verification, payment reconciliation, analytics, support tools, security checks, legal duties, or service operations. Each sharing route is tied to a specific purpose.
Device checks help us recognise sign-ins, protect sessions, and spot unusual access. These records may include browser type, IP signals, device markers, and timing, handled under this Privacy Policy.
Retention depends on the record type and purpose. Account, payment, support, and security records may be kept while needed for operations, dispute handling, legal duties, or fraud-prevention checks.
Use the account-linked form when available, or ask chat support to route your privacy request. Include relevant dates and references, but never send wallet PINs or unrelated personal documents.