Reference

bahagia4d Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use, store and protect the details connected with your bahagia4d account, including phone verification, device access and wallet records.

Clear data purposesWallet record contextAccount request pathPolicy access
bahagia4d bahagia4d Privacy Policy for Your Account
PRIVACY HELP PATH

Ask About Data From Your Account

A direct support request is the quickest way to ask about a Privacy Policy matter tied to your account.

Account privacy request Use our support chat while signed in and state whether you want to access…
Wallet record query For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the date…
Security concern If a device, phone number or sign-in activity looks unfamiliar, contact support promptly from…
DATA CONTROL DETAILS

What We Do With Your Account Data

Privacy work covers more than the form you complete at registration. We also consider cookies, device behaviour, account security and the records created when you move between a…

Account details

We use your submitted account details to create the requested profile, complete phone verification and respond to account requests.

Device signals

A phone browser or desktop browser may provide device type, browser version, access time and security signals.

Cookies

Cookies can remember sign-in preferences, maintain page settings and support security checks.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account can be matched to an account request.

Retention

We keep account, security and transaction records only while they serve the stated purpose or an applicable requirement.

Change requests

You can ask us to correct an inaccurate detail, explain a data use or assess a removal request through support…

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the questions we expect before an account is opened or a support request is sent. They focus on the records that matter in practice: phone verification, browser access, wallet references and account changes. If your question is more specific, use the support path and include only the minimum detail needed to locate your account.

It covers account details, phone verification, device and browser signals, cookies, payment references, security records, retention and your requests to access or correct data. Access depends on local law.

We use the phone number to create and verify the requested account path, support sign-in checks and connect your privacy request with the correct profile. We do not need your wallet PIN.

Yes. A DANA or QRIS reference can be linked to an account record so we can check a payment status or answer a receipt question. We do not request the wallet security code.

A phone or desktop browser may provide device type, browser version, access time and security signals. We use these details for sign-in protection and support checks, not to read unrelated device content.

We retain account, security and transaction records while they serve the stated purpose or an applicable requirement. We then remove or separate records where practical under our retention process.

Contact support chat while signed in, identify the detail that needs correction and provide the account identifier requested by our team. We may confirm ownership before changing phone or profile data.

You can submit a removal request through support chat. We assess the request against account security, transaction records and applicable requirements, then explain what can be removed and what must remain.