Reference

Privacy Policy For Your mini4d Account

Our Privacy Policy explains what we collect when you open a mini4d account, use the casino lobby, or check DANA and QRIS status.

Clear data useWallet record contextCookie choices
mini4d Privacy Policy For Your mini4d Account
REQUEST HELP

Get Help With Privacy Requests

A privacy question should have a clear route, especially when it concerns a wallet receipt or an account login. Contact our account support route with the email or phone detail attached to your mini4d account, and tell us whether your request concerns access, correction, deletion, cookies, or a payment reference. If you are checking a DANA, OVO, GoPay, or QRIS record, include the visible status and date rather than sending your full password. We may ask for an account step to confirm that the request comes from you.

Team online

Account data request

Use the account support route when you want to ask what personal data we hold, request a correction, or ask how a login record is connected with your account. We may verify your account details before sharing or changing anything.

Wallet record question

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, send the payment reference and visible status through support. We use that narrow detail to locate the relevant record without asking you to disclose your password.

Cookie preference

If a browser cookie concerns you, contact support with the device path you used, such as mobile browser or desktop browser. We can explain the cookie purpose and the available setting while keeping your account request separate from wallet activity.

DATA HANDLING

How mini4d Handles Account Data

Privacy is part of the account path, not a separate promise shown only after a problem.

Account details

We use contact and verification details to create your account, confirm requested access, and reply to account cases.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references help us match a wallet event with your account.

Cookies and devices

Cookies can remember a browser setting, while device and session signals help us spot an unusual login path.

Account security

We use login activity, verification steps, and session signals to help protect your account.

Retention period

We retain personal data for the period needed to provide account support, resolve payment status questions, protect the service, or…

Changes and contact

You can ask about your stored data, request a correction, or ask about deletion through account support.

Privacy Policy Questions About mini4d

These common questions focus on the parts of our Privacy Policy that affect your account, device, wallet records, and support requests. We keep the answers practical so you know what to send, what we may check, and when local requirements affect access. If your situation is not covered, use the account support route with only the details needed to identify your request.

The mini4d Privacy Policy covers account details, login and device records, cookies, support conversations, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains retention, security handling, and how to request access or correction.

We collect account details to create and maintain your login, and device or session signals to help identify unusual access. These records also let us investigate a wallet status question or support case without asking you to repeat every account step.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity on your account. Send only the reference and visible status when asking us to check a payment record.

Use the account support route and state that you want to request your personal data. Include the email or phone detail attached to your account and describe the records you mean, such as login history, cookies, support messages, or payment references.

You can request a correction or ask about deletion through support. We first confirm that the request comes from you, then check whether the record is still needed for account security, payment support, or applicable legal duties before changing or removing it.

On a mobile browser, cookies may retain settings and session details, while device signals help us assess unusual login activity. You can adjust cookies in your browser settings. Some changes may require you to repeat login or verification steps.

The policy is available for you to read, but account access and eligibility depends on local law. Our data handling applies where local law permits. If a legal requirement affects your request, support can explain the relevant account step without requesting your password.