Reference

ovo88 Privacy Policy for Your Account

Your ovo88 Privacy Policy explains what we collect when you open an account, verify your phone, browse on mobile and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record clarityAccount access stepsCookie choices
ovo88 ovo88 Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Account

A direct account route keeps a Privacy Policy question separate from general lobby browsing. Start from the support link shown after login, include the email or phone detail attached to your account, and tell us whether your request concerns access, correction, deletion or a payment record. For a DANA, OVO, GoPay or QRIS question, include the visible status and date so we can locate the relevant record.

Team online

Account access

Use the support route attached to your logged-in account when you need a copy of personal data or want us to confirm which account detail is stored.

Wallet record

For DANA, OVO, GoPay or QRIS records, send the payment reference and status shown in your account; we use those details to narrow the privacy request.

Correction request

If your phone, email or identity detail is incorrect, identify the field and the requested change through account support so we can check ownership first.

DATA PRACTICE

How ovo88 Handles Personal Data

We keep this Privacy Policy practical: each data category has a reason, an access path and a request method.

Account details

We hold the contact details you submit for account access and phone verification. Before changing a core detail, we may ask you to confirm account ownership through the existing login path.

Cookies

Cookies can remember your selected session settings and help us see whether a privacy page link works. You can manage browser cookie controls, though some account steps may then need repeating.

Mobile signals

When you move from login to the lobby on a mobile browser, we may record device and session signals for access protection. These signals help us identify unusual sign-in patterns.

Payment tracing

A DANA, OVO, GoPay or QRIS reference can remain linked to its account status so we can answer a receipt question. We do not need your wallet password for that check.

Retention

We retain records only for the account, security, payment tracing or legal purpose that requires them. When a record no longer has that purpose, our retention process marks it for removal.

Your request

Use the account support route to ask what we hold, request a correction or ask about deletion. Include your account contact detail, and we will check ownership before responding.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account records, wallet references, browser cookies, access requests and the local-law condition that applies to eligibility. If your case involves a specific transaction, use the payment status shown in your account when contacting us.

We may collect account contact details, phone verification status, device and browser signals, cookie settings, and payment references from DANA, OVO, GoPay or QRIS when those records support your requested account action.

Phone verification connects the person opening an account with the submitted account detail and helps protect later access. We use its status for account security and policy administration, where local law permits.

Yes. The policy covers sessions on a mobile browser as well as desktop access. We may use device and session signals to identify unusual login activity without reading unrelated content on your device.

We use the DANA or QRIS reference, amount status shown to us and relevant account link to trace a receipt or cashier question. We do not request your wallet password through support.

Yes. Send a correction request through the account support route, name the field that needs changing and provide the attached email or phone detail. We check ownership before updating the record.

We keep each record while it serves an account, security, payment tracing or legal purpose. Once that purpose ends, the retention process removes or separates the record where local law permits.

Yes. Account access and eligibility depend on local law. Our Privacy Policy explains the data handling connected with an eligible account, and you can contact support if your access status needs clarification.