Reference

api288 Legal Access for Indonesia

api288 Legal explains how account access, wallet records and policy requests work before you open an account.

Account conditionsData handlingPolicy contact
api288 api288 Legal Access for Indonesia
POLICY HELP ROUTES

Get Help With Legal Questions

A clear contact path matters when a policy message interrupts account access or a wallet record needs checking.

Account access Use the support link beside the account sign-in area when phone verification or an eligibility message blocks access. We can direct your request to the correct policy path without asking you to repeat the full account history.
Wallet records For a DANA, OVO, GoPay or QRIS status question, send the payment reference shown in your account area. We use that detail to separate a policy restriction from a wallet-status issue.
Policy changes If you want a clause clarified or your stored account details corrected, use the support contact attached to your account. Tell us which wording needs attention and we will identify the next request step.
DATA CARE DETAILS

How We Handle Legal Records

Our policy work covers the account data needed for access, payment checks and requests sent to support.

Account data

We use the details submitted during account opening and phone verification to match access requests with the correct account. If a detail is wrong, ask support to identify the correction route for that record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may appear as payment references. We use them to trace status and policy checks, not as a substitute for your account identity.

Cookies

Cookies can help retain sign-in state and remember choices made during an account visit. Our policy wording explains their role, and you can ask support which cookie setting applies to your session.

Account security

Phone verification is part of the access path, while sign-in details should remain private to you. If access looks unfamiliar, contact support from the account area and describe the activity shown.

Record retention

We retain account, payment and policy-request records only for the operational or legal purpose that requires them. A request about a retained record should include your account phone number.

Correction requests

You can ask for a correction, clarification or account-data change through the support route linked to your account. We may need to verify ownership before changing a stored detail.

api288 Legal Questions Answered

These Legal answers cover the questions we expect you to ask before opening an account or sending a policy request. We keep the wording practical, with direct references to phone verification, local access conditions, cookies, payment records and account corrections.

It covers account access, phone verification, local eligibility, data handling, cookies, payment references and policy contact routes. Read it before opening an account so you know where to send a clarification.

Yes. Access depends on local law and the conditions applicable to your location. Where local law permits, the available account and lobby areas are shown after the required access steps.

Phone verification helps connect the access request with the correct account record. If the number or verification message does not match, use the account support route before trying another account.

DANA and QRIS may appear as payment references linked to an account activity or status check. We use the reference to trace the request, while account ownership remains tied to your verified details.

Yes. Send a correction request through the support contact attached to your account and identify the stored detail. We may verify account ownership before applying any change to the record.

The policy explains how cookies support sign-in state and session choices. If you need help with a cookie setting or want its role clarified, contact support from your account area.

Use the support link near your account area and quote the clause or access message. Include your account phone number where requested so we can route the policy question correctly.