Reference

ulti88 Privacy Policy For Your Indonesia Account

Our Privacy Policy explains what we collect when you open an ulti88 account, use DANA or QRIS, and move from a phone login into the lobby.

Account dataWallet referencesDevice signalsCookie choices
Explore Our Lobby Read FAQ
ulti88 ulti88 Privacy Policy For Your Indonesia Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact route helps you act on the Privacy Policy instead of searching through unrelated account screens. When you ask about personal data, include the phone number or account identifier used during registration, the subject of your request and any relevant wallet reference. We use those details to locate the correct record, protect the account from an unauthorised request and tell you what can be changed. Access remains where local law permits.

Team online

Account privacy request

Use the support contact attached to your ulti88 account when you want a copy of stored account data, a correction or clarification about the Privacy Policy. Include your registered phone number so we can match the request without asking you to send a wallet password.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the payment date, amount shown in your account and the relevant reference through support. We can check the account trail while keeping your wallet PIN and external login credentials outside our request.

Login data concern

Tell us if a new device, browser session or phone verification event does not match your activity. We use the account step and device signal together to investigate access concerns, then explain which data was checked and what action is available under this policy.

HANDLING YOUR RECORDS

What Our Privacy Controls Cover

Our handling process follows the account journey rather than treating every visitor the same. Registration, phone verification, wallet status and device access create different records, so a Privacy Policy request can be…

Account collection

At the account step, we may collect your phone number, verification result and details needed to maintain your account record. We use these fields to identify your request and connect support replies to the right account, rather than asking you to repeat private details in an open message.

Wallet references

DANA, OVO, GoPay and QRIS can return a status or reference for reconciliation. We use that limited payment context to check whether an account action was recorded. Your wallet PIN, wallet password and separate banking credentials are not required for this matching process.

Cookie controls

Cookies and similar browser storage may remember a session setting or help us understand whether a page request belongs to the same visit. You can clear browser storage through your device settings, although doing so may require another login or phone verification step.

Account security

Phone verification and device signals help us spot an access pattern that differs from your usual account path. If you move from mobile login to a desktop browser, a security check may be requested. Never send us a one-time code or account password in support messages.

Retention period

We keep account, payment-reference and support records only for the period needed for security checks, dispute handling and applicable legal duties. When a retention need ends, records are deleted, anonymised or separated from direct account identifiers where that process is available.

Changes and contact

You can ask for access, correction or a Privacy Policy explanation through the account support path. Include the registered phone number and a precise request. We may verify ownership before responding, and we will explain if a legal, security or dispute requirement limits a change.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the account actions you are most likely to ask about before opening an account or contacting support. We explain the practical path for wallet references, cookies, phone verification, device changes and data requests. For any access or eligibility question, the applicable position depends on local law.

It covers account registration, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how you can request access or correction.

No. We use the payment reference or status needed to match an account action, but your DANA, OVO or GoPay password and wallet PIN stay outside that process. Do not send those credentials when asking about a Privacy Policy matter.

Contact support through the account path and provide the phone number used during registration plus a clear request for access. We may ask for an ownership check before replying, then describe which records can be supplied and whether any security or legal limit applies.

You can request a correction through support by identifying the account field that appears wrong and explaining the change. We verify ownership before editing records. A correction may be limited where the original entry is needed for payment reconciliation, security or a legal duty.

Cookies or browser storage may keep a session setting and help connect related page requests. You can clear them in your phone browser settings. After clearing storage, you may need to log in again and complete phone verification before account access resumes.

A new phone, browser or desktop path can produce a device signal that differs from your earlier login. We may request phone verification to protect the account. This check does not require your wallet password, and access remains where local law permits.

We retain account, support and payment-reference records for as long as needed for security, dispute handling and applicable legal duties. When that purpose ends, we delete, anonymise or separate the records from direct identifiers where available, subject to any continuing requirement.

Related Pages

ulti88 Indonesia Account information ulti88 Casino Access guide FAQ