Reference

obc212 Privacy Policy for Indonesia Accounts

Our Privacy Policy explains how we handle the details connected with your obc212 account, including phone verification, wallet status, device access and support requests.

Account clarityWallet contextDevice controlsPolicy access
obc212 obc212 Privacy Policy for Indonesia Accounts
CONTACT OUR TEAM

Privacy Policy Help Along Your Account Path

A clear contact route matters when you want to ask what data we hold or why an account check is needed. Use the support path linked from your account area and describe the request in plain English, including the phone number or account reference connected with it. Do not send a wallet PIN or full payment password. Our team can direct a privacy request, login concern or wallet-status question to the right handling path, while access remains subject to local law.

Team online

Account privacy request

Ask us to locate the account details connected with your phone verification. Include your account reference and the email or phone route attached to it, so we can check identity before discussing personal data.

Wallet data question

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, tell us the date, amount and payment reference without sharing your wallet PIN. We can check the account-side record and explain the next privacy step.

Access correction

If your name, phone detail or account record needs correction, send the specific field and the reason for the change through our support path. We may request verification before updating information attached to your account.

DATA CONTROL DETAILS

What We Do With Account Data

We keep our Privacy Policy practical by connecting each data purpose to an account action you recognise.

Account records

We use the details you provide during account creation and phone verification to create, maintain and secure your profile.

Payment references

A DANA, OVO, GoPay or QRIS reference can be stored alongside an account-side transaction record.

Device signals

Browser type, device identifiers and sign-in timing may help us recognise an unusual access attempt.

Cookies

Cookies can keep a session active, remember a selected setting or help us understand which policy page was opened.

Retention timing

We keep personal data only for the period needed for account operation, security checks, payment reconciliation or legal duties.

Your requests

You can ask about access, correction or deletion through the support route connected with your account.

Privacy Policy Questions About obc212

These Privacy Policy answers cover the account and payment questions you are most likely to have before opening an obc212 account. We explain the practical route for checking data, changing details, managing cookies and asking about records linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Where a request concerns eligibility or access, it depends on local law.

The obc212 Privacy Policy covers account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each type of data, how long we may retain it and how you can request access, correction or deletion through the account support route.

We may collect the details needed for your account path, such as contact information, phone verification results, sign-in records, device signals and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account may also be connected with your account-side record.

Use the support path linked with your account and clearly ask for access to your personal data. Include your account reference and the verified phone route where possible. We may ask for identity confirmation before releasing details, and the response depends on local law.

Yes, you can ask us to correct an inaccurate account detail through support. State the exact field that needs changing and provide the account reference connected with it. We may check your phone verification first, because changes to account data can affect wallet and login records.

Yes. The Privacy Policy covers account-side references used to identify DANA, OVO, GoPay and QRIS activity, as well as bank transfer and virtual account records. These references help us check payment status, but you should never send a wallet PIN or banking password.

Cookies may keep your session available, remember a page setting or show how the Privacy Policy was accessed. Your browser controls many cookie choices. If you block required cookies, the mobile path from login to account pages may not work as expected.

We retain personal data for the period needed to operate the account, investigate security events, reconcile payment references or meet legal duties. When a record is no longer needed, we aim to remove or anonymise it. Deletion requests are handled where local law permits.