Reference

alexabet88 Privacy Policy for Your Account

The alexabet88 Privacy Policy explains how we collect, use and protect the details connected with your account, including contact data, device signals and wallet records for DANA, OVO…

Clear data purposesWallet records explainedPhone verification contextPolicy requests supported
alexabet88 alexabet88 Privacy Policy for Your Account
HELP WITH REQUESTS

Get Clear Answers About Your Privacy

A privacy question should not leave you guessing about the next step. We keep account help and policy requests near the same support route used when login or wallet status stalls, so you can describe the issue without posting personal details in a public channel. Include the phone number linked to your account, the request type and any relevant payment reference; never include a password, one-time code or full wallet credentials. We answer through the support channel available inside your account.

Team online

Account data request

Ask which personal details are linked to your account and why we use them. We may ask you to complete phone verification before discussing private records, so the request reaches the correct account holder.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount reference and wallet name through our account support path. We use those details to locate the status without requesting your wallet password.

Change or correction

You can ask us to correct contact details or explain a retention decision. Keep your request specific, and we will confirm the safe account step needed before changing information connected with access or payment records.

YOUR DATA CONTROLS

Privacy Choices That Stay Near Login

We handle privacy as part of the account flow rather than as a separate promise. Login protection, phone verification and wallet status checks each create records with a defined operational purpose.

Data collection

We collect details you provide during account creation and verification, along with device, session and transaction references generated when you sign in or use a wallet route. The Privacy Policy explains why each category is needed.

Cookie controls

Cookies can keep your login session connected and help us identify technical faults across a phone or computer. Browser settings can limit them, but switching them off may interrupt account access or require another sign-in.

Account security

Phone verification helps us distinguish an account holder from an unknown sign-in. Never share a one-time code or password with anyone; contact support through the account path if access looks unusual.

Retention timing

We retain account, payment and support records only as long as needed for the purpose described, security checks, dispute handling or legal duties. You may ask why a particular record still needs to remain.

Your requests

You can ask for access to personal data, correction of inaccurate details, an explanation of use, or deletion where applicable. We may verify your identity before releasing or changing account-linked information.

Policy contact

Use the support channel shown after account access and label the message as a Privacy Policy request. Add your account phone number and a short description, while leaving passwords and wallet secrets out.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers cover the questions we hear before account access: what we collect, how wallet references are used, how cookies affect a device and how you can contact us. Read them with the full policy and use the account support path when your situation needs a specific answer. Eligibility depends on local law.

It covers personal details, phone verification, device and session signals, cookies, payment references and support messages connected with your account. It also explains our purposes, security controls, retention approach and the steps for access, correction or other applicable requests.

DANA and QRIS references help us match a payment status with the correct account and investigate a missing receipt. We may also handle references for OVO, GoPay, bank transfer or a virtual account, but we do not need your wallet password.

We use your phone number for account identification, phone verification, login assistance and relevant support handling. If the number is inaccurate, request a correction through the account support channel; we may verify you before changing an access detail.

Yes. The Privacy Policy explains that cookies and device signals can keep a session active and help locate access faults. You can adjust browser controls, but limiting cookies may sign you out or affect parts of the account path.

You can request access to personal data linked with your account through the support route shown after login. State what you need, include your account phone number and complete any identity check required before we disclose private records.

Send a specific correction request through account support, such as an incorrect phone number or contact detail. We will explain the account step required and may verify the request before changing information used for login, security or payment matching.

Yes. Ask which record you want removed and why through the Privacy Policy contact path. Some account, payment or security records may need to remain for dispute handling or legal duties, and we will explain the applicable reason.