Reference

loka55 Privacy Policy For Your Account

Our Privacy Policy explains how we handle the account details, device signals and wallet references you provide when you open and use loka55.

Account clarityWallet data controlCookie choicesIndonesia access
loka55 loka55 Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Account Support

A clear contact path helps you ask about your Privacy Policy rights without explaining your whole account history.

Account request Use the account support path to ask how we hold your registration details, phone…
Wallet question For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and…
Access concern If a new phone, browser or sign-in location caused an account check, contact us…
DATA PRACTICE

How We Apply This Privacy Policy

We keep the Privacy Policy practical: each data use should connect to account access, payment checking, security, site operation or a request you make.

Data we receive

We receive details you enter for an account, phone verification results, support messages and payment references. We can also receive technical signals such as browser type, device path, login time and pages used, which help us keep account activity connected to the correct session.

Cookie settings

Cookies may remember a login preference, maintain a session or show whether a page works correctly. You can manage cookies through your browser controls, although disabling some cookies may require you to repeat an account step or sign in again on your device.

Account security

Phone verification adds an account check before access, and unusual device behaviour may prompt another confirmation. Keep your password and one-time code private. Our support path will not need your wallet PIN to discuss a DANA, OVO, GoPay or QRIS reference.

Payment records

A payment record can include a rail name, amount reference, status and time needed to match the account request. Bank transfer and virtual account checks may require this trail. We use it to investigate a missing status without asking you to reveal banking login credentials.

Retention questions

We retain account, security and payment records only for the period needed for the stated purpose, account support and applicable legal duties. The period can differ by record type. Ask us to explain the retention basis for a specific item instead of sending a complete identity document.

Rights requests

You can contact us to ask for access, correction, deletion where available, or clarification about a data use. Tell us which request you are making and the account detail used to identify you. We may verify ownership before taking action, and local law can affect the result.

Privacy Policy Questions About loka55

These Privacy Policy answers focus on the account steps Indonesian customers are most likely to question before opening an account. We explain the role of phone verification, cookies, device signals and local wallet references in plain terms. If your situation is unusual, contact account support with the specific record or access event, and we can direct the request to the appropriate privacy path.

The loka55 Privacy Policy covers details you enter during account creation, phone verification status, support messages and account activity needed for access and security. We use those records for the stated account purpose, not as a public profile. You can ask which personal details are connected to your account.

Yes. The Privacy Policy covers payment references such as the wallet or QRIS rail, request time, status and matching details. These records help us check a cashier issue, while wallet passwords, PINs and one-time codes should remain private. Bank transfer and virtual account references can follow the same process.

Phone verification helps us connect an access request with the account holder and reduce mistaken or unauthorised access. The Privacy Policy treats the verification result as account-security data. If your phone path changes, use account support and describe the issue without sending a password or one-time code.

Cookies can keep a session active, remember a page setting or help us understand whether an account page loads correctly. Browser controls let you remove or block them. The Privacy Policy explains their purpose, and blocking some cookies may make you repeat login or verification steps on your device.

You can contact us to ask for access to personal data linked to your account or to correct an inaccurate detail. Identify the account using its registered contact route. We may verify ownership first, and the response or available action depends on local law and the type of record requested.

Retention depends on the record and its purpose. Account-security events, support history and DANA, OVO, GoPay, QRIS, bank transfer or virtual account references may need to remain available for account support and applicable legal duties. Ask us about a specific record and we will explain the relevant basis.

Use the account support path and state whether you want access, correction, deletion where available, or an explanation of data use. Include the registered contact detail and a short description of the request. Do not send wallet credentials. We may confirm ownership before discussing personal information.