Reference

holand4d Privacy Policy For Your Account

Our Privacy Policy shows what we collect when you open a holand4d account, use DANA or QRIS, and move between mobile lobby pages such as Wayang Legend Slots.

Account dataCookie choicesWallet recordsAccess requests
holand4d holand4d Privacy Policy For Your Account
DATA HELP ROUTE

Three Ways To Ask About Privacy

A clear contact route helps you deal with a data question without searching through unrelated account pages.

Account privacy request Ask us to locate the personal data attached to your account, including phone verification details, sign-in records, and support messages. We first confirm that you control the account before sharing account-specific material or changing the contact details used for access.
Wallet record question Send the payment reference and method when your question concerns DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. We can compare the reference with the stored status record while avoiding a request for your wallet password or private security code.
Cookie choice request Tell us if you want to ask about cookies or device storage used on the mobile path. We can explain the purpose of the relevant record and apply available changes after checking your account and the browser or device from which you contacted us.
SIX DATA CONTROLS

What Your holand4d Policy Covers

Privacy work is tied to practical account events rather than broad statements. We separate contact details from payment references where our systems allow, limit access to records according to support needs, and…

Account collection

We collect details you submit during account opening and phone verification, plus records created when you sign in. These details help us match a privacy request to the correct account and prevent disclosure to a person who cannot confirm account control.

Payment references

A DANA, OVO, GoPay, or QRIS action can create a reference, amount, status, and time record. Bank transfer and virtual account activity can create similar records. We use these details to reconcile status and answer receipt questions without storing wallet passwords.

Cookies and storage

Cookies and local device storage can keep a session active, remember a selected setting, or help us identify an interrupted sign-in. Your browser controls whether some storage is accepted. Removing it may require you to complete phone verification again.

Security checks

We use sign-in time, device signals, phone verification, and account changes to identify access that needs an extra check. A withdrawal verification record may also be retained when it is necessary to match an account request with the correct payment status.

Retention period

We keep personal data only while it supports account security, payment reconciliation, support handling, dispute checks, or a legal requirement. When a record is no longer needed for those purposes, our retention process removes it or separates it from direct account identification.

Changes and deletion

You may ask us to correct inaccurate account details, explain a stored record, or delete eligible data. Some records may remain when needed for security, payment reconciliation, dispute handling, or legal duties. We explain the reason if a request cannot be completed fully.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account and device questions you are most likely to have before using holand4d. They cover what we collect, how wallet references are handled, why a phone check can appear, and how to request access or correction. If your situation is not listed, use the account support route with the smallest amount of personal detail needed to identify your request.

It covers data collected when you open an account, complete phone verification, sign in, use cookies, contact support, or create a payment reference through DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains retention, security checks, access requests, and eligible deletion.

Phone verification helps connect an account request to the correct account and reduces the chance that another person receives private details. We may request it before account access or before answering a data request, with access handled where local law permits.

No. When you use DANA or QRIS, we retain operational references such as method, status, time, and account link for reconciliation and support. We do not need your wallet password or private security code to check whether a payment record matches your account.

Cookies or local storage can keep your session active, preserve a setting, and help identify an interrupted sign-in on a phone or tablet. You can manage browser storage through device settings. Clearing it may sign you out and trigger phone verification on your next access.

Yes, you can contact us through the account support route and request the personal data connected with your account. Include the account contact detail and request type, but do not send a wallet password. We may verify account control before preparing the response.

You can ask us to correct inaccurate details or delete eligible records. We may retain information needed for account security, payment reconciliation, withdrawal verification, disputes, or legal duties. If deletion is limited, we explain which operational or legal reason requires continued retention.

The policy is intended for supported Indonesian access, including your use from Semarang, where local law permits. Local rules can affect eligibility, retention, and the way a request is handled. Contact us through the account route if you need a location-specific privacy response.