Reference

alexabet Privacy Policy In Plain English

Our Privacy Policy explains how alexabet collects, uses, protects and removes information connected with your account, wallet activity and support requests.

Clear data purposesWallet record contextAccount access choicesPolicy contact route
Explore Our Lobby Read FAQ
alexabet alexabet Privacy Policy In Plain English
CONTACT THE TEAM

Get Privacy Help Beside Your Account

A clear contact path matters when a data request concerns your account or wallet record. We ask you to use the support route linked from your account area and include the email or phone detail connected with your alexabet access. That lets us locate the correct record without asking you to send payment credentials. Requests can cover access, correction, deletion, cookie choices or an explanation of how a DANA, OVO, GoPay or QRIS reference is used.

Team online

Account contact

Use the support route beside your account settings for a Privacy Policy request. Include your registered contact detail and the subject of the request, while keeping passwords, wallet PINs and one-time codes out of the message.

Wallet record check

If your request concerns DANA, OVO, GoPay or QRIS activity, share the transaction date and reference shown in your account history. We use those details to find the relevant record without requesting your full wallet credentials.

Access assistance

When phone verification or a sign-in check blocks a privacy request, tell us which step stopped you and which device you used. We can route the matter to account support while keeping the request focused on your personal data.

DATA HANDLING

How We Apply Privacy Controls

We handle privacy as part of the account flow rather than as a separate promise.

Account details

We may hold your name, contact detail, verification result and account activity so we can provide access and answer account…

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can contain a reference, amount, time and status.

Cookies and sessions

Cookies and similar session details help keep your account path working, remember security state and identify unusual sign-in behaviour.

Security checks

Phone verification, session controls and device signals help protect your account from access that does not match your normal sign-in…

Record retention

We retain account, support and transaction records only while they serve an operational, dispute, security or legal purpose.

Change requests

You can ask us to access, correct, restrict or remove eligible personal details through the account support route.

Answers About Your Privacy Policy

These Privacy Policy answers address the searches we hear most often from people checking alexabet before opening an account. Each answer stays focused on personal data, account records, device access and the contact steps available to you. Where a right or access condition varies by location, it depends on local law.

The alexabet Privacy Policy explains what we collect during account opening, phone verification, sign-in, wallet status checks and support contact. It also describes cookies, security records, retention, permitted uses and the way you can request access or correction where local law permits.

We use phone verification to connect account access with the correct contact detail and to reduce unauthorised sign-ins. The verification result can also help us confirm ownership before changing account information or responding to a request about DANA, OVO, GoPay or QRIS records.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use that context to match a record to your account, investigate a status question and meet applicable service or legal duties.

Open the support route from your account area and ask for an access request under the Privacy Policy. Add your registered email or phone detail and the records you want reviewed. We may complete an ownership check before sending information where local law permits.

You can request a correction through the account support route. State which detail is wrong and provide the accurate replacement without sending a password, wallet PIN or one-time code. We may verify your identity before changing contact, verification or account profile records.

Retention depends on the record and its purpose. We may keep account, support, security and transaction material while needed for service delivery, dispute handling, fraud checks or legal duties. When the applicable purpose ends, we remove, restrict or anonymise the record where required.

You can manage optional cookies through your browser settings and contact us through the account support route with a cookie question. Required session cookies may still be needed for login, phone verification and secure movement between the policy page and account settings.

Related Pages

alexabet Indonesia Liga 2 Match Bet Coin Flip Arcade About Us FAQ