LEGAL REFERENCE

Privacy Policy Behind Every hx777 Account

Every account on hx777 is built on one clear commitment: you always know what we hold and why we hold it. This page sets out the data we...

Data you controlCookie choicesSupport hoursRegional notes
hx777 Privacy Policy Behind Every hx777 Account

What This Policy Covers Day to Day

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

REACHING OUR DESK

How to Send a Privacy Request

Requests reach us faster when they come from the email address already registered on your account, because that is how we confirm...

Email our privacy desk Write from the address registered on your account...
Chat when you are signed in Sign in, open a live chat and say...
Postal address on record If you prefer paper, our postal address appears...
WHO MAINTAINS THIS

The People Behind This Policy

This page is owned by our compliance team rather than by marketing, and the wording is checked whenever account data starts moving differently through our systems. A named policy owner signs each...

Named policy owner

One person is accountable for this page. Their role, rather than personal details, appears in the change history, so account data always has a single desk answerable for it.

Dated change history

Each revision carries a date and a short line explaining what moved. Nothing is edited silently, so you can compare the wording you agreed to with the version live now.

Plain-English editing

A separate editor strips out legal padding before anything is published. If a sentence cannot be read once and understood, it goes back to the drafting desk for simpler wording.

Regional wording checks

Rules differ across supported regions, so our team checks the text against what applies where you hold the account and flags any paragraph that needs a regional version.

Payment wording verified

Every mention of JazzCash, Easypaisa, SadaPay, NayaPay or Raast is checked against the fields those rails actually send us, so the page describes real data, not guesses.

Corrections from account holders

If a paragraph does not match what you have seen on your own account, tell us. We open the account, look at the case, and reword the clause where it is genuinely wrong.

How Our Sibling Pages Stay Consistent

We keep this policy, our account terms and our cookie page aligned, so the same word means the same thing on all of them. Definitions, contact routes and...

Account terms
Both pages use the same definitions for account holder, verified profile and closed account. Where this policy says we delete a record, the terms page repeats that commitment word for word.
Cookie settings
Cookie categories here match the toggles on the settings page, so switching off analytics in one place is reflected in the other without you needing a second request.
Security and login
Device tracking, session timeouts and resets are described once and linked from here. The data fields listed there are the same fields this policy accounts for.
Withdrawal routes
That page lists the account fields each Pakistani rail needs. This policy explains how long we keep those fields and who can see them, so the two read as one story.
Sportsbook house rules
Settlement and bet-history rules sit there; retention of that history sits here. Both pages quote the same clock for how long records stay on file after an account closes.
Live casino room rules
Room logs and table chat records are covered by the retention wording on both pages, so you are never told two different things about how long a session log lives.
Complaints route
Escalation steps appear on the complaints page, while the address for a data request appears here. Each page links to the other, so the right desk is always within reach.
WHAT YOU SEE HERE

Layout Choices Behind This Policy Page

You should be able to answer a privacy question without reading the whole document, so we built the page around short sections with links you can share. The...

Summary before detail The opening section gives you the shape of the policy...
Downloadable copy You can save a dated copy of this policy from...
Version stamps Every published version carries its own date and number. When...
Direct section links Each heading has its own address. Send that link to...
Mobile-first reading Most people open this page on a phone, so tables...
Region notes in place Where a paragraph applies only in certain supported regions, that...

What People Ask About Their Records

Your name, date of birth, mobile number, email address and the reference your bank or wallet attaches to a JazzCash, Easypaisa, SadaPay or Raast transfer. Nothing beyond what the account needs to run.

We store the transfer reference and the last digits of the wallet number so funds reach the right place. We never hold your wallet password, your PIN or the full number your provider issued.

Financial records stay for the period our audit cycle and local rules require. Chat transcripts, device logs and marketing preferences are removed earlier, usually once they stop serving a purpose.

Yes. Send the request from your registered email address and we gather what we hold, then pass it to you in a readable file. Identity checks apply so nobody else can claim your records.

Only with the providers that make the account work: payment rails, identity checks and the studios whose tables you open. They act on our instructions and cannot use your data for their own campaigns.

Ask us through email or live chat and we freeze the account first. We then delete whatever rules do not require us to keep and confirm in writing what was removed and what remains.