Reference

udin88 Privacy Policy for Your Account Data

DANA, QRIS, OVO and GoPay details stay connected to a clear Privacy Policy, so you can see why we collect account, device and payment records before opening an…

Account dataWallet recordsDevice choicesPolicy access
udin88 udin88 Privacy Policy for Your Account Data
HELP WITH YOUR RECORDS

Get Privacy Help Beside Account Support

A direct support route helps when a Privacy Policy question meets a login or wallet-status issue. Keep your account phone number and payment receipt ready, then contact us through the support path shown beside the account and cashier areas. We can use those references to locate the right record without asking you to send a full wallet password.

Team online

Account access

If phone verification blocks access, tell us which account step stopped and the device you used. We can explain the related data record and the Privacy Policy section that applies.

Wallet status

For DANA, OVO, GoPay or QRIS questions, include the payment reference and status shown at the cashier. We use that detail to trace the request without requesting your wallet PIN.

Policy requests

Ask us to correct an account detail, explain a cookie record or clarify retention through the available support contact. We will confirm the account step needed before discussing personal data.

HOW WE HANDLE DATA

Keep Wallet And Device Data Clear

We keep the Privacy Policy practical by connecting each data point to an account action you recognise.

Collection at account steps

We collect details when you create an account, complete phone verification or sign in. Login events help us identify unusual access, while contact details let us respond to a request about your policy records.

Wallet and payment records

A DANA, OVO, GoPay or QRIS reference can show payment status without exposing your wallet PIN. Bank transfer and virtual account records are used to match the account action you ask us to check.

Cookies and device signals

Cookies can remember a session choice, while device signals help keep login activity consistent between mobile and desktop. You can ask support how a specific cookie or device record relates to your account.

Account security checks

We may compare your phone verification, login event and payment reference before discussing personal data. This account step reduces the chance that another person receives details about your wallet or profile.

Retention and deletion

We keep records only for the period described in the current Privacy Policy and any period required for account, payment or legal handling. Ask us which retention rule applies to a named record.

Changes and contact

You can request correction, clarification or an eligible change through our support path. Include the account phone number and the exact record, such as a QRIS receipt or device entry, so we can verify it.

Privacy Policy Answers For udin88 Accounts

These answers address the Privacy Policy searches we hear most often before account access. If your question concerns a particular phone check, device entry, DANA receipt or QRIS status, use the support path with that reference so we can respond to the record you mean.

It covers account details, phone verification, login events, device signals, cookies, wallet status, payment references, retention and requests to correct eligible records. Access depends on local law.

Yes. It explains how we use DANA and QRIS references to check payment status and connect a cashier action with your account, without asking for your wallet PIN or private wallet password.

Phone verification helps connect you to the correct account before we discuss personal data. It also supports account-security checks when a login, wallet status or payment receipt needs investigation.

We use OVO and GoPay status details and transaction references for the account action you ask us to check. The Privacy Policy explains the purpose, access controls and retention period for those records.

You can request a correction through our support path. State the account phone number and the record needing change, such as a device entry or payment reference, so we can verify your request.

Cookies may retain a session choice, while device signals help identify a consistent login from mobile or desktop. The Privacy Policy explains these uses and how to ask about a specific record.

Contact us through the account support route and name the record, such as a bank transfer receipt, virtual account event or login entry. We will explain the applicable retention rule where local law permits.