Reference

dinamit4d Privacy Policy for Your Account

dinamit4d Privacy Policy explains what we collect when you create an account, use DANA or QRIS, and contact our support team.

Account clarityWallet recordsCookie choicesSecure access
dinamit4d dinamit4d Privacy Policy for Your Account
ASK ABOUT YOUR DATA

Get Help With Privacy Requests

A clear contact path helps when your account record does not look right. Use the support chat linked from the account or cashier area and tell us whether your request concerns phone…

Account privacy chat Open the support chat from your signed-in account and ask us to explain, correct or remove a personal detail where the request is permitted. Include the phone number linked to your account, but do not send a password or full wallet credentials.
Wallet record check If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference through the account support path. We compare it with the stored account record and explain what we can change, retain or share for payment verification.
Sign-in assistance When a phone verification step or device session blocks your privacy request, contact us from the same account where possible. We use account checks before discussing stored details, helping keep a private record away from an unverified contact.
HOW WE HANDLE RECORDS

What Your Privacy Settings Cover

Privacy choices work best when you know which record each choice affects. We separate account identity, wallet references, device activity and cookie preferences so a request can be handled against the right…

Account data

We may hold your phone number, account identifier, verification result and sign-in history to operate the requested account path. Before we discuss those details, we may match your request with the signed-in session or another account check.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can contain references needed to match a wallet event with your account. We use the reference for checking status, not as a reason to request your wallet password.

Cookies and devices

Cookies can retain a session choice or help us identify an error on a phone or desktop browser. Your device may clear these cookies, although clearing them can require another sign-in or phone verification before account access.

Account security

We use sign-in records, device signals and phone verification to identify unusual account access. If your session changes while you browse Live Roulette or Rocket Crash, we may request an additional check before showing private account details.

Retention approach

We keep personal records only for the operational, dispute, security or legal purpose connected with them. A DANA receipt or QRIS reference may remain while a status question is open, then follow our deletion or retention process.

Change requests

Ask through the signed-in support chat if your phone detail, contact record or cookie preference needs correction. We explain the result, any identity check required and any reason a record must remain where local law permits.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. We keep the wording practical, including what happens on a phone, how payment references are handled and which support route to use when you need a personal data request.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security checks, data requests and sharing where local law permits.

We use your phone number to create and verify the requested account path, help identify the correct record during support and reduce mistaken access. We do not need your wallet password for this step. Access and eligibility depend on local law.

Yes. The Privacy Policy covers references used to match DANA or QRIS activity with your account, including a receipt or status query. We may retain that reference while checking a payment question or meeting an applicable legal or security purpose.

Use the support chat from your signed-in account and state whether you want a copy, correction or clarification. Include your account identifier and the relevant record, such as an OVO or GoPay reference. We may verify your identity before responding.

No. Clearing browser cookies mainly removes local session choices and may require another sign-in or phone verification. It does not automatically delete account, support or payment-reference records held for operational, security, dispute or legal reasons.

We may use sign-in history, device signals and phone verification to spot unusual access. If you move from a phone to a desktop or a new browser, an extra check can appear before private account details are shown.

Start with the support chat available from your signed-in account or the account and cashier area. Tell us whether the request concerns personal details, cookies, phone verification or a DANA, OVO, GoPay or QRIS reference, and we will direct it to the relevant check.