Reference

apibet Privacy Policy for Indonesian Accounts

The apibet Privacy Policy shows how we handle account data when you use DANA, OVO, GoPay or QRIS, including phone verification before account access.

Account dataWallet recordsCookie choicesRequest access
apibet apibet Privacy Policy for Indonesian Accounts
CLEAR CONTACT ROUTES

Get Privacy Policy Help Near Your Account

A clear support route matters when you want to ask about a record, cookie choice or account detail.

Account data request Use the account support path to ask what data is linked to your login. Include your verified phone number and we can direct the request to the appropriate privacy contact.
Wallet record question For DANA, OVO, GoPay or QRIS queries, add the receipt or transaction reference. We use that detail to distinguish a payment record from another account activity.
Access problem If phone verification blocks a policy request, tell us the device path you used, such as mobile browser or desktop browser. Do not send your wallet PIN.
DATA HANDLING DETAILS

How apibet Keeps Privacy Workable

We keep this policy practical by connecting each data use to an account action you can recognise.

Data we collect

We may handle your account name, verified phone number, sign-in events, device details, wallet references and support messages. The purpose is to operate account access, check requests and resolve activity tied to you.

Cookies on your device

Cookies can retain a sign-in preference and record movement between the policy page and account area. You can manage browser cookie settings, though disabling them may require another login.

Account security

Phone verification comes before account access, while unusual sign-ins or wallet changes may trigger another check. We will not ask for your DANA PIN, OVO PIN, GoPay PIN or QRIS secret.

Retention periods

We keep records only for the period needed for the stated account, payment, security or support purpose and for applicable requirements. When a record is no longer needed, our handling process addresses it.

Change requests

You can ask us to correct account data or clarify its use through the support path. Provide the verified phone number and a precise change request so we can check ownership.

Policy contact

Questions about this Privacy Policy should stay in the account support route rather than a wallet chat. We can then connect your question with the relevant login, cookie or payment record.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the checks you are most likely to meet before opening or using an Indonesian account. We cover wallet records, phone verification, cookies, correction requests and contact steps, so you can decide what to provide before entering the account area.

It covers account data, phone verification, sign-in events, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for account verification and ownership checks before access. It also helps us match a privacy request with the correct account without requesting your wallet PIN.

Yes. A QRIS receipt reference may be handled to match an account activity or answer a payment query. We do not need your QRIS secret or wallet login details.

You can send a correction request through the account support path. Include your verified phone number, the field that needs attention and the reason, so ownership and accuracy can be checked.

Cookies may remember sign-in choices and connect your mobile browser session with policy pages. Browser settings can remove or block them, but you may need to complete phone verification again.

Retention depends on the reason for collection, such as account access, payment matching, security or support, together with applicable requirements. We address records when they are no longer needed.

Use the support path attached to your account and describe the data or cookie question clearly. For DANA, OVO, GoPay or QRIS matters, add the relevant reference without sharing a PIN.