Reference

alexavegas Privacy Policy for Your Account

Our Privacy Policy explains how we use the account, wallet and device details needed to provide access to alexavegas.

Account clarityWallet statusMobile access
alexavegas alexavegas Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Account Path

A clear contact route matters when you want to ask about personal data rather than a wallet result.

Account data request Ask us to confirm which account details we hold by using the support route linked from your signed-in account area. We may ask for a phone verification step before discussing private records.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, share the transaction date and visible reference only. We can check the linked status while keeping your wallet PIN and full login secret private.
Access concern If a mobile browser shows an unexpected sign-in or privacy message, contact us through the account help path before opening another session. We can use device and session details to investigate.
HANDLING DETAILS

How We Handle Wallet And Device Data

We keep this policy practical: you should know what is collected, why it is needed and how to ask for a correction.

Account records

We handle details such as your account identifier, phone verification result, sign-in events and support messages to provide account access and respond to requests about your personal data.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be retained with a transaction status. We do not need your wallet PIN to match that record.

Cookies and sessions

Cookies or similar browser storage can remember a session choice and help detect unusual access. You can manage browser storage through your device settings, though some account steps may then require another login.

Account security

We use sign-in events, device signals and phone verification to help protect your account. Never send a password, wallet PIN or one-time security code through a support message.

Retention timing

We keep account, payment and support records only for as long as needed for service operation, security checks, dispute handling or legal duties, then remove or separate them where appropriate.

Changes and requests

To request access, correction or removal of eligible details, contact us through the account support route. Tell us what to change, and we may verify ownership before responding.

Privacy Policy Questions For alexavegas

These Privacy Policy answers cover the questions we expect you to ask before opening an account, linking a wallet or returning from a mobile browser. If your case involves a specific record, include only the minimum details needed for us to locate it.

The alexavegas Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

We use phone verification to help confirm account ownership before discussing private records or completing certain access steps. It also helps distinguish your account when several people share one device.

Yes. The Privacy Policy covers QRIS, DANA, OVO and GoPay references linked to your account, including status and transaction time. We do not ask for your wallet PIN or full security code.

We may handle browser, device, connection and session signals to keep account access secure, remember a session choice and investigate an unexpected sign-in. These signals can be generated on a mobile browser or desktop.

Use the support route in your signed-in account area and state whether you want access or correction. Include your account identifier, not your password, and we may verify ownership before releasing details.

You can request removal of eligible account details through the account support route. Some payment, security or dispute records may need to remain for a defined operational or legal purpose.

This Privacy Policy applies to records handled through our service where local law permits. Access and eligibility depends on local law, so you should check the rules that apply in your location.