Privacy Policy for your hg777 account
Live Baccarat, cricket markets and slot rooms share one account record at hg777, so this Privacy Policy explains how we collect, use, secure and retain your data. Read...
How we handle your account data
This Privacy Policy sets out how hg777 handles personal data when you create an account, verify access, contact support, use the lobby or request a payout check in supported regions. We collect only what we need for account operation, security checks, transaction tracing and service messages. That can include your name, mobile number, login record, device signals, payment reference, support messages and
activity linked to your account. We use these records to keep your wallet accurate, answer privacy requests, detect unusual access and meet record keeping duties that apply where local law permits. We do not sell your personal data. When partners help us process payments, host tools or provide fraud screening, we limit access to the task they perform for hg777.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Where to ask privacy questions
Your privacy request should reach the team that can read account records and answer without exposing extra data. We separate account help from privacy handling, then ask for enough detail to find the correct record. Do not send passwords or full wallet screenshots; a transaction reference or registered mobile number is usually enough.
Privacy inbox
Email us for access, correction or deletion requests. Include your registered mobile number, the issue date and the part of the Privacy Policy you are asking about so our team can trace the correct account record.
Live chat handoff
Use chat only to start a privacy case or check its status. Our chat team will not ask for passwords, and deeper requests move to a privacy inbox so account records stay controlled.
Payment reference help
If your privacy question involves JazzCash, Easypaisa, SadaPay, NayaPay or Raast, share the reference code only. We use that code to match records without collecting full wallet access details.
How we keep policy wording reliable
We write this Privacy Policy from our own account flow, not from copied legal text. The wording reflects how registration, wallet checks, live table sessions and support messages...
Account flow mapping
We map each privacy statement to a real account step, such as mobile verification, wallet reference matching or device access...
Payment rail context
JazzCash, Easypaisa, SadaPay, NayaPay and Raast can create reference data. Our policy explains why those references are stored, who can...
Access security checks
Login records, device signals and failed access attempts help us spot unusual activity. The policy explains this use so you...
Limited team access
Only trained staff with a work reason can view personal account records. We log access, separate support from payment checks...
Clear retention approach
We keep records only for account operation, dispute handling, security checks and duties that apply in supported regions. When data...
Change tracking
Policy edits are dated internally and checked against live account screens. If wording changes in a material way, we place...
Consistency across our legal pages
This page sits beside our terms and cookie pages, but it has a narrower role. It focuses on personal data: what we collect, why we use it, how...
Privacy layout points to notice
We designed this Privacy Policy so you can find the account data point you care about quickly. The layout follows your journey: account creation, wallet reference checks, lobby...