Reference

alila bola Privacy Policy for Indonesia

Our Privacy Policy explains how alila bola handles the account details, wallet records and device signals used when you open the lobby from Indonesia.

Account dataWallet recordsCookie choicesDevice access
alila bola alila bola Privacy Policy for Indonesia
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact path matters when you want to ask what data we hold or correct an account detail. Start from your signed-in account support route, or use the support link beside the cashier area when a wallet reference needs checking. Tell us the email or phone connected to your account and the request you want handled. We may ask for account confirmation before discussing private records.

Team online

Account support

Use the signed-in account support route for a copy request, correction request or question about how your phone number is used. Include your registered contact detail so we can locate the right record without asking you to send wallet passwords or payment credentials.

Cashier path

If your privacy question concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, open the support route beside the cashier area. Share the receipt reference and date, not your wallet PIN. We use those details to trace status while limiting exposure.

Device access

When a mobile browser keeps an old session or shows an unfamiliar sign-in, contact support from the account page and mention the device path. We can help check account access, sign-in records and cookie behaviour without requesting your full device contents.

HANDLING PRACTICES

What We Keep And Why

We separate account, payment and device records so each request can be handled for a clear reason.

Account details

When you open an account, we collect the contact and verification details needed to provide access. A clear phone verification step helps us distinguish an account change from an unknown sign-in. We do not need your wallet PIN to handle ordinary account support.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference, amount, time and status record. Bank transfer and virtual account activity may carry similar reconciliation details. These records help match receipts and account actions without giving us access to your private wallet credentials.

Cookies and sessions

Cookies can keep your login session, language choice and security checks working when you move between the mobile lobby and account page. You can clear browser cookies through your device settings, although doing so may sign you out and require phone verification again.

Device security

We may record browser type, device signals, sign-in time and approximate network details to protect account access. If a session looks unusual, we may ask you to confirm the account step before discussing wallet status or changing contact details.

Retention period

We keep account, support and payment records for as long as needed to operate the requested service, resolve a dispute or meet a legal requirement. When a retention reason ends, we aim to delete or anonymise the record where local law permits.

Your data request

You can ask us to access, correct or clarify personal data connected to your account. Send the request through account support and identify the relevant phone number, email or payment reference. We may verify ownership first so private data is not disclosed to another person.

Privacy Policy Questions Answered

These Privacy Policy answers address the practical questions you may have before opening an account from Indonesia. We explain the records connected to phone verification, mobile access, cookies and local wallet activity. If your question is not covered, use account support with the contact detail attached to your account so we can check the correct record.

The Privacy Policy covers account details, phone verification, sign-in records, cookies, device signals, support messages and payment references. It explains why we use each category, how we protect account access and how you can ask for access or correction through the account support route.

Yes. The Privacy Policy covers references linked to DANA, QRIS, OVO, GoPay, virtual account and bank transfer activity. We may keep the payment status, time and reconciliation reference needed to match your account action, but you should never send a wallet PIN or full login credential.

Mobile access may create a session record containing browser type, device signals, sign-in time and approximate network details. Cookies can remember your session and security choices. You can clear cookies in your mobile browser settings, though you may then need to sign in and verify again.

Use the signed-in account support route and ask for a data access request. Include the phone number or email connected to your account and describe the records you want, such as support messages or payment references. We may confirm ownership before sending private account data.

Yes. Send a correction request through account support and state which account detail is wrong, such as a phone number or email address. We may ask for a verification step before changing it, especially when the request could affect sign-in, wallet status or account recovery.

We retain records for the operational, legal or dispute reason that requires them. Account, support and payment records may therefore remain after a transaction or support contact ends. When that reason ends, we aim to remove or anonymise the data where local law permits.

Ask through account support and mention whether the issue concerns cookies, an unfamiliar sign-in or a session on your mobile browser. For wallet-related privacy questions, use the support route beside the cashier area. Access to our service depends on local law.