LEGAL REFERENCE

Privacy Policy for Your 7777cb com Account

This page sets out how 7777cb com collects, stores and uses what you hand over when you open an account, and what you can ask us to do...

What we collectHow we hold itYour request rightsCookie handling
7777cb com Privacy Policy for Your 7777cb com Account

How This Policy Applies to Your Region

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

REACHING OUR DESK

Contacting Us About Personal Data

Privacy requests go to the same desk that answers account questions, so you do not have to guess which team to write to. Pick the channel that suits you, include your account number and the region you play from, and we can locate the right record faster. Most written requests get a reply within two working days.

Team online

Live Chat

Open from 9am to 1am Pakistan time, live chat is the quickest route for a privacy question and lets us verify your identity while you wait.

Email Desk

Write from your registered address with a clear description of the request; email suits copy, correction and deletion requests that need a written trail.

Message Centre

Sign in and raise the request from your own profile, where we can see your verification history without asking you to repeat it.

OUR HANDLING STANDARDS

Standards Behind This Privacy Statement

We write this page the way we run the account side of 7777cb com: plainly, and with the details that actually matter to you. Everything here describes practices on our own systems...

Data Minimisation

We ask for your name, date of birth, contact details and payment reference only because verification and payout matching need them, never to fill a form.

Encryption in Transit

Sign-in, deposit and withdrawal traffic between your device and our servers runs over encrypted connections, so credentials and transaction references stay unreadable in transit.

Internal Access Logs

Every time a member of our team opens an account record, the system logs who did it and when, which is how we audit access after a query.

Retention Windows

We keep account and transaction records for the period local rules require, then remove what is no longer needed instead of storing everything indefinitely.

Partner Boundaries

JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers are settled by licensed processors, so we receive a confirmation reference rather than your full credentials.

Plain Language

This page stays free of legal padding so a reader in Lahore or Karachi can follow it without a translator or a lawyer beside them.

ACROSS OUR PAGES

Consistency With Our Other Policy Pages

This privacy page sits alongside our terms and payments pages, and the three are written to be read together. A term defined here carries the same meaning there. If wording elsewhere ever...

01

Terms of Use

Our terms carry the account rules and this page carries the data rules; read together they explain what we hold and why.

02

Payments Page

The payments page lists which rails you can use; here we explain what transaction data those rails generate and how long we keep it.

03

Cookie Notice

Cookie handling is described in the same voice, covering the session and preference cookies that keep your sign-in and language choice stable.

04

Account Security

Password handling, device checks and the prompts you see after an unfamiliar login are explained on our security pages in matching wording.

05

Promotion Terms

Conditions for a running promotion live on their own page, and any personal data tied to it still follows the collection and retention rules written here.

06

Regional Availability

Where access is limited to supported regions, that wording matches across our pages rather than shifting depending on which section you are reading.

07

Change Notices

When we revise a policy we log the change date on every affected page at once, so no page ever shows a newer revision than another.

What You Will Find in This Policy

Before you scroll, here is how the page is arranged. The opening sections cover what we collect, the middle explains how long we hold it and...

Collection Points

Where your details enter our systems: registration, identity checks, deposit references from JazzCash or Easypaisa, withdrawal requests and support conversations.

Why We Need It

Every data point is tied to a purpose, from confirming you meet the age rule for your region to matching a payout to the right account holder.

Sharing Boundaries

Who sees what, including the processors that settle Raast or SadaPay transfers, and the limits we place on anyone acting for us.

Retention Schedule

How long each record type is kept, why transaction history outlives a closed account, and what happens to your profile once that window ends.

Your Request Path

The steps for asking us to show, correct or delete what we hold, including the identity checks we run before releasing anything.

Updates and Dates

How revisions to this page are handled, what a change of wording means for you, and how much notice we give before a new version applies.

Privacy Questions We Get Asked

Your name, date of birth, email, phone number and country, plus the payment reference from your first JazzCash, Easypaisa, SadaPay, NayaPay or Raast transfer. We do not ask for anything we cannot explain a use for.

No. We share data only with processors that help us run the account, such as payment partners and identity-check providers, and only to the extent the task requires.

Message our desk from your registered email address with the phrase data request and your account number, and we will assemble the record for you.

You can close your account at any time, and we will remove what we no longer need. Transaction records tied to payout rules are kept for the required period.

Yes, for sign-in sessions, language preferences and basic performance measurement. You can clear them in your browser, though signing in again will refresh the session cookie.

We update the revision date at the top of this page and post a short note in your account message centre when a change affects how your data is handled.