Reference

amanbola Privacy Policy For Clear Account Control

Your account data, wallet references and device choices stay explained in the amanbola Privacy Policy, so you can decide what to share before opening the lobby.

Account dataWallet referencesCookie choicesPhone checks
amanbola amanbola Privacy Policy For Clear Account Control
CONTACT PATHS

Privacy Policy Help Beside Cashier

A clear contact route matters when a Privacy Policy question concerns your account rather than a general query.

Account requests Ask about a copy, correction or removal of your account data through the support path beside the cashier. Include your registered phone number so we can match the request before discussing account records.
Wallet references If a Privacy Policy question involves DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, add the receipt reference only. We use it to trace a status without requesting your wallet PIN.
Access concerns For a phone verification or login concern, tell us the device type and the step where access stopped. This gives our support route enough context to check security records without exposing unrelated account data.
DATA PRACTICE

How amanbola Protects Account Records

We keep the Privacy Policy practical by connecting each data use to an account step: phone verification, login, wallet status, support or security review.

Account collection

We collect the details needed to open and maintain your account, including your contact route and phone verification result. We do not ask for unrelated personal details simply because you browse Blackjack or Fortune Dragon.

Cookie choices

Cookies can remember a selected language, session state or security setting on your browser. You can adjust cookie controls in your device or browser path, though disabling required cookies may interrupt login or account requests.

Device signals

Login time, browser type and device signals help us identify unusual account access. These records support a security check when your phone verification step does not match the device already associated with your account.

Wallet protection

For DANA, OVO, GoPay and QRIS, we handle payment references and status details rather than wallet passwords or PINs. Bank transfer and virtual account receipts are used to match a request with the correct account.

Retention requests

We keep account, support and security records only as long as an operational or legal reason requires. Ask us through the support route what remains connected to your account and whether a removal request can proceed.

Policy changes

When this Privacy Policy changes, we place the updated wording on this page and identify the relevant account or cookie practice. Check the page before opening an account or changing your phone verification details.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to search for before opening an amanbola account. We cover data collected during phone verification, cookie controls, wallet references, device checks, retention and requests for access or correction. If your situation is not covered, use the support route beside the cashier and include only the account details needed to identify your request.

It covers account details, phone verification, login activity, device signals, cookies, support messages and payment references. It also explains retention, security checks and how to ask about your records. Access depends on local law, and the policy applies where local law permits.

Phone verification helps connect the correct person to an account request and helps us detect unusual login activity. We use the result for account access and security checks, not to request your DANA, OVO, GoPay or QRIS wallet PIN.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use those references to match a receipt or cashier request, while wallet passwords remain outside our request.

You can contact us through the support path beside the cashier and ask what account, device, cookie or support records are linked to your registered phone number. We may need an account check before sharing records, and the response depends on local law.

Send a correction request through the account support route, identify the field that is wrong and provide the current detail. We check the request against your account before changing it, especially when it affects phone verification or a payment reference.

We keep records for the period needed for account operation, security checks, support handling or legal requirements. Retention can differ by record type and region. Ask through support for the status of a specific record; removal remains subject to local law.

Yes. Use the cookie controls in your mobile browser or device settings to adjust optional storage. Required session or security cookies may still be needed for login and phone verification, so disabling them can affect account access.