Reference

dipo4d Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a dipo4d account, why we use it, and how you can ask about it.

Account clarityWallet recordsCookie choicesPolicy requests
dipo4d dipo4d Privacy Policy for Your Account
CONTACT THE TEAM

Contact Us About Account Data

A privacy question should not be mixed with a wallet-status question. Use the support route inside your account when you need help identifying a record, checking a phone-verification detail or asking why a DANA or QRIS event is attached to your profile. Include the email or phone detail linked to your account, but never send a password or full payment credential.

Team online

Account help

Open the support link from your signed-in account and describe the Privacy Policy request, such as a correction, access question or data-use concern.

Wallet record

For an OVO, GoPay or bank-transfer record, share the date, amount reference and wallet type only; we use those details to locate the relevant account event.

Login concern

If a new device reaches your account unexpectedly, contact us through account help and explain the device path, browser and approximate time without sharing your password.

DATA HANDLING

Check How We Handle Your Data

We keep privacy work tied to practical account events rather than collecting details without a purpose.

Account details

We use your account contact details and phone-verification status to create, protect and maintain your sign-in path. Ask us to correct a detail when your account record no longer matches you.

Cookies

Session cookies can keep your sign-in path working and help us recognise an unusual browser change. You can review cookie controls in your browser and ask support about a related record.

Device signals

A mobile browser, tablet or desktop may send device and session signals during account access. We use these signals for protection and investigation, not as a substitute for your account details.

Wallet references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references may appear in payment records. We use the reference, date and status to resolve account questions.

Retention requests

Records are kept only as long as needed for the stated account, safety or legal purpose. Ask support how a category is retained and whether a lawful removal request can apply.

Policy changes

If this Privacy Policy changes, we will present the updated wording through the dipo4d policy path. You can ask what changed before using your account again.

Browse dipo4d Privacy Policy Answers

These answers address the searches we hear most often about the dipo4d Privacy Policy. They explain account data, wallet references, cookies, device access and the practical route for making a request, while access remains where local law permits.

It covers account details, phone verification, login and device signals, cookies, wallet references and records connected with account activity. It also explains request routes, retention questions and policy changes.

Phone verification helps connect account access with the correct contact detail and helps us investigate an unusual sign-in. We use its status for account protection and related support requests.

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

During access, we may receive device type, browser signals, session details and approximate location signals. These help identify unusual account activity when you move between mobile and desktop paths.

Use the support link inside your account and state whether you want access to a data category or a correction. Include your linked contact detail, but do not send passwords or secret wallet codes.

Retention depends on the purpose for which a record was collected, account protection needs and applicable legal requirements. Ask support about a specific category, such as a QRIS or bank-transfer reference.

Yes. You can ask which session or protection purpose relates to a cookie record. Your browser also provides cookie controls, although changing them may affect the account access path.