Reference

Open lcc77 Privacy Policy Clearly

lcc77 Privacy Policy explains what we collect when you create an account, verify your phone, sign in on mobile, or use DANA and QRIS.

Account dataWallet recordsDevice choicesCookie controls
lcc77 Open lcc77 Privacy Policy Clearly
REQUEST A HAND

Contact Us About Privacy Access

Privacy questions should reach the team through a clear account path, not through a payment comment or game message.

Account help Use the signed-in account help route for a Privacy Policy request.
Wallet status For a DANA, OVO, GoPay, or QRIS privacy question, include the payment reference and…
Data request Ask for a copy, correction, or removal review through the same support path.
HOW DATA WORKS

Protect Data Across Your Account

We apply the Privacy Policy to practical moments you can recognise: creating an account, signing in from a new phone, checking a QRIS receipt, or returning to the lobby after a browser…

Account collection

We collect details you enter for an account, such as your phone number, together with the verification result needed to confirm access. We do not need your DANA, OVO, GoPay, or QRIS wallet password to connect a payment reference with your account.

Payment records

A wallet or bank transfer record may show a reference, amount status, route, and time so we can reconcile the account ledger. For BCA, BRI, Mandiri, or BNI transfers, the record is used for matching and support rather than for storing your banking login.

Device sessions

When you sign in on a phone or desktop browser, we may record device and session signals such as browser type, operating system, time, and security events. These details help us ask for another account check when a session looks unfamiliar.

Cookies and choices

Cookies can keep your sign-in flow and selected settings consistent between the lobby and account area. You can manage or clear them through your browser settings; after that, the site may request phone verification again before showing protected account data.

Retention periods

We retain account, security, and payment records only for the period needed for the stated service, dispute handling, security checks, or legal duties. The applicable period can depend on local law, so our support team can explain the reason for a retained record.

Policy changes

If the Privacy Policy changes in a way that affects your account data, we will place the revised wording in the policy area and identify the effective date. Check this page after a major account or payment-flow change so you can see what has been updated.

Find Privacy Policy Answers Quickly

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder: what lcc77 records, how payment references are used, which device details appear, and how to request a change. Read the full policy above for the wider wording, then use account help when your question relates to a particular phone verification or receipt.

It covers account details, phone verification, device and session signals, cookies, payment references, support requests, retention, and policy changes. It applies when you use the account or related wallet flow from Indonesia where local law permits, including activity connected with the listed lobby areas.

No. The Privacy Policy describes payment references and status details used to match DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. We do not need your wallet PIN or banking login for that matching process, so do not send those credentials to support.

Phone verification helps connect an account request with the person trying to access it and supports an extra check when a device session looks unfamiliar. The Privacy Policy treats the verification result as account data and explains its use for access and security.

We may record browser type, operating system, session time, and security events connected with a sign-in. These details help us recognise unusual access and protect account data. They do not require us to collect your device password, wallet PIN, or private messages.

Sign in, open account help near the cashier area, and request access or correction. State the phone number attached to your account and, if relevant, a payment reference. We may verify your account first, then explain the available step where local law permits.

You can submit a deletion request through account help. We will assess which records can be removed and which may need to remain for security, dispute handling, or legal duties. The result and timing can depend on local law and the record involved.

Use your browser settings to view, restrict, or clear cookies. Clearing them can end a remembered session or remove preferences, so the account may request phone verification again. The Privacy Policy explains why cookies support account continuity and which functions may be affected.