Reference

Legal access for your akar388 account

akar388 sets out the Legal terms behind account access, local wallet records and support requests in one place.

Account termsData choicesContact routeLocal access
akar388 Legal access for your akar388 account
CONTACT PATHS

Get a clear route for legal questions

Legal questions are easier to resolve when your account details and payment reference are together.

Account access If phone verification or a sign-in check stops your account path, contact us through the account help route. Tell us the step you reached and the device you used, so we can address access under the Legal terms without asking for your password.
Payment record For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the payment reference and approximate time. We use those details to locate the record, explain its status and keep the conversation focused on the relevant Legal policy.
Policy request You can ask us to explain a clause, correct an account detail or review a data request through the same contact path. We will identify the request, check the account securely and explain any step that depends on local law.
RECORD HANDLING

How we handle your account records

We keep our Legal approach practical: collect the details needed for account access, protect the account path and explain why a record is used.

Data purpose

We use account details to provide access, check a phone verification step, answer support requests and connect payment references with the correct account. We do not need your password in a support message, and we ask you to remove sensitive credentials before sending a request.

Cookie use

Cookies can remember sign-in context, language settings and parts of your account path. They help the page return you to the correct step, but they do not replace phone verification. Ask us which cookie category relates to your Legal question.

Account security

A clear phone verification step helps protect account access when details are checked. Keep your password private, sign out on shared devices and contact us if a sign-in event does not match your activity. We will use the account record to verify the request.

Payment retention

Payment references may remain available after a transaction so we can reconcile wallet status, bank transfer details or a virtual account record. The retained entry is used for account and transaction handling, not as a reason to request your password or wallet PIN.

Change request

You may ask us to correct inaccurate account details, explain a stored record or clarify how a request is handled. Include the account identifier and the specific field in question. We may need to verify ownership before making any change.

Who to contact

Our account support contact is the route for Legal, privacy, cookie and access questions. You can ask about a clause before opening an account or after sign-in. We will explain the applicable process and flag any outcome that depends on local law.

Legal questions before you open an account

These Legal answers cover the questions we expect you to ask before using akar388 from Indonesia. They explain account access, payment records, cookies, corrections and contact steps in plain language. If your situation is not covered, send the account help request with only the details needed to identify your question. We will tell you when an answer depends on local law.

The Legal page covers account access, phone verification, data use, cookies, payment records, security requests and contact routes. It also explains that access depends on local law. Read it before opening an account so you understand which conditions apply to your location and account activity.

Yes. Access depends on local law, and we only describe the service as available where local law permits. If you are in Indonesia, check the conditions for your location before creating an account. Contact us if you need a clause explained.

Phone verification helps connect an access request with the correct account and reduces confusion when sign-in details are checked. It can also be needed before support changes account data. We will not ask you to send a password or wallet PIN in a support message.

We may retain transaction references for reconciliation, account support and payment status checks. A record can show the rail used, such as DANA, OVO, GoPay or QRIS, without requiring your wallet PIN. Ask us to explain a specific entry through the account contact route.

Yes. Send a correction request through the account support contact and name the account field that appears inaccurate. We may verify ownership before changing it. If the request affects access or payment records, we will explain the applicable Legal step first.

Cookies can keep sign-in context, language settings and parts of your account path available between page visits. They support the access process but do not replace phone verification. You can contact us to ask which cookie use relates to your Legal question.

Our account support contact handles Legal, privacy, cookie, access and payment-record questions. Include your account identifier and a short description, but never include your password or wallet PIN. We will confirm the request path and explain any location-based condition.