Reference

obc4d Privacy Policy for Your Account

The obc4d Privacy Policy explains what we collect when you open an account, verify your phone, browse the lobby or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record detailContact request path
obc4d obc4d Privacy Policy for Your Account
CONTACT PATHS

Privacy Policy Help Beside Your Account

A direct contact route helps you resolve a privacy question without explaining your whole account history.

Account support form Send a Privacy Policy question from the support path connected to your account.
Payment record check For DANA, OVO, GoPay or QRIS questions, attach the receipt reference rather than full…
Access request route Ask us to locate, correct or remove eligible personal data through the same support…
DATA CONTROL

What We Do With Your Account Data

Privacy is handled through practical account controls rather than broad promises. We separate login activity, verification details, payment references and support conversations so each record has a clear…

Collection choices

We collect details needed for account access, phone verification, security review and payment matching.

Cookie controls

Cookies and similar browser storage can remember sign-in preferences, session state and security signals.

Account security

Phone verification, login event records and device signals help us identify unusual access.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us connect a receipt with the correct account without requesting wallet credentials.

Retention periods

We keep account, security and payment records only for the period needed for the stated purpose, account protection and applicable…

Change requests

You can ask us to access, correct or delete eligible data through account support.

Privacy Policy Answers for obc4d

These Privacy Policy answers address the account questions we expect before you create access or connect a local wallet. Each response focuses on a practical step, from phone verification and browser storage to payment references and requests for a copy of your data. If your situation is unusual, send the details through the account support path.

It covers account details, phone verification, device and login events, cookies, support messages, payment references and retention. It also explains your routes for access, correction and deletion where local law permits.

We use your phone number for account identification, verification and security messages. It helps us confirm ownership before discussing personal data or changing account details connected with DANA, OVO, GoPay or QRIS.

A QRIS payment may create a reference, amount, status and time record linked to your account. We use those details to match receipts and investigate status questions without asking for your wallet password.

Required cookies or browser storage can retain session and security settings on your phone or desktop browser. Blocking them may sign you out or require phone verification again, but it does not give us your password.

Yes, send an access request through account support with your registered phone number or another ownership reference. We will identify eligible records and explain any limits that depend on local law.

Use the support route to name the incorrect field and provide the matching account reference. We may verify ownership first, then update eligible account details or explain why a payment record must remain unchanged.

We remove or anonymise eligible data after its stated purpose and required retention period end. Security, payment or dispute records may stay longer when needed for account protection or applicable duties.