Reference

Privacy Policy for Your lcc138 Account

lcc138 Privacy Policy explains how we collect, use and protect details connected with your account, wallet status and device access.

Account dataWallet recordsDevice accessCookie choices
Explore Our Lobby Read FAQ
lcc138 Privacy Policy for Your lcc138 Account
HELP WITH DATA

Three Ways to Ask About Privacy

A clear contact path helps you resolve a Privacy Policy question without guessing where to begin. Use the account help route when your request concerns phone verification, sign-in details or a device session. Use the cashier-related support path when a DANA, QRIS or bank transfer reference needs matching. Include your account identifier and payment receipt only through the available support channel, and remove unrelated personal details before sending.

Team online

Account help

Ask us about the personal details attached to your lcc138 account, including phone verification or a sign-in concern. We may request account identifiers so we can separate your request from another account without asking you to send a password.

Wallet status

For a privacy question tied to DANA, OVO, GoPay or QRIS, send the payment reference shown in your account rather than full wallet credentials. We use that reference to check status and limit the details shared during the response.

Receipt check

If a bank transfer or virtual account receipt is part of your request, keep the receipt number visible and hide unrelated balances. Our support path can use that record to locate the transaction without requesting your banking password.

DATA HANDLING

Six Privacy Controls We Keep Clear

We handle Privacy Policy requests around the account actions you actually take, from phone verification to a mobile sign-in and a wallet status check.

Account details

We use the details you submit during account creation and phone verification to identify your account, respond to requests and maintain access. If a detail is incorrect, contact us through account help with the specific field you want checked.

Cookies

Cookies may support a signed-in session and help us understand page performance. You can manage browser cookie settings on your phone or desktop, although changing them may affect sign-in continuity or the way a Privacy Policy page loads.

Mobile sessions

When you move from login to the lobby on a mobile browser, we may record session and device signals for access protection. These signals help us identify an unexpected session without reading private content from your device.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account help us match a transaction to your account. We use the reference and status needed for that check, not your wallet password.

Retention

We keep account, support and transaction records for as long as needed for account service, security checks or a lawful operational requirement. When a record is no longer needed, our handling follows the deletion process available under local law.

Change requests

You can ask whether we hold a specific account detail, request a correction or ask about deletion eligibility. We may verify phone or account control first, and our response will explain any limit that depends on local law.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we expect before you open an account or send a support request. They explain what happens to account details, cookies, device signals and payment references across the lcc138 access path. If your situation involves a specific transaction, include only the reference needed for us to check it. Any access, retention or deletion request depends on local law.

The lcc138 Privacy Policy covers account details, phone verification, sign-in sessions, cookies, support messages and payment references. It explains why we use those records, how we protect account access and how you can ask about correction, access or eligible deletion.

We may store transaction references and status details needed to match DANA, OVO, GoPay or QRIS activity with your account. We do not need your wallet password for that check. Send only the reference requested through the account or wallet support path.

Phone verification connects the number you provide with your account access and helps us respond to account requests. We may use that confirmation when you ask to change details or investigate a sign-in concern, subject to checks required under local law.

You can contact us through account help and ask what personal data is connected with your account. We may confirm that you control the account before responding. The material we can provide and the timing of a response depends on local law.

State the account detail you want corrected or the record you want considered for deletion, then include your account identifier through the available support route. We check the request before acting and explain any retention reason that applies under local law.

Cookies can preserve a signed-in session and help us measure page performance. Device and session signals can help identify unusual access when you move from a mobile login to the lobby. Browser settings let you manage cookies, but may affect session continuity.

Start with account help for personal data, phone verification or sign-in questions. Use the wallet status route for a DANA, QRIS, GoPay, OVO, bank transfer or virtual account reference. Do not send passwords, full wallet credentials or unrelated documents.

Related Pages

lcc138 Indonesia Sriwijaya Gold Megaways Badminton BWF Tour Bet About Us Access guide