Reference

olb88login Privacy Policy For Your Account

olb88login Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account dataCookie choicesWallet recordsLogin security
olb88login olb88login Privacy Policy For Your Account
POLICY SUPPORT

Where To Ask About Policy Access

A clear support path helps when you want to ask about the Privacy Policy, a wallet reference or an account record.

Account contact Use the support contact displayed after login for Privacy Policy questions.
Wallet query For DANA, OVO, GoPay or QRIS records, describe the date and reference shown in…
Access request Ask us through the same account support route when you need a copy, correction…
DATA PRACTICE

How We Protect Login And Wallet Data

We apply the Privacy Policy to the practical moments that matter: opening an account, checking a login, matching a payment reference and responding to a data request.

Collected details

We may handle contact details, account credentials, verification results, device signals and activity needed to maintain a signed-in session.

Cookie choices

Cookies can support login continuity and saved page settings on your mobile browser or desktop device.

Account protection

We use sign-in events, verification steps and device checks to help identify unusual account access.

Payment matching

A wallet or bank reference lets us connect a deposit or account action with the correct profile.

Retention period

We retain personal records for the period needed for account operation, security checks or applicable legal duties.

Changes and requests

You can ask for access, correction or clarification through the support contact shown after login.

Privacy Policy Questions For Indonesia

These answers address the Privacy Policy questions we expect when you are deciding whether to open an account. They cover account records, cookies, local wallets, device access and requests made through the signed-in support path. Where access or eligibility is discussed, it depends on local law.

It covers account details, verification, login events, device signals, cookies, payment references and requests about stored data. It also explains how we use records connected with your account activity.

We need contact and verification details to create your account, protect sign-in access and respond to account requests. The Privacy Policy describes the purpose attached to each data category.

Yes. It covers the reference and status information needed to match DANA or QRIS actions with your account. We do not ask you to provide a wallet PIN through support.

Cookies can keep a signed-in session and remember selected settings when you use a mobile browser. You can change browser controls, but some account functions may then require another login.

You can request access through the support contact shown after login. Include your account identifier and request subject; we may verify ownership before providing personal records.

Send a correction request through the signed-in account support route. Tell us which detail is inaccurate and provide the replacement; we may confirm the account before applying a change.

Yes. Access and eligibility depend on local law, and certain retention or account-handling duties may vary by jurisdiction. Contact support if you need the policy position for your account.