Reference

lampu4d Privacy Policy for Your Account

lampu4d Privacy Policy explains what we collect when you create an account, verify your phone, browse Sic Bo or Aviator, and use DANA or QRIS.

Account clarityWallet data contextMobile session careRequest paths
Explore Our Lobby Read FAQ
lampu4d lampu4d Privacy Policy for Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear support route helps you act on this Privacy Policy without searching through unrelated account screens. From Jakarta or elsewhere in Indonesia, contact us through the support channel shown after account access and include the email or phone number attached to your account. We use the account step and payment reference only to locate the right record before responding.

Team online

Account support

Ask about a stored account detail, phone verification record, or sign-in event through our account support channel. We may request an account identifier before discussing personal data.

Wallet query

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the receipt reference and date. We use those details to trace the relevant payment record.

Privacy request

Request access, correction, or deletion by naming the account detail concerned. We verify the requester first, then explain the available action under the law applying to your account.

DATA HANDLING

What We Do With Your Records

We keep this policy practical by connecting each data category to an account action. A phone check supports account access, a device signal helps us examine an unfamiliar session, and a wallet…

Account details

We use your submitted name, contact detail, and phone verification status to create and protect your account. We do not need your DANA, OVO, or GoPay password to match wallet activity.

Device signals

When you sign in from a mobile browser or desktop, we may record device type, browser version, session time, and approximate network location to investigate unusual access.

Cookies

Cookies can keep a session connected, remember a language or page setting, and help us identify technical errors. You can manage cookie controls through your browser settings.

Account security

Phone verification and sign-in records help us check account ownership. If a session looks unfamiliar, we may ask for another account step before discussing personal or wallet-related details.

Retention period

We retain records only while they support account operations, dispute handling, security checks, or a legal requirement. When a record is no longer needed, our process removes or de-identifies it.

Changes and requests

To correct a phone number, request a copy of stored details, or ask about removal, contact support with your account identifier. We confirm identity before making a change.

Privacy Policy Questions We Hear

These Privacy Policy answers address the account, device, cookie, and payment-record questions you may have before opening an account. If your request concerns a particular DANA, QRIS, or sign-in record, include its reference so we can locate the correct entry.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

No. We use the payment reference needed to match an account transaction. Your DANA, OVO, GoPay, or banking password remains with the relevant payment provider and is not required for our account record.

Device type, browser version, session time, and approximate network location help us investigate unfamiliar sign-ins and technical errors. These signals are handled as part of account security and service support.

Yes, you can contact our support channel and ask for the account details held about you. We first verify account ownership, then respond according to the law applying to your account.

Send a correction request through account support and identify the phone number or profile field concerned. We may require a phone verification step before changing the account record.

We keep payment references while they support reconciliation, security checks, disputes, or legal requirements. After that need ends, the record is removed or de-identified through our retention process.

Cookies can support session continuity and page settings, but you can manage them in your browser. Blocking some cookies may affect account access, while the policy still explains how related data is handled.

Related Pages

lampu4d Indonesia Sportsbook Account information FAQ About Us