Reference

Privacy Policy for slotmax88 Accounts

slotmax88 keeps this Privacy Policy focused on the data you provide when opening an account, confirming your phone, entering the lobby or using DANA, OVO, GoPay and QRIS.

Account dataCookie choicesWallet recordsContact requests
slotmax88 Privacy Policy for slotmax88 Accounts
CONTACT THE TEAM

Privacy Questions Near Your Account Path

A clear contact route matters when a Privacy Policy question concerns your phone verification, wallet record or device session.

Account data request Ask us to identify the personal data connected with your account. Include your account contact detail and the specific category you want checked, such as phone verification, login history or wallet status.
Correction request If your account contact detail is inaccurate, send the corrected value through the account help path. We may ask for an account step that confirms you control the profile before changing the record.
Wallet record query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, share the reference and date rather than your password. We can then compare the payment status with the account event.
DATA HANDLING DETAILS

Inside slotmax88 Privacy Controls

We separate the data needed to operate your account from optional cookie signals used to remember settings or understand a session.

Account creation

When you open an account, we use the details you submit to create the profile and deliver account access. Phone verification confirms the contact step before you enter the lobby, and the verification result becomes part of the account record.

Session security

Login time, device type and browser signals can be used to detect an unusual session. If the pattern needs checking, we may ask you to repeat an account confirmation step rather than request your password or wallet code.

Cookie settings

Cookies can remember a language choice, sign-in state or page preference. You can manage cookies through your browser controls; removing them may require you to repeat login or phone verification on the next visit.

Payment references

We keep the reference needed to match a DANA, OVO, GoPay or QRIS event to your account. Bank transfer and virtual account records help us distinguish a pending status from a completed account update.

Retention approach

We retain data only for the period needed for the stated account, security, support or legal purpose. A request to remove data may be limited when a transaction reference or security event must remain available.

Your requests

You can ask what personal data we hold, request a correction or question a processing purpose. Send the request through account help with enough detail to locate your profile, and we will explain any identity check needed.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions we hear most often from people in Indonesia. They explain the practical route for checking data, cookies, wallet references and account access. If your situation is specific, use the account help path and mention the relevant account step so we can respond to the right record.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains how we use those records for access, security, support and legal purposes, including DANA, OVO, GoPay, QRIS, bank transfer and virtual account events.

Phone verification confirms the contact step attached to your account before access is completed. We use its status to protect the profile and investigate login questions. We do not need your one-time code in a support message, so keep that code private.

Yes. Use the account help path and ask for a data access request. Include the email or phone detail connected to your profile. We may need an identity check before responding, because sending account data to the wrong person would create a security risk.

We store the transaction reference and status needed to match a DANA or QRIS event with your account. We do not ask you to send a wallet password or one-time code. For a status question, provide the reference and date through account help.

You can request a correction through account help and describe the field that is wrong. We may ask you to complete an account confirmation step before changing contact details. The Privacy Policy explains when a record cannot be changed because retention or security duties apply.

Browser controls can block or remove cookies used for language, sign-in state or page preferences. Some account steps may then appear again, including login or phone verification. The Privacy Policy explains the purpose of these cookies without making cookie acceptance a substitute for account security.

Yes. Access and eligibility depends on local law, and our Privacy Policy does not change that position. Where local law permits, we process account and security data for the purposes described here. If you need a location-specific answer, contact us through account help.