Reference

omoda88 Privacy Policy for Indonesia

omoda88 Privacy Policy explains how we handle your account details, phone verification, device signals and payment references when you use our Indonesia service.

Account clarityWallet referencesCookie choicesContact route
omoda88 omoda88 Privacy Policy for Indonesia
CONTACT OPTIONS

Where Privacy Questions Go

A clear contact path helps you act on this Privacy Policy instead of searching through unrelated account pages.

Account contact route Use the support contact shown after account access and mark your message as a Privacy Policy request. Include your account identifier and the specific record you want explained, such as a phone verification event or a DANA payment reference. We use those details to locate the correct account without asking for your password.
Payment data query For OVO, GoPay, QRIS, bank transfer or virtual account questions, send the receipt reference and approximate transaction time through the account support route. We use payment references to investigate status, but we do not need your wallet PIN or one-time code. Redacted evidence is enough for an initial check.
Access correction request If your phone number, account detail or contact preference is inaccurate, tell us which field needs attention and why. We may request a phone verification step before making a change. Where local law permits, you can also ask whether a stored record can be removed or restricted.
DATA PRACTICES

What We Do With Account Data

Privacy decisions are easier when the operational reason is visible. We use account and device records to keep sign-in working, connect a payment reference to the correct account and investigate an unusual…

Account records

When you open an account, we process details such as your chosen account identifier, phone verification result and support messages. These records let us identify your account when you move from login to the lobby or ask why an access attempt was blocked. We use only the details needed for that purpose.

Payment references

A DANA, OVO, GoPay or QRIS transaction may create a reference, amount, time and status record so we can match the payment to your account. Bank transfer and virtual account checks follow the same principle. We do not ask support messages to include wallet passwords, PINs or one-time codes.

Device signals

Our pages may receive browser, device, language, approximate network and session signals. On a phone, these help us distinguish a normal return to the account from an unusual sign-in and keep the mobile path functional. They are not a request for access to your private files or contacts.

Cookies

Cookies and similar storage can remember a session, preserve a selected setting or help us understand which policy page was opened. Your browser controls many cookie choices, and available site controls may offer additional options. Turning some cookies off can affect sign-in continuity or saved preferences.

Retention timing

We keep information only for the account, security, support or payment purpose that requires it, subject to applicable legal duties. A closed account does not always mean every record disappears immediately because a payment query or security matter may still need evidence. Ask support which category applies to your request.

Your requests

You can ask for a copy of eligible account data, correction of an inaccurate field, details about processing or deletion where local law permits. Send one request at a time with enough context to locate your account. We may verify ownership first and explain any record we must retain.

Privacy Policy Answers for omoda88

These Privacy Policy answers address the account and payment questions we hear most often from Indonesian customers. They explain what to include in a request, why verification may be needed and how device or wallet references fit into account support. If your situation is unusual, contact us through the route shown in your account and describe the specific record involved. Access and any related request remain subject to where local law permits.

The omoda88 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use those records for sign-in, payment matching, security and support, plus how to request access, correction or deletion where local law permits.

Phone verification helps us connect you with the correct account and reduce confusion when access is requested from a new device. We record the verification result rather than asking you to send a one-time code to support. We may repeat the check before changing sensitive account details.

Yes. The Privacy Policy covers references linked to DANA, OVO, GoPay and QRIS, including a status, time and account match needed for support. Bank transfer and virtual account references can be handled similarly. Never include a wallet PIN, password or one-time code in your message.

Yes. Send the account identifier, identify the field that is wrong and explain the correction you are requesting. We may verify ownership through the phone linked to the account before changing it. This process applies to contact details, verification records and other eligible account information.

Use the support contact available after account access and label the message as a Privacy Policy data request. State whether you want a copy, processing details or a correction, and include the relevant account identifier. We will verify the request and explain the available scope and format.

Retention varies by record type and purpose. Account, device, support and payment references may remain while they are needed for access, security, dispute handling or applicable legal duties. A request to delete eligible data can be made where local law permits, and support can explain remaining records.

Your browser provides controls for many cookies, while the site may provide additional settings when available. Essential session storage can remain necessary for account access, but optional choices may be changed through those controls. If a setting does not behave as expected, contact support without sending private credentials.