Reference

Privacy Policy for DANA and QRIS Accounts

Our Privacy Policy explains how alexabet88 handles the details you provide when opening an account, signing in from a phone, or using DANA and QRIS.

Clear data purposesWallet activity contextPhone access choicesContact request path
Explore Our Lobby Read FAQ
alexabet88 Privacy Policy for DANA and QRIS Accounts
CONTACT ROUTES

Get Privacy Help Through Your Account

A clear contact path helps you act on this Privacy Policy without sending sensitive details into a public channel. Start from your signed-in account and include the phone number on your profile, the relevant request, and any payment reference you want us to check. We may ask for an account step or identity detail before discussing private records. For a stalled login or wallet status, use the account help route beside the cashier path and describe whether you used DANA, OVO, GoPay, QRIS, or a bank rail.

Team online

Account request

Send a data access, correction, or deletion request through the signed-in account route. Include your registered phone number and the specific record you want us to locate, so we can reduce back-and-forth before handling private account details.

Wallet record

For a payment-related privacy question, add the rail name and reference shown in your cashier history. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records can require different matching details before we discuss them.

Login assistance

If phone verification or a device session blocks your request, explain the device path you used and the message shown on screen. We use that context to separate an access issue from a request about stored personal data.

DATA PRACTICES

How We Protect Wallet And Device Data

Privacy work continues after your account is opened. We limit internal access to data needed for account care, payment matching, security checks, or legal duties, and we use account steps rather than…

Account security

Phone verification connects access to the number on your profile. We may review sign-in, session, and device signals when a login looks unusual, while keeping the request inside the account path instead of exposing details in open chat.

Cookie choices

Cookies can remember session settings, support sign-in continuity, and help us understand whether a page request came from the same device. You can manage browser cookie controls, though changing them may affect account access or saved preferences.

Payment matching

A DANA, QRIS, OVO, or GoPay transaction can carry a reference, status, and timestamp used to match your account request. Bank transfer and virtual account records follow the same purpose: confirming the correct account activity.

Device handling

When you use a mobile browser, we may receive device type, browser version, IP address, and session events connected with your visit. These details help us investigate access problems without requiring your wallet password or unrelated phone content.

Retention choices

We keep personal records only as long as they serve account operation, payment reconciliation, security checks, dispute handling, or legal duties. A deletion request may be limited where a record must remain for one of those purposes.

Change requests

You can ask us to correct inaccurate profile details or explain the data connected with your account. Use the signed-in contact route, identify the requested change, and complete any account check needed to protect your records.

Privacy Policy Questions For Indonesian Accounts

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia: phone verification, mobile access, wallet records, cookies, and requests for your personal data. We keep the answers tied to our actual contact and payment paths. If your question concerns eligibility or access, remember that access depends on local law and the details shown in your account.

The alexabet88 Privacy Policy covers account details, phone verification, payment references, device and browser signals, cookies, support requests, retention, and permitted data changes. It explains why we use each type of record when you sign in, use a wallet rail, or ask for account help.

Yes. The Privacy Policy covers records created when you select DANA, OVO, GoPay, or QRIS, including a reference, status, amount, and time where available. We use these details to match account activity and resolve a payment question, not to collect your wallet password.

We use the phone number attached to your account for phone verification, account access, and requests involving private records. If you contact us about a correction or deletion, we may ask you to confirm account details before discussing information linked to that number.

You can request access to eligible account data or ask us to correct an inaccurate detail through the signed-in contact route. State the record you mean, such as a profile field or payment reference. We may verify your account before responding.

We keep records for the period needed to operate your account, match DANA or bank activity, investigate security events, handle disputes, or meet legal duties. When those purposes end, our retention process can remove or restrict the record as permitted.

Cookies can store session settings and support continuity between phone login and the lobby. Browser and device details may also be received during that visit. You can adjust cookie controls in your browser, but some account functions may not work as expected afterward.

Where local law permits, you can ask us to delete eligible personal data through the account contact route. We may retain records required for payment reconciliation, security, disputes, or legal duties, and we may first verify that the request comes from you.

Related Pages

alexabet88 Indonesia Account information FAQ alexabet88 Casino bolaonline