Reference

h5.g668 Privacy Policy For Indonesia Access

h5.g668 Privacy Policy explains what we collect when you create an account, sign in, browse Lightning Roulette or use DANA and QRIS, and why each data point is…

Account clarityWallet recordsDevice choicesPolicy contact
h5.g668 h5.g668 Privacy Policy For Indonesia Access
POLICY HELP ROUTES

Wallet Status And Policy Help

A clear contact path matters when your account record or wallet status looks unfamiliar. We use support conversations to locate the relevant policy issue, confirm the account step involved and explain what…

Account access Contact support through the account help route when phone verification or a sign-in record looks wrong. We use your registered contact detail to locate the correct profile before discussing personal data.
Wallet records For a payment-status question, provide the wallet name and transaction reference rather than a full password or security code. We can then trace the relevant DANA, OVO, GoPay or QRIS entry.
Policy requests Ask support for a copy, correction or deletion assessment through your account contact route. We will explain identity checks, available action and any records that must remain for lawful account handling.
HANDLING YOUR RECORDS

How Lightning Roulette Data Is Handled

We treat each data category according to the account task that created it. A sign-in from your phone, a session around Lightning Roulette or a receipt from QRIS can produce different records…

Account details

We collect contact and verification details when you open an account or confirm your phone. These details help us connect your requests to one profile and prevent another person from changing your records.

Device signals

Your mobile browser may send device type, operating system, language and sign-in time. We use these signals to recognise unusual access and to keep the account path consistent across phone and desktop.

Cookie choices

Cookies can remember session settings and help pages load the correct account state. You can manage cookies in your browser, although refusing necessary cookies may interrupt sign-in or policy access.

Payment matching

Payment records contain method, amount reference and status rather than your wallet password. For DANA, OVO, GoPay, QRIS or bank transfer, we compare the reference with the account request.

Security controls

We use phone verification, sign-in checks and restricted account access to reduce unauthorised changes. Never send a password, one-time code or wallet PIN in a support message.

Retention requests

You can ask how long a record is kept, request a correction or ask whether deletion is possible. Send the request from your registered contact route so we can confirm ownership first.

Privacy Policy Questions For Your Account

These answers address the Privacy Policy questions that usually arise before you open an account or connect an Indonesian wallet. If your situation is not covered, contact us from the registered account route and describe the specific record, device or payment reference involved.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with your use of h5.g668. It also explains access requests, corrections, retention and contact steps.

Phone verification helps us connect a new account step to you, reduce duplicate or unauthorised access and confirm ownership before discussing personal records. We do not need your wallet PIN for this check.

Yes. The Privacy Policy explains how we receive method, reference and status data for DANA, OVO, GoPay and QRIS. The wallet provider separately controls data processed inside its own service.

We may receive device type, operating system, browser language, sign-in time and related security signals. These details help us identify unusual account access and support the mobile path from login to the lobby.

Yes. Contact us through your registered account route and state whether you want a copy, correction or deletion assessment. We may confirm ownership first and explain any records that must remain.

Retention depends on the record and its purpose. Transaction references may remain for accounting, payment disputes or security checks, while data no longer needed for those purposes may be removed or de-identified.

Yes. Access and eligibility depends on local law. If you are in Jakarta, use the same policy contact route as any other Indonesian account, and ask us when a regional question applies.