Reference

Open omu99 Privacy Policy Before Account Access

Our omu99 Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact rights
omu99 Open omu99 Privacy Policy Before Account Access
CONTACT ROUTES

Check Your Privacy Contact Path

A clear contact route helps you act on this Privacy Policy without searching through the lobby.

Account request Use the support route beside the cashier path when you want to ask what…
Wallet query For a DANA, OVO, GoPay or QRIS privacy query, include the relevant receipt or…
Device access If a mobile browser shows an unexpected sign-in prompt or cookie choice, tell us…
DATA PRACTICES

Explore Data Controls Across Your Account

We keep this policy practical by connecting each privacy point to an account action you can recognise.

Account security

Phone verification can be recorded as part of the account access process.

Cookie choices

Cookies can remember browser preferences and help pages connect your current session with the correct account path.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a payment event with the account that submitted it.

Retention periods

We keep account, security and payment records only for the operational or legal period that applies to the record.

Correction requests

If your phone detail, contact detail or account record needs correction, send the request through the account-linked support path.

Policy questions

Questions about this Privacy Policy can be sent through the same support route, including requests about cookies, device records, wallet…

Ask About omu99 Privacy Policy

These Privacy Policy answers address the account situations you are most likely to meet before or after opening access. We cover wallet references, cookies, phone verification, mobile browsing and requests to see or change records. If your question is not listed, use the account-linked support route and describe the specific data issue rather than sending unnecessary credentials.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, correction requests and how to contact us about your data.

We may retain the payment reference, status and account connection needed to check a DANA or QRIS event. We do not need your wallet password for that process. For a privacy question, send the receipt or status reference through the account-linked support path.

Phone verification helps connect account access with the correct account and supports checks when a sign-in comes from a new device. The verification record may be retained with security logs. We will not ask you to share a one-time code in a support message.

Where local law permits, you can ask what account data we hold or request a correction. Use the support route beside the cashier path, identify the account-linked phone detail, and state whether you seek access, correction or a retention explanation.

Cookies can support session continuity and saved browser choices on a mobile or desktop device. Restricting them may change sign-in prompts or page behaviour. Your browser settings control many cookie choices, while our Privacy Policy explains why the session record may still be needed.

Retention depends on the type of record and the operational or legal period that applies. Account security logs, payment references and support requests may follow different periods. Ask us through the account-linked route for the category and retention explanation relevant to your request.

Yes, the policy explains data handling for Indonesian account access, including mobile browsing and local wallet references. Eligibility and access depends on local law. If you access from Yogyakarta, Jakarta or elsewhere, use the same policy contact route for a data request.