Reference

Privacy Policy for Your Account

Your account data, wallet records, and device signals are handled through this Privacy Policy before you enter Live Roulette, Slots, Rocket Crash, or any other room we carry.

Account data useDANA record handlingOVO and GoPay contextQRIS transaction checksCookie choices
alexsistoto88 Privacy Policy for Your Account
HELP CHANNELS

Privacy Contact Paths

Fast privacy contact matters when your account, phone number, or wallet history needs attention.

Live chat privacy desk Use live chat from the account area between 09:00 and 23:00 WIB for privacy…
WhatsApp account check For changes to your phone number or contact data, message our WhatsApp channel from…
Email data request Send access, correction, or deletion requests by email with your username, registered phone number…
DATA CONTROLS

How We Handle Privacy Requests

Privacy work is part of the account flow, not a separate promise. When you create an account, return on mobile, scan QRIS, or ask support about a transaction, we keep enough data…

Account registration data

We collect the details you enter during registration, including username, contact channel, password status, and account preferences. These records let us identify you when you request changes or report an unfamiliar login.

Payment privacy context

DANA, OVO, GoPay, and QRIS details are used to match transactions with your wallet page. We do not ask you to send unnecessary screenshots when a reference code already verifies the payment route.

Cookies and device signals

Cookies help keep your session active when you move between Slots, Mobile Legends, and the wallet page. You can clear cookies through your browser, but you may need to log in again afterward.

Security checks

We watch for unusual login patterns, repeated password attempts, and device changes that may affect your account. If a check is triggered, support may ask you to confirm recent activity before access continues.

Retention periods

We keep account and transaction records only as long as needed for service, dispute handling, security checks, and legal record duties. When data is no longer needed, we remove or separate it from active account use.

Correction requests

If your phone number, email, or wallet label is wrong, contact us before making another payment. We verify ownership first, then update the record so future privacy and transaction checks match your account.

Privacy Policy Questions

These answers focus on how we use data tied to your account, device, wallet activity, and support requests. If your question involves a specific transaction, include the payment rail name and account username when you contact us.

We collect the account details you provide, such as username, contact channel, password status, and wallet context. We also record login data, device signals, and session activity needed to protect access and answer privacy requests.

We keep payment context so wallet activity can be matched to your account, checked during disputes, and traced by support. The record normally includes the payment rail, reference details, time, status, and related username.

Yes. Contact us through live chat, WhatsApp, or email with your username and registered phone number. We verify account ownership first, then explain what account data we hold and how it is used.

Send a request before your next payment so we can compare the change with your existing account records. We may ask for your username, current contact channel, and a recent DANA, OVO, GoPay, or QRIS reference.

Cookies help keep your login session active and remember basic device choices while you move between game rooms and wallet pages. You can clear them in your browser, but account sign-in may be required again.

Privacy requests are handled by service staff who need access for account support, security checks, or transaction tracing. We keep requests tied to your account record so follow-up messages are consistent and easier to verify.

You can ask us to delete data linked to your account. We review the request, verify ownership, and remove data where possible, while keeping records that must remain for security, dispute, or legal record reasons.