Reference

bumi4d Privacy Policy For Your Data

Clear account, wallet, and device-data choices sit behind the bumi4d Privacy Policy, so you can understand what we collect before opening an account.

Account dataWallet recordsDevice choicesPrivacy requests
bumi4d bumi4d Privacy Policy For Your Data
HELP WHEN NEEDED

Get Privacy Help Near Account Support

A clear contact path matters when a login record or wallet reference needs checking.

Account help route Use the account-help path when you want to ask what personal data is linked…
Wallet status check For DANA, OVO, GoPay, or QRIS questions, share the payment reference rather than a…
Privacy request Ask for a copy, correction, or removal assessment through the same support route.
ACCOUNT SAFEGUARDS

Keep Your Login And Device Choices Clear

Privacy controls work best when the account steps are clear. We separate ordinary lobby activity from details needed to verify a login, check a wallet reference, or investigate a security concern.

Data handling

We use account details, phone verification results, payment references, and support messages for the purposes stated in this Privacy Policy. We do not need your wallet password to investigate a DANA or QRIS receipt.

Cookie choices

Cookies help keep necessary sign-in and page functions working. Your browser can manage or remove them, although changing required cookies may affect how an account session or policy page behaves.

Login security

Phone verification helps connect account access with the correct person. Keep your sign-in details private, and contact account help if a device session or verification record looks unfamiliar.

Retention timing

We retain account, payment, and support records for the operational, security, dispute, and legal needs stated in the policy. A deletion request is assessed against those duties before action is taken.

Request changes

You may ask us to correct account details, clarify a payment reference, or assess removal of personal data. Describe the exact record so we can avoid changing the wrong account field.

Policy contact

Privacy questions belong in the account-help route, including questions about device behaviour after mobile login. We may ask for enough account context to confirm the request without requesting secret wallet credentials.

Privacy Policy Answers For bumi4d

These Privacy Policy answers focus on the account actions you are most likely to take: creating access, verifying a phone, checking a wallet reference, and asking for a data change. We keep the wording practical for Indonesian account holders using mobile or desktop devices. If your question concerns eligibility or access, the answer depends on local law and the details of your request.

It covers account details, phone verification, wallet and bank references, device signals, cookies, support messages, retention, security handling, and the ways you can request access, correction, or removal.

We use phone verification to connect account access with the correct login and to investigate unusual activity. The Privacy Policy explains how that record is used and how you can ask about it.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay, and QRIS, plus bank transfer and virtual account records used to resolve account questions.

Contact us through the account-help route and identify your account, the data period, and the record you want copied. We may verify the request before sharing account-linked details.

Yes. Send the specific account field or payment reference that needs correction through support. Include the reason and supporting context, while keeping passwords and wallet security codes private.

Retention depends on the operational, security, dispute, and legal purposes described in the Privacy Policy. A removal request is reviewed against those purposes before we confirm what can change.

Yes. It explains how cookies and device signals may support a mobile login session, account security, and page functions. Browser settings can affect required cookies and session behaviour.