Reference

obc212 Privacy Policy For Your Account

The obc212 Privacy Policy explains what account details we collect, why we use them and how you can ask about them before opening an account.

Clear data purposesWallet record contextAccount request pathCookie choices
obc212 obc212 Privacy Policy For Your Account
REQUEST ROUTES

Get Privacy Policy Help Through Account Wallet Help

A clear contact path matters when you want to question a record, correct an account detail or understand a cookie setting.

Account Wallet Help Use the Account Wallet Help route when a DANA, OVO, GoPay or QRIS reference appears in your account history and you need us to explain, correct or connect that record to the right account.
Privacy request Send a clear request about access, correction, deletion or a question about our Privacy Policy. Include the account contact detail you can verify so we can avoid discussing personal data with the wrong person.
Login support If a login check prevents you from reaching the policy or account screen, use the account help route and describe the device path you took. We use those details to separate access trouble from a data request.
DATA PRACTICES

What We Do With Your Account Records

We keep the Privacy Policy practical by connecting each data use to an account task: login, verification, cashier matching, security checks or support.

Account details

We use the contact details and verification data you provide to create and protect your account. Before discussing a record, we may ask you to confirm an account step so another person cannot receive private details.

Payment references

DANA, OVO, GoPay and QRIS references help us match a cashier action with your account. Bank transfer and virtual account records can support reconciliation, but we do not need your wallet password in a request.

Cookies and devices

Cookies and device signals can remember a session, preserve a language choice or help identify unusual access. You can manage cookie settings through your browser, although changing them may affect the policy and login path.

Account protection

Login checks, contact verification and unusual-access checks help us protect account records. If you change your phone or lose access to your contact method, Account Wallet Help can direct the next verification step.

Retention periods

We retain records only for the account, payment trace, security or legal purpose that calls for them. The period can differ by record type, so ask us through the privacy request route if you need a record-specific explanation.

Changes and questions

You can ask us to access, correct or clarify personal data connected with your account. We may need identity confirmation, and where local law permits we will explain any limit before taking action on the request.

Privacy Policy Questions About obc212

These Privacy Policy answers cover the points you are most likely to check before opening an account or using a wallet route. We keep the wording tied to actual account actions, including phone verification, cookie controls and payment reference checks. If your situation is not covered, use Account Wallet Help and identify the account detail you can confirm.

The obc212 Privacy Policy covers account details, verification records, device and cookie signals, payment references and support messages. It explains why we use each category, how we protect it, how long records may remain connected to an account and how you can send a privacy request.

We use your phone or other account contact detail for account access, verification and security checks. It also helps us identify the correct account when you ask about a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record.

Yes. The Privacy Policy covers payment references connected with your account, including DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account references. These details help us trace cashier status without asking for your wallet password.

Use Account Wallet Help and state that you want a correction under the Privacy Policy. Include the account contact detail you can verify, describe the record that looks wrong and avoid sending passwords or wallet credentials. We may request an additional account check.

You can send an access request through the privacy contact route and ask which personal data remains connected with your account. We may need to confirm your identity first. Retention can differ for login, security and payment records, so our reply may separate those categories.

Cookies can retain a session, remember a setting and help us detect unusual access. Your browser controls can limit or remove them, but the login or Privacy Policy path may not work in the same way afterward. We do not use a cookie choice as permission to request wallet passwords.

Yes. Account access and eligibility depends on local law, and the available policy or account functions may differ where local law permits. If a legal rule limits a request or service action, we will explain the relevant limit through the contact route connected with your account.