Reference

dinamit4d Privacy Policy For Indonesia Accounts

Our Privacy Policy explains what we collect when you open a dinamit4d account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesContact steps
dinamit4d dinamit4d Privacy Policy For Indonesia Accounts
HELP WITH RECORDS

Check Your Privacy Contact Route

A clear contact route matters when a login record, wallet status or account detail needs attention.

Account privacy request Use the account support path when you want to ask what personal data we hold or why a sign-up, login or verification record appears in your profile. Include your linked contact detail so we can identify the correct account before discussing private information.
Wallet record question If a DANA, OVO, GoPay or QRIS entry does not match your account activity, send the payment date, displayed status and reference shown in your cashier history. Do not send a wallet password or full security code in a support message.
Correction or deletion Ask us to correct an inaccurate detail or explain whether a deletion request can be completed. We may need to verify account ownership first, and some records may need to remain available for legal, security or transaction reasons where local law permits.
DATA HANDLING

Browse How We Handle Account Privacy

Privacy work is tied to ordinary account actions rather than a separate hidden process. We record the information needed to create access, check a submitted account step, show wallet status and respond…

Account details

We may handle the contact details you submit during account creation, plus verification results connected to that account step. This lets us distinguish your profile from another account and respond to a request about access, correction or the reason a detail is required.

Login and device signals

Login time, browser type and device signals can be recorded to help identify unusual access. These signals support account security; they do not replace your responsibility to protect passwords and verification codes. Tell support if a device record looks unfamiliar.

Cookie settings

Cookies can remember session choices, language settings and parts of your route from login to the lobby. Your browser may let you remove or block cookies, although some account functions may not work as expected after those settings change.

Wallet and cashier records

A cashier action may create a record of the chosen DANA, OVO, GoPay, QRIS, bank transfer or virtual account rail and its displayed status. We use that record to match account activity and investigate a receipt or pending status.

Retention decisions

We do not keep every record for the same period. Retention depends on why the data was collected, whether an account matter remains open and whether security or legal duties require continued storage where local law permits.

Requests and verification

When you ask to access, correct or remove personal data, we may request enough account information to confirm that the request comes from you. Send only the details needed for that check, and use the support path linked to your profile.

Find Answers About Privacy Policy

These Privacy Policy answers cover the account questions you are most likely to ask before using dinamit4d from Indonesia. They explain the practical connection between account access, device activity, cookies, wallet records and support requests. If your situation is not covered, contact us through the account support route with the smallest useful set of details. Access depends on local law, and the options available to you may vary by location.

It covers information connected with your account, including submitted contact details, verification status, login and device signals, cookie settings, support messages and cashier records. It also explains why we use those details, how retention works and how you can ask about access or correction.

We need the details required to create and protect your account, connect a verification step to the right profile and answer account requests. We use only the relevant context for a request, and access depends on local law and the options shown in your location.

Yes. The policy explains that cashier activity may record the selected rail and its status, including DANA, OVO, GoPay and QRIS. Bank transfer and virtual account records may also appear. These names describe available record types, not universal access in every location.

Use the account support path and state whether you want access to a record or correction of an inaccurate detail. Include your linked email or phone, but do not send passwords or security codes. We may verify account ownership before responding to the request.

Cookies can help remember a session or selected setting when you move from login to the lobby on a mobile browser. You can manage them through browser controls, but blocking required cookies may interrupt account access or make a saved setting unavailable.

There is no single period for every record. We consider the purpose of collection, an open account or support matter, security needs and legal requirements where local law permits. Ask support about a specific record and we can explain the applicable retention reason.

You can contact us to ask whether deletion is available for a particular record. We first verify the account request, then check whether security, transaction handling or legal duties require retention. Where local law permits, eligible data can be removed after that assessment.