Reference

sbc4d Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an sbc4d account, verify your phone, browse from a mobile device, or use DANA and QRIS.

Clear data purposesPhone verification explainedWallet activity coveredYour request path
sbc4d sbc4d Privacy Policy for Your Account
CONTACT PATHS

Get Help With Privacy Requests

A direct account-help route keeps a Privacy Policy request connected to the correct record.

Account help Use the account support path for requests to access, correct, or remove personal details.
Payment status For a privacy question tied to DANA, OVO, GoPay, QRIS, or bank transfer, provide…
Access concern If a mobile sign-in or recognised-device check blocks your request, tell us the device…
ACCOUNT DATA CARE

How We Handle Your Policy Rights

Our Privacy Policy is practical: it connects each data use to an account step you can recognise.

Data collection

We collect the details needed for an account, including your contact data, phone-check result, sign-in events, device signals, support messages…

Cookie choices

Cookies can preserve a sign-in session and remember functional choices on your mobile browser.

Account security

A phone verification step helps us distinguish an account holder from an unauthorised requester.

Record retention

We retain account, support, security, and payment-reference records for operational, dispute, or legal reasons.

Correction requests

If your phone, contact detail, or account record is inaccurate, send a correction request through account help.

Who receives requests

Our support and account operations teams handle Privacy Policy requests.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the practical steps for data access, wallet records, cookies, phone verification, and contact requests, so you know what to prepare when contacting us.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification helps us confirm that the person requesting account data is connected to the account. We may ask for this step before correcting, disclosing, or removing account details.

Yes. Use the account-help path and request access to your stored details. Describe the account phone number and the records you want checked; we may verify ownership before replying.

Yes. The policy covers payment references and status data linked to DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity. We do not need your wallet password for this check.

Cookies help preserve a session and functional choices in your mobile browser. Browser controls can remove them, but you may need to complete phone verification again when returning to your account.

We keep records while they serve account operation, security, dispute handling, or legal needs. After that need ends, our process removes or de-identifies the relevant records.

Send the request through account help with the affected account detail and your requested action. We check ownership and local requirements first; access depends on local law and the record involved.