Reference

afabola Privacy Policy, Clearly Explained

afabola Privacy Policy explains what we collect when you open an account, sign in, browse Slots or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
afabola afabola Privacy Policy, Clearly Explained
CONTACT YOUR WAY

Privacy Policy Help Near Account Support

A clear contact path matters when you want to ask about Privacy Policy data or correct an account record. Start through our account help path and include the phone number linked to your afabola account, the subject of your request and any relevant payment reference. We use those details to locate the right record without asking you to send a password or wallet PIN. Where local law permits, we can explain the next step for access, correction or deletion requests.

Team online

Account help

Use the account help path for Privacy Policy questions about your phone verification, sign-in records or stored profile details. Include your account phone number so we can separate your request from another account without asking for your password.

Wallet status

If your question concerns DANA, OVO, GoPay or QRIS, share the payment reference and approximate time rather than a wallet PIN. We can check the linked status and explain which account record the Privacy Policy request concerns.

Receipt checks

For bank transfer or virtual account questions, attach only the receipt details needed to identify the transaction. Our support path can help match the reference, clarify retention and route a request to the person handling data access.

DATA HANDLING

Privacy Controls From Login To Lobby

We handle Privacy Policy requests around the real account journey: phone verification before access, wallet checks at the cashier path and device sessions used to open the lobby.

Account records

We collect account details you submit, including your phone number and verification state. These records let us connect a sign-in request with the correct account and explain what we hold when you ask about Privacy Policy access.

Device sessions

When you move from a mobile browser login to the lobby, we may record technical session details such as browser or device signals. These help protect account access and diagnose a failed session without reading unrelated device content.

Cookies

Necessary cookies support sign-in and page continuity, including the path from account access to Slots or a wallet status screen. You can manage browser cookie settings, although disabling required cookies may interrupt the Privacy Policy access path.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to match a receipt with your account. We use the reference for status checks and do not need your wallet PIN for that process.

Retention choices

We keep account, support and payment records only for the period needed for the stated purpose, account security or legal duties. A deletion request does not remove records that we must retain where local law permits or requires continued storage.

Request changes

You can ask us to access, correct or delete eligible personal data through account help. State the Privacy Policy request clearly, provide the phone number linked to your account and answer reasonable identity checks before we make a change.

Privacy Policy Answers For afabola Accounts

These Privacy Policy answers address the searches we hear most often from people checking afabola before opening an account. They cover account data, cookies, Indonesian wallet references, device access and requests to see or change stored details. If your situation is not listed, use the account help path with the phone number connected to your account.

The afabola Privacy Policy covers information you submit for an account, phone verification records, device session details, cookies, support messages and payment references. It explains how we use those records for access, account security, payment matching and requests to see or correct eligible data.

We use your phone number to create and identify the correct account, complete phone verification before account access and route support requests. It also helps us distinguish your DANA, OVO, GoPay or QRIS status from another account when you ask about stored data.

Yes. Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account references. We use them to match receipts and explain a cashier status; you should never send a wallet PIN.

Cookies help maintain necessary account sessions and keep the path from mobile browser login to the lobby working. Your browser controls can manage cookies, but blocking required cookies may stop sign-in or remove the continuity needed to reach a Privacy Policy page.

Use the account help path and ask for Privacy Policy data access. Include the phone number linked to your account, describe the records you want and provide any relevant payment reference. We may ask reasonable identity questions before sending data connected with you.

You can request correction or deletion of eligible data through account help. Explain the error or the records you want removed and identify your account by its linked phone number. We may retain payment, security or legal records where local law permits or requires it.

The Privacy Policy applies to account and device data collected when you use afabola in supported Indonesia regions. Access or eligibility depends on local law. If you contact us from Jakarta or elsewhere, include your account phone number so we can handle the request accurately.