Reference

Open ibc4d Privacy Policy Clearly

Our Privacy Policy explains what we collect when you open an ibc4d account, sign in on mobile, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPolicy requests

Explore Our Lobby Read FAQ

Read How Wallet Data Is Used

ibc4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies when you create an account, complete phone verification, sign in, or ask us to check a wallet transaction. We may handle contact details, verification records, login events, device signals and payment references needed to match a DANA, OVO, GoPay, QRIS, virtual account

1
or bank transfer request to your account. We do not describe these records as game activity; they support account control, payment status and fraud checks. We retain records only for the period needed for the stated purpose, account support, dispute handling or legal duties that apply
2
where local law permits. You can ask what data we hold, request a correction, or ask about deletion by contacting our support path. Some records may need to remain while a payment or account matter is open. Check this page before using the lobby, and contact
3
us if a policy point does not match your situation.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT YOUR WAY

Reach Support About Privacy Policy

A clear support route helps you act on this Privacy Policy without guessing where to send a request.

HANDLING DETAILS

Explore Your Privacy Choices

Privacy depends on practical controls, so we describe the account actions behind this policy. Our handling covers sign-in records, device behaviour, cookies, wallet references and retention rather than vague promises.

Account records

We may keep your name, contact details, phone verification result and account events to maintain sign-in control. These records help us respond when your login path or account details need checking.

Device signals

A mobile browser or desktop session can create device and login signals. We use them to identify unusual access, protect your account and connect a support request to the correct session.

Cookie settings

Cookies can remember a session and support page preferences. Your browser controls can remove or block them, though doing so may require another sign-in before account pages load.

Wallet references

For DANA, OVO, GoPay, QRIS, virtual account and bank transfer requests, we handle references and status details needed to match the payment step, not a request for your private password.

Retention checks

We keep records for the purpose that created them, open payment or account questions, and legal duties where local law permits. When those needs end, our retention process can remove or restrict them.

Change requests

You can ask for access, correction or deletion through support. We may request account verification first, then explain any record that must remain for an unresolved payment or legal reason.

Browse Privacy Policy Answers

These Privacy Policy answers address the account and wallet questions you may search before opening ibc4d. They cover what we collect, how you can request a change, and why a verification step may be needed for private records.

It covers data connected with your account, phone verification, login sessions, device signals, cookies, support requests and wallet references for DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity.

Yes. Contact support through the account help path and ask for an access request. We may verify that you control the account before describing or sending private records connected with your login.

We use payment references, dates and visible status details to match a DANA or QRIS step with your account. We do not need your password to investigate a receipt or pending status.

Cookies may keep a session active or remember page preferences on your phone. You can manage them in your browser settings; blocking them may cause another sign-in or limit page functions.

Send support a correction request through account help and identify the field that needs changing. We may confirm ownership first, particularly for phone details linked to account access.

You can ask about deletion at any time. We assess the request against open wallet questions, account security needs and legal duties; where local law permits, records no longer needed can be removed or restricted.

The page is available for policy reading, while account eligibility and data rights can depend on local law. Contact support if you need the rule applied to your Indonesian account situation.

Open ibc4d Privacy Policy Clearly

Reach Support About Privacy Policy

Explore Your Privacy Choices

Account records

Device signals

Cookie settings

Wallet references

Retention checks

Change requests

Browse Privacy Policy Answers

01 What does the ibc4d Privacy Policy cover?

02 Can I request my ibc4d account data?

03 How does the Privacy Policy handle DANA or QRIS data?

04 Does ibc4d use cookies on my phone?

05 How do I correct details under the Privacy Policy?

06 When can ibc4d delete my personal data?

07 Does access to the Privacy Policy depend on local law?

Related Pages