Reference

kelinci88 Legal terms for Indonesia access

Our Legal page explains how account access, identity checks, payment records and policy requests work at kelinci88.

Access termsData handlingPayment recordsSupport requests
kelinci88 kelinci88 Legal terms for Indonesia access
POLICY CONTACT ROUTES

Where Legal questions reach our team

A clear contact path helps when you need a Legal answer rather than a general lobby explanation.

ACCOUNT HELP Use the account support route when you need clarification about Legal access terms, phone…
PAYMENT RECORDS For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the receipt…
DATA REQUESTS Send a data access, correction or deletion request through the account support route.
RECORDS AND CONTROL

How Legal controls protect account records

Legal handling is connected to the practical steps you take on kelinci88: creating an account, confirming your phone, selecting a wallet and contacting support.

DATA HANDLING

We use account details, phone verification data and transaction references to administer access, investigate status questions and answer Legal requests. We do not ask for a wallet password through the support route.

COOKIE USE

Cookies and similar browser storage may help keep your session connected while you move between account pages. You can manage browser settings, although changing them may affect Legal notices or login continuity.

ACCOUNT SECURITY

Keep your registered phone and account credentials private. If access looks unusual, contact us through the account support route and avoid sending full wallet passwords, card details or private authentication codes.

RETENTION RULES

We retain account and payment records for the period needed to administer the account, address disputes, meet applicable Legal duties and respond to valid requests. The exact period can depend on the record type.

POLICY CHANGES

When Legal wording changes, we place the current version on the relevant account page. Check that page before opening an account or continuing after a material change affecting access, records or payment handling.

REQUEST OWNER

Our support team handles Legal questions and routes data requests to the appropriate account process. Include your registered phone number, request type and supporting receipt when the matter concerns DANA or QRIS.

Legal answers before opening your account

These Legal answers address the points Indonesian customers most often need before account access: eligibility, identity checks, records, cookies, payment evidence and policy changes. If your situation is specific, use the support route shown in your account and refer to the current wording on the relevant page.

It covers account access, phone verification, data handling, cookies, payment records, support requests and policy changes. It does not replace the current terms shown inside your account or any rule required where local law permits.

Yes. Account eligibility and access depend on local law. Availability can differ by region, so check the current account wording before opening an account or submitting payment details through DANA, OVO, GoPay or QRIS.

Phone verification helps connect the account to the person requesting access or a record change. We may request it before discussing private details, correcting account data or checking a payment status.

Use the account support route and state whether you want access, correction or deletion of a record. Include your registered phone number and enough context for us to identify the account without sharing private credentials.

We use transaction references, receipts and account details to match DANA or QRIS activity with the correct status. Keep your receipt until settled, and send it only through the account support route when needed.

Yes. The Legal wording explains that cookies or browser storage may support session continuity between account pages. You can adjust browser settings, but doing so may affect login continuity or notice display.

Send the matter through the support route available inside your account. Describe the issue, include the relevant page or payment reference, and avoid sharing wallet passwords or private authentication codes.