Reference

Legal rules for your kno 89 account

kno 89 Legal sets out how account access, identity checks, wallet records and policy questions are handled for Indonesia.

Local-law accessPhone verificationPrivacy controlsPolicy support
kno 89 Legal rules for your kno 89 account
CONTACT ROUTES

Where to ask Legal questions

A clear contact route matters when you need a policy answer before using your account. We direct Legal questions through our support channel so the request can be matched to your account record, wallet status or access question. Include the email or phone detail linked to your account, the relevant policy heading, and any receipt reference from DANA, OVO, GoPay or QRIS. We do not ask you to send a password or one-time verification code. Access remains subject to local law while our team checks the details.

Team online

Account policy desk

Use the account support route for questions about Legal wording, phone verification, account ownership or access eligibility. Include your registered contact detail and the policy heading you are asking about. We can explain the process without asking for your password or one-time code.

Wallet evidence path

If your Legal question concerns a wallet record, attach the transaction reference and name the rail used, such as QRIS, DANA or bank transfer. We compare the receipt with the account record before discussing status. Remove passwords, PINs and full card details from any message.

Access clarification

For eligibility questions, tell us your country or region and the access wording you are checking. We will explain that availability depends on local law and identify the applicable policy path. Do not try to bypass a location or account control while waiting for a response.

DATA PRACTICES

How we handle Legal requests

Legal requests are handled against the account details and records needed for the specific question. We use the minimum practical context to check identity, payment ownership, policy access or a requested change.

Account data

We use your registered contact detail, verification result and account activity only as needed to handle access and Legal requests. Keeping your phone number current helps us match a policy question to the correct account. Tell support if a stored detail is inaccurate.

Cookies and sessions

Cookies can keep your browser session connected to the account path and remember required settings. You can manage cookies through your browser controls, although blocking essential cookies may interrupt sign-in or policy access. We do not treat a cookie as permission to request your password.

Wallet records

Transaction references from DANA, OVO, GoPay, QRIS, virtual account or bank transfer may be kept to reconcile ownership and account status. A receipt helps us investigate a mismatch, but it should not contain your PIN, password or one-time verification code.

Account security

Phone verification is part of the account access path where required. Keep your phone, email and device lock private, and contact us if you see an access attempt you did not make. We will not ask you to disclose a secret code in a support conversation.

Retention rules

Some account, payment and support records may remain for the period required to resolve disputes, meet legal duties or protect the service. If you ask why a record remains, we will identify the relevant reason and explain what can be changed or removed.

Change requests

To request a correction, access copy or policy-related data change, contact support from the email or phone linked to your account. State the exact request and the record involved. We verify ownership first, then confirm the action or explain its legal limitation.

Answers about kno 89 Legal

These Legal answers cover the questions we expect you to ask before opening an account or sending a policy request. They explain local access, account checks, privacy, payment evidence and contact steps in plain terms. If your situation is not covered, send the policy heading and your registered contact detail to support so we can route the question correctly.

Access depends on local law. Before opening an account, check whether this type of service is permitted in your location and follow the current Legal wording on our site. We may also use account and phone verification steps before access is enabled.

You need to provide accurate account details and complete phone verification where required. We may compare your account name with a payment record when checking wallet ownership. Never send a password or one-time code to support, even when asking about Legal.

Send the request from the email or phone linked to your account and identify the exact record or policy issue. We verify ownership, check whether retention rules apply, then confirm the correction, access request or removal step available for that record.

DANA and QRIS references can help us match a receipt to the correct account and investigate a status mismatch. We use the reference and relevant account details for that check. Remove PINs, passwords and one-time codes before sending any receipt.

Yes. Contact support with the account detail linked to you and name the record, such as a payment receipt or access request. We will explain whether it remains for dispute handling, legal duties, security or another stated retention reason.

Use the account support route and state that your question concerns Legal access, then include your registered contact detail and region. We will explain the applicable policy path. Availability remains subject to local law, and you should not attempt to bypass access controls.

Contact support from your linked email or phone and describe the exact correction or change. Include the policy heading and account detail involved, but not your password or verification code. We verify ownership first and then confirm the next available action.