Reference

uni88 slot Privacy Policy And Account Privacy

uni88 slot gives you a clear Privacy Policy for account details, wallet records and device access, so you can understand what we collect before opening an account.

Account data explainedWallet records clarifiedCookie choices includedIndonesia access wording
uni88 slot uni88 slot Privacy Policy And Account Privacy
PRIVACY CONTACT

Privacy Help Beside Your Account Path

A privacy request should be easy to connect with the right account, especially when it concerns a wallet record or a login device.

Account data request Ask us which account details we hold and why they are used. Include your registered phone number or account identifier through the account help path so we can confirm the correct record before responding.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, tell us the date and status shown in your account. We use those details to locate the relevant transaction without requesting your wallet password.
Access and correction If your name, phone number or verification detail is inaccurate, contact us from the account path and describe the change. We may request account checks before editing information connected with login or payment records.
DATA PRACTICES

What Our Privacy Policy Covers

We treat privacy as an account process rather than a vague promise: collect only details needed for access, transaction matching, security and support, then retain them according to the purpose and applicable…

Account details

We may hold your name, phone number, login identifier and verification responses because those details connect you to the correct account. We use them to provide access, respond to account requests and identify changes that need confirmation.

Payment references

A DANA, OVO, GoPay or QRIS record can include a reference, amount status, date and account link. Bank transfer and virtual account entries serve the same matching purpose; we do not need your wallet password to check a status.

Device security

When you move between a mobile browser and desktop, we may capture device type, browser version, IP address and session time. These signals help us identify unusual login behaviour and may prompt an account check before access continues.

Cookies and storage

Cookies or similar browser storage can remember session settings and help us understand whether a login request belongs to the same browser. You can manage browser storage through device settings, although removing it may require you to sign in again.

Retention choices

We keep account and transaction records for as long as needed for the stated service purpose, security checks, dispute handling or applicable legal duties. When a record is no longer needed, our processes call for deletion or removal of direct account links where feasible.

Your privacy request

You can ask what we hold, request a correction or ask about deletion by contacting us through the account help path. We may verify ownership first, then explain any limit that applies to payment, security or legal records.

Privacy Policy Questions For Indonesia

These Privacy Policy answers focus on the questions we expect you to ask before opening or using an account from Indonesia. They explain the data connected with wallets, devices and account access in plain language. If your situation is different, use the account help path and provide only the details needed to locate your record.

It covers account details, verification records, device and session signals, cookies, payment references and support requests. The Privacy Policy also explains why we use each category, how retention works and how you can ask for access or correction through the account help path.

Yes. We may retain a DANA or QRIS transaction reference, date, status and account connection so we can match a payment and investigate a missing update. We do not need your wallet password for that check, and the same approach applies to OVO and GoPay.

Device type, browser version, IP address and session timing help us recognise unusual login activity and protect your account. For example, a move from a mobile browser to desktop may create a security signal. We use these details for access protection, not to request your wallet credentials.

Use the account help path and identify the account with your registered phone number or account identifier. Ask for the categories of data held and the reason for use. We may verify ownership before sharing records, which helps prevent another person from receiving your details.

Yes. Send the correction through the account help path and describe whether it concerns your name, phone number or verification detail. We may compare the request with account records before making a change, particularly when the detail is linked to login or payment matching.

We retain information for the service purpose that created it, account security, payment dispute handling or applicable legal duties. After that need ends, our processes call for deletion or removal of direct account links where feasible. We can explain the reason for a particular retention period.

Cookies and browser storage can keep a session connected and remember selected settings. You can remove or limit them through your phone or desktop browser controls, but doing so may sign you out or require another account check when you return. The Privacy Policy explains their limited purpose.