What This Privacy Policy Covers
This page sets out the personal data 666p online collects when you open an account, what we do with it, how long we keep it, and the choices...
How We Apply This Policy Where You Live
666p online ties this privacy policy to the region you sign in from. Where local law permits, we collect only what runs your login, verifies a transfer through JazzCash, Easypaisa, SadaPay, NayaPay or Raast, and keeps your session safe. Where a region sets stricter rules, those rules win. Consent records are stored so that if you ask what we hold, we answer
with the same list you accepted. Support conversations are logged, so a query raised tonight is picked up tomorrow without you repeating yourself. Retention follows the same idea: we keep what payment partners and regional rules require, then delete the rest on a rolling schedule. Write to us about access, correction or deletion and we walk you through it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Writes And Changes This Policy
We draft this policy in house and revise it whenever a rail or a data practice moves. Every change is dated and summarised in one paragraph, then pushed to your account notice...
In-House Drafting
The same team that runs account operations in Pakistan writes this text, so the wording matches what actually happens when you sign in, verify a rail or close your account.
Dated Change Log
Each amendment carries a date and a one-line reason. Earlier versions stay archived so you can compare what you accepted with what stands on the page today.
Rail Mapping
We list which data each rail needs, from JazzCash wallet references to Easypaisa numbers, SadaPay identifiers and Raast transaction codes, instead of hiding them in one vague sentence.
Bilingual Wording
Replies and policy text are written in clear English with Urdu support, using the same labels your account screens already show so nothing has to be translated twice.
Security Practice
Sessions are pinned to a device fingerprint, password resets ask for a second step, and staff access to account records is limited to named roles and logged for later checking.
Regional Standards
Handling follows the rules of your supported region. Where two sets of requirements differ, we apply the stricter reading rather than picking the lighter one.
Matching Our Other Policy Pages
The wording here matches our terms page, our cookie page and our account rules, so the same subject reads the same way wherever you land. Where two pages...
| Shared Definitions | Terms such as account data, processing and retention carry one meaning across the privacy page, the terms page and the cookie page you clicked through to reach here. |
|---|---|
| Cookie Alignment | What we describe here about tracking matches the cookie list exactly: the same categories, the same opt-out path and the same effect on your lobby view. |
| Terms Alignment | Account duties described in our terms reference the same data points used here, so you are never asked to accept two versions of a single rule. |
| Withdrawal Clauses | Verification wording on the withdrawal side follows this page: identical documents, an identical retention window and the same delete-on-request route for your records. |
| Local Rail Naming | JazzCash, Easypaisa, SadaPay, NayaPay and Raast are named the same way across every page, so the rail you actually use reads consistently wherever you look. |
| Revision Order | When a change touches several documents, it appears here first and the remaining pages catch up inside the same working week instead of leaving mismatched sentences live. |
| One Contact Point | Every policy page points to a single privacy mailbox, so you never have to guess which address belongs to which document before raising your question. |
How This Page Is Laid Out
Everything here is built to be scanned. A notice banner opens the page, the data table follows, and a dated log runs down the side for...
Notice Banner
A short banner shows when this policy last changed and links straight to the amended paragraph, so you never have to hunt for the difference yourself.
Data Table
One table lists what we collect, why we need it and how long it stays, covering login details, device signals and rail references side by side.
Dated Rail
A dated column records each amendment with a one-line reason and a paragraph number, and older entries stay visible instead of disappearing on the next update.
Consent Switches
Switches for optional tracking sit beside the clause explaining them, so you can make that choice while the reason for it is still in front of you.
Language Toggle
English and Urdu versions of the same text sit one tap apart with matching numbering, so any clause keeps the same reference in either language.
Request Shortcut
A button at the foot of the page opens a pre-filled data request against your logged-in account, saving you from typing your reference out again.