LEGAL REFERENCE

How 888gv Handles Your Account Data

We explain what we collect when you open an account, load funds through JazzCash, Easypaisa, SadaPay or Raast, and move through the lobby from anywhere in Pakistan. You...

Data categoriesRetention windowsCookie settingsYour choices
888gv How 888gv Handles Your Account Data

Where Our Privacy Rules Apply

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

DATA REQUESTS

Reaching Our Policy Desk

Questions about your data should not sit unanswered. Our policy desk runs on live chat through operating hours and on email for longer threads, and every request gets a reference you can quote back. Tell us what you need — a copy, a correction or a deletion — and we point you to the clause that deals with it.

Team online

Live chat

Open live chat inside your account and a policy agent picks up during operating hours. Keep the request in one thread so we can confirm it in writing.

Email requests

Email our policy desk with the account number tied to your profile. Attach nothing unless we ask. We aim to reply within two working days. Access and deletion requests can take longer.

Escalation

If our answer does not settle the matter, ask for escalation to the policy lead. We name the handler and set a date for a final written response.

HOW WE PROVE IT

Evidence Behind This Policy

A policy is only worth the practice behind it. Our data team writes these clauses from systems we actually run, not from a template, and each one names a purpose, a retention...

Named purposes

Every field we store carries a stated reason — running your account, settling a transfer, meeting a legal duty or keeping the lobby secure. Nothing sits there without one.

Retention windows

We publish how long each category stays. Account records outlive a closed profile because anti-fraud and tax duties demand it, while marketing preferences drop away on your request.

Local rail partners

JazzCash, Easypaisa, SadaPay, NayaPay and Raast each apply their own privacy terms to the transaction data they see. We share only identifying fields a transfer needs.

Access controls

Staff access runs on role permissions and two-factor sign-in. Anyone touching account data leaves a trace, and we audit those logs on a fixed schedule, not just after incidents.

Plain language

Clause headings say what each section does before you read it. Short sentences, no definitions parked at the bottom, and a plain summary table up front for scanning.

Accountability

Every clause names the team that owns it — data, payments, security or support. That team answers questions directly, so an escalation reaches someone able to change the wording.

How Our Policy Pages Fit Together

This page sits inside a small set of legal documents that back each other up. Read them together and you get the full picture of how an account...

Cookie notice
Sets out the small files our pages store on your device. This privacy page says why a cookie exists; the notice names each one, its lifespan and its switch.
Terms of use
The contract side of your account, carrying the rules you accept when you open a profile. This privacy page deals only with data handling — two documents, two separate jobs.
Identity checks
Explains when we ask for a document and what happens to the copy afterwards. It runs on the same retention clock as this page, so one timeline governs both.
Account rules
Fair-use expectations inside the lobby. If access is ever paused, this page states which records we hold during an enquiry and which we release for you once it closes.
Complaints policy
Mirrors the escalation steps in the support block. It fixes the response clock, names the person owning a dispute, and shows the point where you can take a matter further.
Security statement
Describes encryption in transit, session handling and sign-in alerts. It pairs with this page: one explains what we guard, the other explains what we keep and for how long.
Consent choices
Lists the optional uses you can switch off without losing your account — marketing messages, lobby suggestions shaped by play history, and survey invites. Each change applies the moment you save.

What Stands Out On This Page

Scan the headings and you meet the same four questions every time: what we hold, why we hold it, how long it stays, and who can...

Summary table

A short table near the start maps each data category to its purpose and retention period, so you can see the whole shape at a glance before reading a single clause.

Regional clauses

Some rights apply only where local law permits, and those paragraphs carry a visible marker. You never have to guess whether a clause reaches your region — the tag sits beside it.

Wallet transparency

When you load funds with JazzCash, Easypaisa, SadaPay, NayaPay or Raast, we state which transaction fields we keep, which we pass on, and which we never touch at all.

Closed accounts

Shutting a profile does not wipe everything at once. We spell out what leaves immediately, what stays for a set period under anti-fraud and tax duties, then it goes.

Device sessions

Every sign-in from a new phone or laptop is listed in your account with the city we detected and the time. Spot something odd and end that session.

Change history

Revisions sit in a dated running list rather than being silently rewritten. If a clause shifts in a way that affects you, the entry says what moved and gives the date.

Data Questions We Hear Often

We take the name, date of birth and contact details you type in, plus device and connection signals our systems log. Identity documents are asked for only when a check is due.

Only the identifiers a transfer needs — an account reference and the amount. Each partner applies its own privacy terms to what it does with that data, and we send nothing else.

Account and transaction histories stay for as long as anti-fraud and tax duties require, then they are deleted or anonymised. Marketing preferences and session logs clear far sooner.

Yes. Ask through live chat or our policy email and we send a readable export of your account file. Where local law allows a fee or a longer window, we say so first.

Two-factor sign-in runs on every fresh device, sessions are listed inside your profile, and card or wallet details are never shown in full once stored. Anything unusual triggers a check.

It is updated whenever our systems or the rules around them shift. The revision date at the foot of the page moves with it, and anything affecting your data is flagged inside your account.