Reference

Privacy Policy for Your Account

Your Privacy Policy starts with the places where data appears first: account setup, DANA, OVO, GoPay, QRIS wallet records, and lobby sessions for Dragon Tiger, Dream Catcher, Aviator…

Account data useDANA OVO GoPay QRISCookie choicesSupport privacy requests

Explore Lobby Read FAQ

What We Collect and Why

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

We collect only the details needed to run your account, protect your login, process wallet activity, and answer privacy questions with enough context to act correctly. That may include your name or account handle, phone or email, device type, IP logs, cookie choices, payment reference codes

1
from DANA, OVO, GoPay, QRIS, and support chat history. We use those records to confirm account ownership, match deposits to your wallet, flag unusual access from a new device, and keep a clear audit trail when you ask us to change or delete data. If a
2
privacy request touches access or eligibility, we handle it according to local law and only where local law permits. We do not sell your account data, and we limit internal access to staff who need it for account, wallet, or support work.

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

CONTACT ROUTES

3 Ways to Reach Privacy Support

Privacy help should be easy to find before you open an account and after you join.

DATA HANDLING

6 Privacy Controls Inside aceslot88

Good privacy practice is visible in small account steps, not only in long policy text. We keep payment references separate from gameplay history where practical, use session checks when your device changes…

Account setup

When you open an account, we ask for the details needed to create and protect your profile. We avoid collecting extra personal fields at entry, then add verification only when wallet activity or support handling requires it.

Payment records

DANA, OVO, GoPay, and QRIS records are used to match your wallet activity with the correct account. We store reference codes, timestamps, and status changes so your privacy request can be checked against a clear payment trail.

Device checks

If your login shifts from mobile Chrome to desktop, we may keep device, browser, and IP signals for account safety. You can ask us what device records we hold and request correction if something looks wrong.

Cookie choices

Cookies help remember your session, language preference, and basic lobby behavior. You can clear cookies in your browser settings, and we explain what may change, such as needing to log in again on that device.

Retention period

We keep account and wallet records only as long as needed for operations, dispute handling, security checks, and local legal duties. When records no longer serve those purposes, we remove or separate them from your active profile.

Change requests

You can ask us to correct profile details, check stored records, or close data that no longer needs to stay active. We confirm ownership first, then tell you what can change and what must remain for legal reasons.

Privacy Questions Before You Join

Your privacy questions usually come before the first deposit, especially when local payment rails and mobile access are involved. These answers explain how we handle account data, wallet references, cookies, device signals, and correction requests in plain terms. If your case needs a decision rather than a general answer, contact support and we will check your account record directly.

We collect the details needed to create and protect your account, such as your contact method, account ID, login signals, and wallet references. Extra verification may be requested only when payment, security, or support handling needs it.

We use local payment records to match a deposit or withdrawal request to your wallet. The record usually includes a timestamp, payment rail, reference code, status, and account link so support can trace the transaction safely.

Yes. Contact support through live chat or the privacy email path and tell us what you want to check. We confirm account ownership first, then share the relevant account, device, cookie, or payment record summary.

Open Account, then Security, then Privacy Request, or contact support if you cannot log in. We verify ownership, update the profile field when allowed, and keep a change record for account safety.

Device and IP data help us spot unusual access, protect your wallet, and answer login disputes. For example, a switch from mobile Safari to desktop Chrome may be logged so we can verify whether the activity was yours.

We keep records while they are needed for account operations, wallet matching, security checks, support history, and local legal duties. When that need ends, we delete, anonymize, or separate the record from your active profile.

Use the privacy email path or the Account menu request form and state which data you want deleted. We confirm identity, check whether local law requires retention, then explain what we removed or why it must remain.

Privacy Policy for Your Account

3 Ways to Reach Privacy Support

6 Privacy Controls Inside aceslot88

Account setup

Payment records

Device checks

Cookie choices

Retention period

Change requests

Privacy Questions Before You Join

01 What personal data does aceslot88 collect when I open an account?

02 How are DANA, OVO, GoPay, and QRIS records used in the Privacy Policy?

03 Can I ask to see the data linked to my account?

04 How do I correct my phone number or email in the privacy record?

05 Why does aceslot88 keep device and IP data?

06 How long do you keep account and payment data?

07 Who do I contact if I want data deleted?

Related Pages