Reference

Open with clear Legal terms here

klikme88 puts Legal terms, account duties and data choices beside the access path, so you can understand the conditions before opening an account.

Policy-first accessIndonesia account rulesWallet checks explainedMobile and desktop path
klikme88 Open with clear Legal terms here
POLICY HELP PATH

Check login and wallet policy help

If a Legal question affects your account, start from the support route beside the login and cashier areas. We ask you to include the account phone detail, the relevant policy heading and any payment receipt reference, so our team can identify the issue without asking you to repeat the whole case. In Yogyakarta and other Indonesian locations, access still depends on local law. Keep your browser open on the same device while the status is checked.

Team online

Account access

Use the account support path when a phone verification step, login detail or policy acceptance screen does not complete. We can point you to the relevant Legal wording and explain which account detail needs correction before access continues.

Wallet status

For DANA, OVO, GoPay or QRIS questions, send the payment receipt and the time shown in your account. We use those references to separate a wallet status question from a wider Legal or account-security request.

Policy request

Ask us to clarify a clause, record a correction request or explain the route for a data question. Include your account phone detail and preferred contact route, and avoid sending passwords or one-time verification codes.

DATA CARE PRACTICE

Protect account data before using DANA

Legal care is practical: we separate account access, payment status and policy requests so each question reaches the right check.

Data handling

We use the details attached to your account to process access, verify a phone step, investigate a payment status and answer a Legal request. Send only the details needed for the case, and never place a password or one-time code in a support message.

Cookie choices

Cookies can help keep an account session working and remember selected access settings. You can review cookie controls in your browser; blocking some cookies may require you to repeat login or policy acceptance steps on the next visit.

Account security

Keep your phone, password and verification messages private. If an account detail looks unfamiliar, stop the cashier or lobby action, sign out from other devices where possible, and contact support with the affected account detail rather than sharing access codes.

Record retention

Payment receipts, account changes and support exchanges may be kept for the period needed to resolve disputes, maintain security and meet applicable legal duties. Ask us which record or category you are asking about so we can route the request accurately.

Correction requests

If your phone detail, name or other account record is wrong, send a correction request through support. We may ask for a matching account step before changing it, because a quick change without verification could expose the account to another person.

Contact ownership

The account owner should make Legal, data and access requests directly through the support path. We may limit what can be disclosed until ownership is checked, particularly when the request concerns wallet activity, bank transfer records or another device session.

Browse answers about Legal access

These Legal answers focus on the questions you are most likely to have before opening an account or asking us to change account data. We keep the route practical: read the clause, complete the matching account step, and contact support with a receipt or account reference when a wallet or access check is involved. If a rule applies differently to your location, access depends on local law.

The Legal page covers account access, accurate account details, policy acceptance, data handling, cookies, security checks, record retention and request routes. It also explains why DANA, OVO, GoPay, QRIS and bank records may appear in an account or support check.

Yes. Access or eligibility depends on local law, so you must check whether the service is available for your location before continuing. We may ask for account details or pause access when a location, identity or policy condition cannot be confirmed.

Send a data correction request through the support path and name the field that needs changing, such as a phone detail. We may ask you to complete an account verification step first, then explain the next action without requesting your password or one-time code.

We may use your account reference, phone detail, payment receipt, transaction time and selected rail to investigate a status question. For DANA, OVO, GoPay or QRIS, provide only the receipt details needed to match the record.

Yes. You can ask how cookies support a login session or selected access setting, and you can adjust browser controls. Blocking cookies may cause another login or policy acceptance step, but it does not remove the need to follow the Legal terms.

We link a request using the account phone detail, the policy heading and any relevant receipt reference. This helps us avoid mixing your case with another account. We still ask you not to send passwords, one-time codes or full wallet access details.

Contact us through the policy support route and identify the record category, such as an account change, support exchange or bank transfer receipt. We can explain the applicable handling route and may first check that you own the account.