Reference

Open lambangbet Privacy Policy for Account Clarity

Our Privacy Policy explains how lambangbet handles your account details, device signals and wallet references when you use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet detail contextAccount request pathLocal-law wording
lambangbet Open lambangbet Privacy Policy for Account Clarity
PRIVACY HELP

Check Privacy Questions Through Support

A clear support route helps when your account record, wallet reference or privacy request needs attention. Sign in, open the support link near your account area and describe the request in plain English, including the phone number connected to your account. If you cannot sign in, use the same support route available from the access page and avoid sending a full password or one-time code.

Team online

Data access request

Ask us which account details, device records or payment references are linked to you. We may confirm account ownership before sharing a response, helping keep another person from receiving your records.

Correction request

If your phone number, name or wallet reference needs correction, tell our support desk what changed. We can ask for account details needed to match the request with the correct record.

Account privacy concern

For an unexpected login, unfamiliar device record or unclear DANA and QRIS reference, contact support through the account path. Include the date and visible status so we can trace the event.

DATA PRACTICE

Explore How Our Data Controls Work

Privacy controls work alongside the account steps you already use. We separate login checks from payment references, use session and browser signals to keep the mobile path stable, and explain cookies in…

Account data

We may hold details such as your name, phone number and login record to maintain your account. Phone verification before access helps us connect a privacy request with the right account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data. We use those references to match receipts and status questions without needing your wallet password.

Cookies and sessions

Cookies and similar browser signals can remember session state, device behaviour and basic preferences. You can manage browser cookie settings, though changing them may affect login continuity on mobile.

Account security

We may compare sign-in time, device type and account activity when checking unusual access. Never send us your password or one-time code when asking for privacy help.

Retention approach

We keep records for the period needed for account service, security, payment tracing or applicable obligations. The Privacy Policy explains the purpose-based approach rather than promising one fixed period.

Change requests

You can ask us to access or correct personal data through support. Include your account phone number and request type; we may verify ownership before changing or disclosing any record.

Browse Privacy Policy Questions

These Privacy Policy answers address the account and wallet questions you may have before joining lambangbet. They explain the practical route for data access, corrections, cookies, security checks and contact requests without replacing the full policy text.

It covers account details, phone verification, device and session signals, cookies, payment references, security checks, retention and requests concerning your personal data when you use our services.

We may collect your name, phone number, login records, device type, browser signals and account activity. Payment references from DANA, OVO, GoPay or QRIS may also connect to your account.

Wallet and QRIS references help us match a receipt or payment status with the correct account. We do not ask for your wallet password, and support may verify ownership before discussing a record.

Yes. Use the support path near your account area and request data access. Include the phone number connected to your account; we may complete an ownership check before sharing personal records.

Send a correction request through support and explain whether your name, phone number or payment reference changed. We will assess the request against account security and may ask for confirmation.

Cookies and browser signals can help preserve your login session and basic settings when moving through the mobile path. You can change browser controls, but some account functions may behave differently.

Open the support link from your account area or the access page if you cannot sign in. Describe the concern, date and related account reference, while keeping passwords and one-time codes private.