Reference

Privacy Policy for Your jalak4d Account

Our Privacy Policy shows how we handle the details you provide when opening a jalak4d account, checking Live Roulette Diamond or moving between the lobby and your wallet.

Account detailsWallet referencesDevice choicesCookie controls
jalak4d Privacy Policy for Your jalak4d Account
CONTACT PATHS

Privacy Questions Reach Our Account Desk

A direct support path helps you control personal data without guessing where to send a request.

Account access If phone verification or sign-in affects your privacy request, give us the account identifier and the device path you used. We can connect the request to the correct record without asking you to disclose a wallet password.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, tell us the payment rail and approximate transaction reference. We use that context to locate relevant records without requesting complete payment credentials.
Policy requests Ask us to explain, correct or remove eligible personal data through the account support path. We may verify account ownership first, then confirm what action is possible under local law and when the change will take effect.
DATA HANDLING

Six Practical Data Handling Commitments

We keep this Privacy Policy connected to the actions you take, rather than treating privacy as a separate page with no operational detail.

Account records

When you open an account, we use the details needed to create and maintain that account. Phone verification can be used to confirm ownership before we discuss records or process a privacy request.

Payment references

A DANA, OVO, GoPay or QRIS reference may be connected to your account activity so we can match cashier status questions. We do not need your wallet password to investigate a payment record.

Device signals

Your mobile browser or desktop session can provide device and connection signals linked to sign-in security. We use these signals to identify unusual access patterns, not to request unrelated personal content from your device.

Cookie choices

Cookies can keep a session active, remember selected settings and help us understand technical errors. You can manage browser cookie controls, although disabling some cookies may affect account access or saved preferences.

Retention period

We keep personal data for the period needed to provide the requested account service, handle disputes, protect account security or meet a legal duty. When a record is no longer needed, we remove or restrict it.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used. Send the request through account support with enough detail for us to identify you, and we will respond according to applicable law.

Privacy Policy Questions Indonesia Searches

These Privacy Policy answers cover the practical points you may want to settle before opening an account or contacting us. We address what we collect, why wallet references appear, how device data works, and how you can request a correction or deletion. If your situation is not listed, use the account support path and include the smallest amount of information needed to identify your request.

The jalak4d Privacy Policy covers account details, phone verification, device and connection signals, cookies, support messages, lobby activity connected to your account and payment references. It explains why we use each category, how long records may be kept and how you can ask about eligible rights.

Phone verification helps us confirm that an account request comes from the account holder before we discuss personal records or change access details. It also supports account security when sign-in behaviour changes. We use the result for these purposes and handle it under this Privacy Policy.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records used to match account activity. We use these references for status checks and support, not to request your wallet password.

We may receive practical device and connection signals from the mobile browser or desktop session used to access your account. These can include session details and technical indicators linked to unusual sign-in activity. They help protect access and troubleshoot errors without reading unrelated files on your device.

Contact our account support path and state which record appears inaccurate, such as a phone detail or account identifier. We may ask for an ownership check before making changes. We then assess the request under applicable law and confirm whether the correction can be completed.

You can ask us to remove eligible personal data through account support. Some records may need to remain for account security, dispute handling or a legal duty, so removal is assessed under local requirements. We will explain the result and any restriction that applies to your request.

This Privacy Policy is written for access connected with Indonesia and applies where local law permits. Eligibility depends on local law. If you are unsure whether a request or account action is available in your location, contact support before sharing additional personal details.