Reference

Terms & Conditions for Your Indonesia Account

loket88 Terms & Conditions set the rules for opening, using and closing your account, with clear steps for identity checks, wallet records and access where local law permits.

Account eligibilityWallet recordsData and cookiesPolicy requests
loket88 Terms & Conditions for Your Indonesia Account
ACCOUNT HELP

Account Help When Policy Questions Stall

A clear support route helps when a Terms & Conditions question affects login, wallet status or a payment record. Sign in first when you can, then use the account support path beside the cashier area so our team can match your request to the right account entry. Include the relevant date, payment rail and receipt reference, while leaving passwords and verification codes out of your message. If access is unavailable, explain the issue without sending sensitive credentials; we will use the details needed to locate the policy or account step.

Team online

Login access

If a policy check leaves you unable to sign in, contact us through the account help path and describe the exact screen or step shown. We can identify whether the issue concerns account details, a pending check or a local access condition.

Wallet status

For DANA, OVO, GoPay or QRIS records, include the rail used, transaction date and receipt reference. We use those details to compare the account ledger with the status shown beside the cashier path without asking for your wallet password.

Policy changes

You may ask us to clarify a clause or request a correction to your account details through support. State the section name, the change you seek and a safe contact route, so our team can respond to the right policy question.

DATA PRACTICE

How We Handle Account Policy Details

Our Terms & Conditions connect account rules with practical records: the details you submit, the device session used to sign in and the payment reference attached to a wallet or bank action.

Account details

We use the account details you submit to identify your account, apply the stated access checks and respond to a Terms & Conditions request. Keep your phone and profile details current, and tell us if an entry is inaccurate.

Cookies and sessions

Cookies help keep your signed-in session and selected account path working across mobile and desktop. If you block them, a login or policy confirmation may not persist, and we may ask you to repeat that account step.

Account security

Keep your password, phone verification details and wallet credentials private. Our terms do not treat a message containing a code as proof of ownership, so contact support through the account path if access looks unfamiliar.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained with the related account record. This lets us compare receipt details and status history when a policy or payment question is raised.

Retention requests

We keep records for the period needed to apply the Terms & Conditions, resolve account questions and meet applicable legal duties. You can ask support what record a request concerns and whether a change or removal can be considered.

Correction path

To request a correction, name the account field or policy wording, explain the issue and provide a safe reply route. Do not send passwords or wallet codes; we may request an account check before changing protected details.

Terms & Conditions Questions You May Search

Most account questions come down to access, records, changes or the effect of a policy check. These answers summarise how we apply the Terms & Conditions in practical situations, including local eligibility, wallet references and requests about stored account details. Read the full wording before confirming your account, and contact us when a clause does not match your situation.

They cover account creation, accurate details, access checks, wallet and bank references, acceptable account use, data handling, cookies, policy changes and closure steps. The full Terms & Conditions apply to your account activity where local law permits and should be read before confirmation.

Yes. Access and eligibility depend on local law. You are responsible for checking whether account use is permitted where you are located, while we may pause access if a required regional or account check cannot be completed.

Verification helps us connect the account to the correct details and review an unusual login or payment record. We may ask for a phone confirmation or another account step described in the Terms & Conditions before restoring access.

The payment rail, date, receipt reference and account status may be recorded together so we can check a wallet question. A DANA or QRIS receipt does not by itself change the Terms & Conditions or bypass an account review.

Yes. Send the field name, the correction requested and a safe contact route through account support. We may verify ownership before making a protected change, and we will explain if a record must remain for legal or account reasons.

Cookies can preserve your signed-in session and remember a policy confirmation on the same device. If cookies are blocked or cleared, you may need to sign in again and repeat the confirmation step before continuing.

Name the relevant clause, describe the question in your own words and include the account or payment date when it matters. For DANA, OVO, GoPay or QRIS records, add the receipt reference, but never send passwords or verification codes.