Reference

alilabola Legal access, privacy and account terms

Our Legal page brings account rules, privacy handling and access conditions into one clear place, so you can check the position before opening an account.

Account rulesPrivacy controlsLocal access
alilabola alilabola Legal access, privacy and account terms
POLICY CONTACT ROUTES

Get Legal help beside your account

A clear contact path matters when a Legal question affects account access or a payment record.

Account access Use the account help route when phone verification, login details or eligibility wording prevents…
Wallet records For DANA, OVO, GoPay or QRIS status questions, choose the payment path and include…
Policy changes Use the policy contact route to request a correction, ask how a clause applies…
DATA HANDLING DETAIL

Six Legal safeguards inside alilabola

Legal protection is practical: we separate account details from payment references, limit access to records by operational need and keep policy requests tied to the account concerned.

Account data

We use the details attached to your account to manage access, phone verification and policy requests. Check your account information before a payment so a DANA or QRIS record can be matched correctly.

Payment references

A bank transfer, virtual account or wallet reference is handled as a transaction record. We use it to investigate status and account matching, not as a substitute for your private wallet credentials.

Cookies

Cookies may support sign-in continuity, security checks and policy preferences on your device. You can manage browser cookie settings, although changing them may affect account access or saved policy choices.

Account security

Keep your password and phone access private, and complete verification only through the account path. If a sign-in detail looks wrong, stop the account step and contact us through the policy route.

Record retention

We retain account and transaction records for the period needed to operate the account, resolve disputes and meet applicable Legal duties. Ask through the policy route if you need the retention basis for a record.

Change requests

To correct or question personal data, send the account identifier, affected field and requested change through support. We may ask for a verification step before changing information tied to your account.

Answers about Legal and account access

These Legal answers cover the questions we expect before account creation: which rules apply, how data is handled, what happens to payment references and where to request a change. If your situation is different, use the account policy route and include the specific clause or record you want us to check.

Legal covers our account terms, privacy handling, cookies, payment records, access conditions and contact process. It explains what you agree to when opening an account and how to request a correction.

Access depends on local law and is provided only where local law permits. Your location and account eligibility may affect access, so check the policy wording before completing phone verification.

Phone verification helps connect you with the correct account before access is granted. It also reduces account mix-ups when we investigate a DANA, OVO, GoPay or QRIS transaction reference.

We use payment references to match and investigate account transactions. Wallet credentials are not requested through the policy route, and you should share only the transaction details specifically requested.

Yes. Send the account identifier, the field that needs correction and your requested change through the policy contact route. We may complete a verification step before updating account-linked information.

Cookies can keep security checks, sign-in continuity and policy preferences working on your device. Browser controls can remove them, but account access or saved policy choices may then need to be repeated.

Use the policy contact route and identify the account record or transaction reference. We can explain the retention basis connected with that record after confirming the request belongs to the account holder.