Reference

lambe100 Privacy Policy for Indonesian Accounts

Our Privacy Policy explains how we handle your account details, device signals, cookies and wallet records when you access lambe100.

Account dataCookie choicesWallet recordsMobile access
lambe100 lambe100 Privacy Policy for Indonesian Accounts
CONTACT PATHS

Privacy Policy Help for Wallet Status

A clear contact path matters when your Privacy Policy question involves a wallet record, a device sign-in or a phone verification step. We ask you to include the account detail that helps us locate the request, while leaving out passwords and one-time codes. Our support route can then address access, correction and retention questions without exposing unnecessary account data.

Team online

Account access

Ask us to check a phone-verification or sign-in record when your account access looks different on mobile and desktop. We use the account details you provide to locate the correct Privacy Policy request.

Wallet record

For DANA, OVO, GoPay or QRIS questions, share the transaction reference rather than your wallet password. We can use that reference to clarify which payment record the Privacy Policy covers.

Data request

Request a copy, correction or removal of eligible account data through our site support route. We may ask for account verification first, so a change is applied to the correct lambe100 profile.

DATA PRACTICES

Privacy Policy Controls for Mobile Accounts

Our Privacy Policy is applied through practical account controls rather than broad promises. We separate sign-in details from payment references, record security events when needed and use cookie settings to support the…

Data handling

We use account details to provide access, confirm phone ownership and respond to support requests. Payment references from DANA or QRIS help us trace status without requiring us to store your wallet password.

Cookie controls

Cookies can remember a sign-in state or preserve essential page settings. Your browser controls can clear them, although clearing required cookies may send you back through phone verification.

Account security

We monitor sign-in patterns, device changes and verification events to protect your account. Never send us a password or one-time code; support can work from your account reference instead.

Retention period

We retain account, support and wallet records only while they serve an operational, security or legal purpose. When that purpose ends, records are deleted or changed so they no longer identify you.

Access requests

You can ask what personal data we hold, request a correction or ask whether removal is available. We verify the request against your account before changing any record linked to you.

Policy contact

Use the support contact shown on our site for Privacy Policy questions, including cookie choices, account records or wallet references. Include your registered contact detail and a short description of the request.

Privacy Policy Answers for lambe100 Accounts

These Privacy Policy answers focus on the account actions you are most likely to take: creating access, checking a wallet record, changing a device or asking us to handle your data. Each answer points back to a practical request route rather than describing unrelated lobby features.

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

We use phone verification to confirm account ownership and help protect sign-in access. If your number changes, contact support after verification so we can assess the requested account update.

Yes. The Privacy Policy covers payment references and status checks linked with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity.

Where local law permits, you can ask what eligible account, cookie, support or payment-reference data we hold, why it is used and whether a correction or removal request can be made.

Use the support contact shown on our site and describe the record that needs correction. Include your registered contact detail, but do not send a password or one-time verification code.

No. The same Privacy Policy applies when you sign in from a mobile browser or desktop. A new device may trigger security checks or phone verification before account access continues.

We retain data while it supports account operation, security, support or a legal need. After that purpose ends, we delete or anonymise eligible records under the policy process.