Reference

loket88 Privacy Policy for Your Account

loket88 Privacy Policy explains what we collect when you open an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesContact route

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

loket88 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details supplied during account creation, including your contact details and phone verification status, plus sign-in records such as device type, browser path and approximate connection data. It also covers transaction references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account

1
activity. We use this material to operate account access, match payment status and investigate support requests, not to create a separate profile unrelated to your account. We keep records only for operational, security or legal needs, then remove or anonymise them when those needs end. You
2
can ask us what we hold, request a correction or ask about deletion where local law permits. Eligibility and access depend on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Get Clear Answers About Your Data

A clear contact route helps when a Privacy Policy question overlaps with account access or a wallet receipt.

HANDLING IN PRACTICE

How loket88 Handles Privacy Requests

Privacy work follows the same account path you use to reach the lobby from a phone or desktop browser.

Account collection

When you open an account, we collect the contact and verification details needed to create access. Phone verification confirms that the account step belongs to you before account records are displayed.

Device activity

Sign-in records can include browser type, device path, connection details and time of access. These signals help us spot unusual account use without requiring access to unrelated files on your phone or computer.

Payment matching

A payment reference helps us match DANA, OVO, GoPay, QRIS, bank transfer or virtual account status to the correct account. We do not need your wallet PIN to check that reference.

Cookie choices

Cookies can keep your session active and remember selected page settings. You can adjust cookie controls in your browser, although turning some off may require another sign-in on the mobile path.

Retention period

We retain account, device and transaction records only while needed for account operation, security checks, support handling or legal duties. After that point, records are deleted or changed so they no longer identify you.

Change requests

You can request a correction, copy or deletion through the account support route. Include the affected field or record, and we will verify the request before explaining what local law allows us to change.

Privacy Policy Answers Before Access

These Privacy Policy answers focus on the searches we hear before an account is opened or a payment is checked. We explain the account step, mobile browser records, wallet references, cookies and request routes in plain terms. If a question concerns eligibility or access, the answer depends on local law, and support can explain the available path without asking for a password or wallet PIN.

It covers account details, phone verification, device and browser records, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to confirm account ownership before access to account records. It also helps support locate the correct account when you ask about a wallet status or a Privacy Policy request.

Yes. The same policy applies when you sign in through a mobile browser, including the device type, browser path and session records needed to protect account access. Eligibility depends on local law.

We use the payment reference, amount status and date to match a DANA or QRIS transaction with your account. We do not ask for your wallet PIN or one-time verification code.

Yes. Contact support from the signed-in account path, identify the field or record, and complete the identity check. We can provide a copy or correction where local law permits.

We keep account, device and transaction records while they serve account operation, security, support or legal needs. When those needs finish, we delete or anonymise the relevant records.

Use your browser cookie controls or contact support through the account path. We can explain which session settings are affected; disabling cookies may require another sign-in on your device.

loket88 Privacy Policy for Your Account

Get Clear Answers About Your Data

How loket88 Handles Privacy Requests

Account collection

Device activity

Payment matching

Cookie choices

Retention period

Change requests

Privacy Policy Answers Before Access

01 What does the loket88 Privacy Policy cover?

02 Why does loket88 collect phone verification data?

03 Does the Privacy Policy apply on mobile browsers?

04 How are DANA and QRIS records used?

05 Can I request a copy or correction of my data?

06 How long does loket88 keep account data?

07 How do I ask about cookies in the Privacy Policy?

Related Pages