Terms of Service
The terms page describes the contract; this page describes the data. Where they overlap — account closure, for instance — both documents use the same retention window.
This is our privacy policy — the page that explains what ovo88 collects when you open an account, why we hold it, and how long it stays with...
We collect what we need to run your account and nothing we can't justify: the name and contact details you give us at signup, the device signals your browser sends, and the transaction references tied to your wallet top-ups. Where local law permits, we keep this on servers aligned with Indonesia data-handling expectations, and we only share with processors who help us
deliver the lobby — payment partners, fraud screening, and customer contact. You can ask us what we hold on you, ask us to correct it, or close the account and have the record retired after the retention window required for financial reconciliation. Our policy is jurisdiction-aware and applies across supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach our privacy desk through any of the channels below. We log every request and respond inside the window our policy commits to, so you always know where your query sits.
We treat the policy as a living document. Below is how we keep it accurate, reviewed and aligned with how the lobby actually behaves.
Every change to this page carries a date stamp at the top. You can see when wording shifted and decide whether the new version affects how your account data is held.
Our policy text is checked by counsel familiar with Indonesia consumer data norms before it goes live, so the language matches what we actually do behind the scenes.
A named team inside ovo88 owns this document. They sign off changes, approve processor additions, and answer escalations that come through the privacy inbox.
Any third party that touches your account data is contracted under data-handling clauses. We don't onboard a vendor without confirming they meet our retention and access standards.
Staff access to account records is logged. If you ask who has touched your file, we can describe the categories of access without exposing internal identifiers.
If a clause reads ambiguously, tell us. We've rewritten sections more than once because a reader flagged that the original phrasing didn't match how the lobby behaves.
This privacy policy sits alongside our terms, cookie notice and account rules. Here's how the wording lines up so you don't get conflicting answers depending on which page you land on.
The terms page describes the contract; this page describes the data. Where they overlap — account closure, for instance — both documents use the same retention window.
Cookies sit in their own document because they're browser-side. Anything stored server-side under your account ID is governed here in the privacy policy instead.
Account rules cover behaviour inside the lobby. Personal data captured to enforce those rules — verification photos, for example — is held under this privacy policy.
Transaction metadata from DANA, OVO, GoPay and QRIS top-ups is referenced here. The payment page itself covers fees and timing, not data handling.
Marketing opt-ins are described here and mirrored in your account preferences. Either source is authoritative; they cannot disagree because they read from the same flag.
Identity checks live in a separate notice but reference back to this document for storage duration and access. Both pages quote identical retention numbers.
How long we keep records after you close the account is stated here and repeated in the terms. The financial reconciliation window applies in both places.
Quick map of what you'll find on this page so you can jump to the part that matters to your question. Every block below is policy-side, not lobby marketing.