Reference

liga8et Privacy Policy for Your Account

Our Privacy Policy explains how liga8et handles the account, device and wallet details you provide before you enter Baccarat, ara4d or other available rooms.

Account detailsDevice signalsWallet recordsPolicy requests

Explore Our Lobby Read FAQ

How We Apply This Privacy Policy

liga8et Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details collected when you create or use an account, verify your phone, sign in, contact support or check a wallet transaction. We may connect your account reference with payment status from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account so

1
we can match a receipt to the correct account. Device and browser signals help us recognise unusual sign-in activity and keep an interrupted session from being linked to the wrong account. We do not ask you to send payment credentials through an open chat. Access and
2
eligibility depends on local law, and some data handling may follow requirements that apply to the region from which you connect. This policy applies to our site, its account screens and the support path shown after login. We may update the wording when our handling changes,
3
with the current version available on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP PATH

Privacy Help Through Your Account Path

A clear support route helps you ask what we hold, why we use it or how to correct an account detail.

DATA CONTROLS

Six Controls Behind Your Data Choices

Our handling starts with a narrow purpose: account access, transaction matching, site operation and support for your request.

Account details

We use the details you enter during account creation and the phone verification step to identify your account and help prevent one person’s login or receipt from being attached to another account.

Cookies

Cookies and similar browser storage can keep your session, language choice and policy access working. You can manage browser permissions, but removing them may sign you out or require the phone verification step again.

Device signals

When you move from a mobile browser to desktop, basic device and browser signals can help us spot an unusual sign-in. They are used for account protection and troubleshooting, not as a substitute for your account details.

Account security

Keep your login details private and use the support path rather than sending a password or wallet PIN. If a sign-in looks unfamiliar, tell us through the account route so we can examine the relevant access record.

Record retention

We retain account, support and transaction records only for as long as needed for the purpose described here, account safety and applicable legal duties. When a record is no longer needed, our process removes or de-identifies it.

Change requests

You can ask us to access, correct or assess deletion of personal data through the policy contact path. We may request account verification, explain any legal retention need and confirm the action taken.

Privacy Policy Questions for liga8et

These answers address the Privacy Policy searches we hear most often before an account is opened. They cover the data connected to login, phone verification, payment receipts, cookies, device changes and requests sent through our support path. If your situation is different, use the policy contact route inside your account and describe the exact record or action you want checked.

The liga8et Privacy Policy covers account details, phone verification, browser cookies, device signals, support messages and payment-status records. It applies when you create an account, sign in, check a receipt or send a request through the site’s policy support path.

Phone verification helps us connect you with the correct account before access and helps separate your login from another account. It can also support an ownership check when you request a data copy, correction or change to account details.

Yes. The Privacy Policy covers the payment-status details needed to match a DANA, OVO, GoPay or QRIS receipt with your account. We ask for a receipt reference when needed and do not require you to send a wallet PIN or secret credential.

We may receive basic browser and device signals linked to a sign-in, such as the device type or session details. These signals help identify unusual access and diagnose a page issue when you switch between a mobile browser and desktop.

You can use the policy contact path inside your account to request access or correction. Describe the data concerned and the change you need. We may verify account ownership first, then explain the action or any record that must remain.

We keep personal data for the account, support, security or legal purpose that requires it, rather than for an undefined period. Once that purpose ends and no legal duty applies, the relevant record is removed or de-identified through our process.

The policy page is available through the site, while account access and eligibility depends on local law. If a regional rule affects how we handle a request or account record, we explain that limit through the same support path.

liga8et Privacy Policy for Your Account

Privacy Help Through Your Account Path

Six Controls Behind Your Data Choices

Account details

Cookies

Device signals

Account security

Record retention

Change requests

Privacy Policy Questions for liga8et

01 What does the liga8et Privacy Policy cover?

02 Why does liga8et need my phone verification?

03 Does the Privacy Policy include DANA and QRIS records?

04 What data does liga8et collect from my device?

05 Can I request a copy or correction of my data?

06 How long does liga8et keep personal data?

07 Does access to this Privacy Policy depend on local law?

Related Pages