LEGAL REFERENCE

How We Look After Your Account Data

666d4 keeps this privacy policy short on jargon, so you always know what we record when you open an account, move money with JazzCash or Easypaisa, and play...

JazzCash and Easypaisa awareRaast-ready recordsPakistan account flowPlain-language terms

Explore The Lobby Read FAQ

What We Collect And Why

Your 666d4 account holds only what we need to run it: your name, contact details, an age check, and the transaction references that come back from JazzCash, Easypaisa, SadaPay or Raast when you move money. We use those records to confirm who you are, settle withdrawals, and keep the lobby fair for everyone playing from supported regions. Where local law permits, we

also keep device and session details such as browser type, rough location and login times, because that is how we spot account takeover attempts early. We do not sell your details to advertising lists, and we pass payment identifiers only to the processor that needs them to finish your transfer. Staff access inside 666d4 is limited to the people handling a specific

task, and each lookup is logged.

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

PRIVACY DESK

Reaching The Team That Handles Data

Privacy questions should not send you hunting around the site. Our support desk runs seven days a week, 9am to 1am Pakistan...

POLICY OVERSIGHT

How This Policy Gets Checked

We do not set privacy wording once and forget it. A small internal group owns the text, checks it against how the platform actually behaves, and signs off every change before it...

Named Data Lead

One named owner holds responsibility for this policy, so questions do not bounce between departments. You can ask for that role by title through any support channel we list here.

Rail Mapping

Every payment route we carry, from JazzCash and Easypaisa to SadaPay and Raast, is mapped to the exact data it hands us, so nothing is collected by accident.

Access Log Checks

Staff lookups are recorded with a timestamp and a reason. We sample those logs on a schedule, which keeps everyday access narrow and makes unusual activity easy to flag.

Retention Schedule

Records are held for a set period tied to account activity and legal duties, then removed. You can ask which window applies to a particular record you want explained.

Partner Register

Any outside service that touches your data is listed internally with its purpose and contract terms. We do not pass details to advertising networks, list brokers or unrelated third parties.

Change Log Discipline

Each revision carries a date and a short summary of what moved, so you can see whether it affects you before you rely on the new wording.

How Our Policy Pages Line Up

Privacy sits alongside several other documents that govern your account, and we keep their language aligned so you never read two different answers to the same question. Where...

Terms Of Use

Sets the rules for using your account, and refers back here whenever personal data is mentioned, so the two documents never contradict each other on what we hold.

Cookie Notice

Explains the small files your browser stores on 666d4, how long they last, and how to clear them. Anything cookie-related belongs there rather than in this policy.

Account Verification

Covers the identity checks we run before withdrawals leave, including the documents you upload and how long we keep copies once a check is closed. It repeats the same retention wording used here.

Withdrawals And Timelines

Deals with how long a payout takes on each rail and what can delay it. The data points it shares with this page, such as transaction references, follow identical retention rules.

Promotional Terms

Sets out the conditions attached to any offer running on the site, and confirms that joining an offer never widens what we collect about you or how long we hold it.

Security Practices

Describes login protection, device checks and how we respond to a suspected breach. It uses the same definitions for personal data that appear throughout this policy.

Complaints Route

Explains how to raise a complaint and what happens next. If your complaint concerns data handling, it is routed to the same person who owns this policy.

The Elements That Shape This Page

This page is laid out so you can find the answer you came for without reading every paragraph. Headings carry plain labels, tables are avoided, and...

Sticky Section Index

A short list jumps you to any heading on this page, which saves scrolling on a phone when you only want the retention or contact part.

Summary Badges

The eyebrow chips under each heading flag what the section covers, so you can skim the page and pause where your own question is answered.

Rail Chips Row

Local payment names appear as chips beside the data terms, linking each collection point to JazzCash, Easypaisa, SadaPay, NayaPay or Raast.

Version Date Stamp

The date at the foot of the page tells you how fresh the wording is. Compare it with your last visit to see whether anything you relied on has moved.

Contact Cards

Each support route is shown as a card with its channel and expected reply time, so you know where to send a request before you finish reading.

Language Toggle

The page is written in Pakistani English and can be served in Urdu where the browser asks for it, carrying the same meaning in both versions.

Privacy Questions We Hear Often

Your name, contact details, date of birth and the transaction references returned by JazzCash, Easypaisa, SadaPay or Raast. We also log sign-in times and device type to keep the account secure.

Only with the processor handling that specific transfer, because it cannot complete without them. We do not sell or rent payment identifiers, and advertising partners never receive them.

Retention depends on the record. Transaction references are held for the period our financial duties require, while marketing preferences stay until you change them in your account settings.

Yes. Send the request from your registered email address and we confirm receipt within one working day, then deliver the file in writing once your identity is confirmed.

We watch login patterns, flag sessions that look unusual, and can require a fresh code sent to your registered contact. You should also keep your password off shared devices.

Every revision gets a new date and a message in your account message centre. Where a change affects how we use your data, we tell you before it takes effect.