Reference

Open laga88 Privacy Policy for Your Account

Our Privacy Policy explains how we handle the account details connected with DANA, OVO, GoPay and QRIS, including verification records used before account access.

Clear data purposesWallet-linked account recordsCookie and device choices
laga88 Open laga88 Privacy Policy for Your Account
CONTACT PATHS

Contact Us About Privacy Policy Questions

A clear contact path helps when you want to ask about a record rather than a lobby matter. Use the support route shown beside account access and the cashier path, and include the phone or email connected with your account. We use those details to locate the right record, while you should avoid sending a wallet password or one-time verification code.

Team online

Account data request

Ask us to identify the account data linked with your phone verification step. Include your account reference so we can separate your request from another DANA, OVO, GoPay or QRIS payment record.

Cookie question

Contact us if a browser setting changes how the Privacy Policy page remembers your choices. Tell us whether you used a phone or desktop browser so we can explain the relevant cookie control.

Correction request

Send a correction request through the account support path when your contact detail is outdated. We may ask for a phone verification step before changing a record connected with account access.

DATA PRACTICES

Explore How laga88 Handles Your Data

Our handling steps follow the account journey: we receive details during account creation, use selected device signals during sign-in, and connect payment references only to the account action…

Account collection

We collect contact and verification details when you create or access an account.

Wallet references

A DANA, OVO, GoPay or QRIS reference can be attached to the relevant account action for payment matching.

Device signals

Your browser type, device path and sign-in signals may be used to spot an unusual access attempt.

Cookie choices

Cookies can retain settings that help the Privacy Policy page and account route work as expected.

Retention requests

We keep records only for the stated account, security, dispute or legal purpose, subject to applicable requirements.

Policy changes

If this Privacy Policy changes, we will present the updated wording on the policy page.

Find Answers About Privacy Policy Access

These Privacy Policy answers focus on the questions you may have before opening an account or sending a data request. They cover account records, local wallets, cookies, device access and the practical route for asking us to correct or explain something.

It covers account creation, phone verification, sign-in signals, cookies, support contacts and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use phone verification to confirm account access and help prevent a privacy request from reaching the wrong record. We do not ask you to share a one-time code with support.

Yes. The Privacy Policy explains how a DANA or QRIS reference may be matched with an account action. Wallet passwords and one-time codes should never be sent through the support route.

You can send a correction request through account support and include the phone or account reference connected with the record. We may verify account ownership before making a change.

Cookies may remember selected settings in your browser. You can change them through browser controls, but removing cookies may require you to choose policy or account settings again.

You may ask about deletion where local law permits. Some account, security, dispute or legal records may need to remain, and we will explain the reason when deletion cannot be completed.

Yes. Account access and some data requests depend on local law. We apply the policy to supported Indonesian access where local law permits and explain any limits through the contact path.