Reference

ultra88 Privacy Policy: What We Collect

Our Privacy Policy explains how we use the account details, phone verification, wallet records and device signals connected with your ultra88 access.

Account clarityWallet recordsDevice choicesContact steps
ultra88 ultra88 Privacy Policy: What We Collect
HELP CHANNELS

Contact Routes for Privacy Questions

You can raise a Privacy Policy question without guessing which team to reach. Start with the account help panel, then include the account phone number, relevant date and the payment or device record you want us to check. Our displayed support hours and available channel appear beside that route, while the cashier path helps you locate DANA, OVO, GoPay or QRIS references before sending a request.

Team online

Account help panel

Use the account help panel to ask what data is linked to your profile. Include your verified phone number so we can locate the correct record without asking you to send a password.

Cashier privacy route

When your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, begin from the cashier path and attach the receipt reference shown there.

Device access route

For a phone, browser or login-record request, tell us which device path you used and when. We use those details to separate a genuine access issue from another account event.

DATA PRACTICE

Phone, Cookies and Account Records

Our handling process is built around records we can identify and explain: account creation, phone verification, cashier activity, login events and support requests.

Account details

We use the details supplied during account creation to connect your profile, phone verification result and account requests. If a record is wrong, contact us through the account help panel with the requested correction.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries can create transaction references. We use those references to reconcile your account request, receipt and payment status.

Cookies and devices

Cookies and device signals help maintain your login path and identify unusual sign-in behaviour. Your browser settings can control cookies, although changing them may affect access to account pages.

Account security

Phone verification is checked before account access, and security events may be retained to investigate an unfamiliar sign-in. Never send us your password when asking about a Privacy Policy matter.

Retention period

We retain records only for the period needed for the stated account, payment, security or support purpose, subject to legal requirements. Ask us for the applicable retention detail tied to your record.

Change requests

To request access, correction or another permitted change, contact the route shown in the policy area and identify the account phone number. We may ask for verification before discussing private records.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is checked. They cover the data tied to your account, the device path used for access and the contact steps available when you need a correction. Where a request depends on local law, we will assess it against the applicable rule.

It covers account details, phone verification, login and device signals, payment references, cookies, security events and support messages connected with your access. It also explains retention, permitted requests and contact steps.

We use your phone number to create and identify the account, complete phone verification before access and connect a privacy request to the right record. Do not send your password with a request.

Yes. The policy includes transaction references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us match receipts, account requests and payment status questions.

Use the account help panel and provide your verified phone number, the record concerned and the requested action. We may confirm your identity before sharing private account data or applying a correction.

Retention depends on the purpose of the record, such as account access, payment reconciliation, security or support, plus applicable legal requirements. Contact us with the record type for a more specific response.

Yes. Tell us whether you used a mobile browser or another device path and include the approximate access time. Browser cookie settings can also be adjusted, although some account pages may then behave differently.

The policy explains our data handling, but account access depends on local law. If you are unsure about eligibility from your location, contact support through the displayed account route before opening an account.