Reference

jalak4d Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, or check DANA and QRIS status beside titles such as Live Baccarat.

Account dataWallet recordsDevice choicesPolicy requests
jalak4d jalak4d Privacy Policy for Your Account
CONTACT PATH

Get Clear Help With Privacy Requests

A clear contact path helps you ask about the Privacy Policy without searching through payment screens.

Account access If you cannot reach your account, use the displayed support route and provide the…
Wallet reference For a DANA, OVO, GoPay, QRIS, or bank transfer question, send the payment reference…
Data request Ask for access, correction, or deletion through the listed contact route.
DATA PRACTICE

Know What We Do With Your Details

We keep the Privacy Policy practical by connecting each data use to an account action you can recognise.

Collection purpose

We collect account, phone verification, device, activity, and payment-reference data for stated service needs.

Cookie choices

Cookies can keep a session active and remember selected settings. Your browser controls available cookie choices, although refusing some cookies…

Account security

Phone verification and sign-in signals help us protect account access.

Retention approach

We retain records for the period needed for account support, payment matching, security checks, and legal duties.

Correction requests

You can ask us to correct inaccurate account details through the contact path shown after sign-in.

Policy contact

Questions about the Privacy Policy belong in the account support route, including requests about device data, cookies, retention, or a…

Find Privacy Policy Answers Before Opening

These Privacy Policy answers cover the account steps you are most likely to ask about before using jalak4d from Indonesia. We explain what data is collected, how wallet references are handled, how to request changes, and what happens when you contact us. If your question is not listed, use the account support route and include only the details needed to locate your record.

The Privacy Policy covers account creation, phone verification, sign-in, device signals, cookies, lobby activity, payment references, support messages, retention, and requests to access or correct your records.

We may collect details needed for account access and phone verification, plus device, browser, activity, and support records. The exact fields depend on the account step and the request you make.

No. Payment handling may include a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference for status matching. We do not ask for your wallet password through support.

Use the support contact path shown in your account and ask for a data copy under the Privacy Policy. We first confirm account ownership, then explain the available response and format.

Yes, you can request a correction through the listed account contact route. Include the field that needs changing, and complete any phone verification needed before we update the record.

Cookies can support sign-in continuity and saved preferences. Your browser provides available controls, but refusing necessary session cookies may prevent some account or policy settings from working.

It can. Our response to an access, correction, or deletion request depends on local law, account verification, and any retention duty that requires a record to remain available.