Reference

Privacy Policy For Your live555 Account

Our Privacy Policy explains what account details we collect, why we use them, and how you can ask us to correct or remove eligible data.

Account clarityWallet data careCookie choicesPolicy requests
live555 Privacy Policy For Your live555 Account
CONTACT YOUR WAY

Privacy Help Near The Cashier

A clear contact path matters when a Privacy Policy question starts with a payment receipt or account check.

Account route Use the support path inside your account for a Privacy Policy request linked to phone verification or access records. Include the account detail needed to locate the case, but do not send a password or a full wallet security code.
Cashier context If your question follows a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account receipt, mention the rail and reference shown to you. This gives us a practical starting point without asking you to repeat unrelated personal details.
Data request Ask us to access, correct, or remove eligible personal data through the same account support path. We may verify that the request comes from you before changing records, especially when it could affect account access or a payment reconciliation.
DATA HANDLING

Inside live555 Privacy Controls

We handle this policy area through practical controls rather than broad promises. Account access uses phone verification, wallet records are tied to the relevant transaction reference, and browser cookies help preserve a…

Account details

We collect details needed to create and maintain your account, then use them for access checks and account support. Phone verification helps us distinguish an account request from an unverified attempt to enter the lobby.

Wallet references

A DANA, OVO, GoPay, or QRIS reference can be used to match a cashier event with your account. Bank transfer and virtual account records serve the same reconciliation purpose when you ask us to check a receipt.

Browser cookies

Cookies and similar browser storage may remember a session, language setting, or consent choice. You can manage cookies through your browser controls, although removing them may require you to verify access again.

Access security

We use account checks, phone verification, and case-specific questions before discussing private records. Never share your password or wallet security code in a support message, even when a request appears to concern your account.

Retention choices

We retain records only while they serve an account, cashier reconciliation, support case, or operational requirement. You can ask what we hold and request deletion or restricted handling when the applicable conditions allow that request.

Policy contact

Send a Privacy Policy question through the account support route and describe the record involved. We may ask for a verification step before releasing details or applying a correction, protecting you from changes made by another person.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account situations you are most likely to encounter in Indonesia. We explain the connection between personal data, wallet references, browser behaviour, and account access without turning the page into a general lobby description. If your question is not covered, use the account support route and identify the specific record or request.

It covers account details, phone verification, support messages, cashier references, browser cookies, and records created when you access the service. It explains why we use those details, how long they may be retained, and how you can ask about access, correction, deletion, or restricted handling.

Phone verification helps confirm that an account access request belongs to you. We may use the verification result when protecting account records or answering a Privacy Policy request. It does not mean you should send a password, wallet security code, or unrelated personal details to support.

Yes. A DANA or QRIS reference may be stored with the related account and cashier record so we can check whether a receipt matches your request. OVO, GoPay, bank transfer, and virtual account references can be handled for the same reconciliation purpose.

You can ask through the account support path for access to eligible records or correction of inaccurate details. Describe the specific data you mean, such as a phone number or payment reference. We may verify your identity first, particularly when the request could change account access.

Cookies and browser storage can preserve a session, remember a setting, or record a consent choice. Your browser lets you remove or restrict them. After removal, you may need to complete phone verification again, and some account-related pages may not retain your previous preference.

We keep data while it supports your active account, a cashier reconciliation, a support case, or an operational requirement. Retention can differ by record type. You can ask us to explain a record's purpose and request deletion or restricted use where the applicable conditions permit.

Use the support route inside your account and state whether your question concerns access, cookies, phone verification, or a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record. We may request a verification step before discussing private details or changing stored data.