Reference

alexabet Legal For Your Account

alexabet Legal sets out how we handle account access, wallet records, cookies, security checks and requests from you.

Account rulesData requestsLocal-law accessPayment records

What Legal Covers Before Access

alexabet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Legal terms explain the conditions attached to your account, the checks used before access, and the records created when you use a wallet route. DANA, OVO, GoPay and QRIS may appear in your payment history with the relevant status, while bank transfer and virtual account

1
entries can require matching account details. Access depends on local law, and availability can differ by location or account review. We may ask you to confirm phone details before account access, especially when login or payment information does not match. Read the policy before opening an
2
account so you know which requests we can process and which restrictions may apply.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

POLICY HELP

Get Clear Answers On Legal Questions

A clear contact path matters when a Legal question blocks your account or leaves a wallet status unclear. Start from the account support route beside the cashier area and describe the issue in plain English, including the affected payment rail or account step. We can use that context to direct your question about access, data handling, cookies or a policy change. If you are in Yogyakarta, the same online support path applies; access still depends on local law.

Team online

Account access

Tell us if phone verification, login details or an eligibility message prevents account access. Include the account identifier shown on your screen, but do not send a password. We use the account support route to connect your question with the relevant Legal wording.

Wallet status

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the payment status and reference shown in your cashier record. We can explain which policy step applies without asking you to repeat private wallet credentials.

Policy request

Ask us to clarify a Legal clause, request a data change, or raise a concern about cookies and retention through the same support path. State the exact request and the account email or phone detail connected to your profile.

DATA HANDLING

How We Apply Legal To Your Details

Legal is practical when you can see how a request moves through the account.

Account data

We connect account details to the profile you open, including the contact detail used for phone verification.

Payment records

A DANA, OVO, GoPay or QRIS action can create a status and reference in your account history.

Cookies

Cookies help keep an authenticated session available as you move from login to the lobby on mobile or desktop.

Account security

Phone verification can appear before account access when our checks require it.

Retention requests

If you want to ask how long a particular account or payment record is kept, name the record and its…

Policy changes

When Legal wording changes, we place the current terms on this page and may require you to acknowledge an updated…

Your alexabet Legal Questions Answered

These Legal answers focus on the questions you may have before opening an account or sending a policy request. We cover local access, account checks, payment records, cookies, corrections and contact steps so you can decide what to do next with the current wording in view.

alexabet Legal covers account conditions, access checks, payment records, cookies, account security, data requests and policy changes. It applies to the account journey and related cashier records, including DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries.

Yes. Account eligibility and service access depends on local law, and some functions may only be available where local law permits. If a location or account check affects you, read the current Legal wording and contact support for clarification before proceeding.

Phone verification helps connect the account to the contact detail supplied during the account step and can be required before access. If the code does not arrive or the detail is wrong, use the account support route rather than sharing your password.

DANA and QRIS actions can produce a payment status and reference in your account history. We use those details to trace a cashier question and explain the relevant policy step. Do not send wallet passwords or private authentication codes in a support request.

You can request a correction by contacting support through the policy contact path. State which account detail is wrong, what it should say and the profile identifier we can use. We may need to confirm ownership before applying a change.

Cookies can keep your session active while you move between login, the lobby and the Legal page on a phone or desktop. Browser controls let you manage them, but blocking certain cookies may affect sign-in, saved settings or page functions.

Use the account support route beside the cashier area and describe the exact clause, data field or payment reference. Include your connected account email or phone detail, but never send a password. We will direct the request to the relevant policy path.

alexabet Legal For Your Account

Get Clear Answers On Legal Questions

Account access

Wallet status

Policy request

How We Apply Legal To Your Details

Account data

Payment records

Cookies

Account security

Retention requests

Policy changes

Your alexabet Legal Questions Answered

01 What does alexabet Legal cover?

02 Does Legal access depend on local law in Indonesia?

03 Why does Legal require phone verification?

04 How are DANA and QRIS records handled under Legal?

05 Can I request a change to my alexabet account data?

06 How do cookies affect Legal and account access?

07 Where can I ask about a Legal clause or retained record?

Related Pages