Reference

Legal clarity for your alohatoto account

alohatoto Legal sets out how account access, identity checks, wallet records and policy requests work before you enter the lobby.

Account accessData requestsPolicy contactsLocal-law wording
alohatoto Legal clarity for your alohatoto account
POLICY HELP

Where to ask about Legal matters

Questions about Legal are easiest to resolve when you use the account support route and include the exact issue, account phone number and any relevant reference shown in your wallet history. We separate access questions from payment-status questions so the right record can be checked. If you are in Surabaya or another Indonesian location, the same account path applies, while eligibility still depends on local law. Do not send passwords or one-time verification codes in a support request.

Team online

Account access

Use the support route attached to your account when phone verification, sign-in status or an access decision needs clarification. Include the message shown on screen, but keep your password and one-time code private.

Wallet records

For DANA, OVO, GoPay or QRIS questions, send the payment reference and date shown in your account history. We can then match the record without asking you to repeat sensitive wallet credentials.

Policy requests

If you want a Legal clause explained or need to request a correction, contact us through the account help path. State the section and requested change so our team can respond to the right policy point.

DATA PRACTICES

What we do with policy-related records

Legal is also about the records created when you open an account, verify a phone number or ask us to check a wallet status.

Account data

We use registration details and phone verification status to connect a request to the correct account. This helps us avoid changing access details for the wrong person when several accounts use similar contact information.

Cookie choices

Cookies can support the account path and remember necessary session activity on your device. Our Legal wording explains their purpose, so you can understand what is used when moving from sign-in to policy pages.

Access security

Phone verification is part of the account access check. Never share a one-time code with support or another person; if a code arrives unexpectedly, use the account help path before attempting a security change.

Record retention

Policy-related records may be retained for account operation, dispute handling and legal obligations. The applicable Legal text describes why records are kept and when a request may need additional account verification.

Correction requests

If a registration detail or payment reference appears wrong, identify the field or transaction in your request. We may ask for account confirmation before correcting information connected with DANA, QRIS or bank transfer.

Contact route

Use the support path inside your account for questions about data, cookies, retention or access. Keep your message focused on one policy issue, and remove passwords, wallet PINs and verification codes.

Answers about alohatoto Legal

These Legal answers cover the questions we expect before an Indonesian customer opens an account or asks for a policy change. They explain the practical route for access, data and payment records without replacing the current terms. When a question concerns eligibility, the deciding condition is always where local law permits, together with the account status shown to you.

It covers account access, phone verification, data handling, cookies, retention, payment records and requests to correct or explain policy details. The current Legal text is the reference to read before opening an account or asking support to change account information.

Access depends on local law and the eligibility status shown through your account path. If you are asked to complete phone verification or provide an account confirmation, follow that step instead of creating another account or sending security codes.

DANA and QRIS references are treated as account-related payment records. We use the reference, date and status available in your account to investigate a question. Do not send a wallet PIN or one-time verification code with your request.

Yes. Use the account support route, identify the specific detail that appears wrong and explain the correction requested. We may ask you to confirm phone verification or another account detail before changing information linked to your account.

Send a focused request through the account help path and name either cookies or record retention. We will direct the question to the relevant Legal wording. Please include only necessary account details and never include passwords or wallet credentials.

An account check helps us protect access and make sure a data, wallet or policy request belongs to the correct account. This can apply before discussing OVO, GoPay, bank transfer or virtual account records.

Start with the support route inside your account and quote the policy section or status message involved. We can explain the applicable process, while any access or eligibility outcome remains subject to local law and the account conditions shown.