Reference

Privacy Policy For Your zidan 4d Account

zidan 4d Privacy Policy explains what we collect when you open an account, use a mobile device, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet details explainedAccount access choicesSupport contact path
zidan 4d Privacy Policy For Your zidan 4d Account
CONTACT ROUTES

Privacy Policy Help Near Your Account

A clear contact path helps when a Privacy Policy question is tied to a real account event, such as a phone check or a wallet status…

Account data request Use the support path inside your account to ask which personal details we hold…
Wallet privacy question If DANA, OVO, GoPay or QRIS appears with an unexpected status, send the payment…
Correction request Tell us which profile detail needs changing and why it is no longer accurate.
DATA PRACTICES

Six Privacy Policy Details We Follow

Privacy Policy decisions are easier to assess when each data use has a practical reason.

Account details

When you open an account, we use the details you submit to create your profile and complete phone verification before…

Payment matching

DANA, OVO, GoPay and QRIS status helps us connect a wallet event with the right account.

Device signals

Your browser, operating system and basic connection details can help us identify a sign-in problem or protect an account from…

Cookie controls

Cookies can remember session choices and help pages load with the account state you selected.

Account security

We use phone verification and account checks to reduce the chance that a private request reaches the wrong person.

Storage and requests

We keep records only as long as needed for account operation, transaction checks, security work or a legal requirement.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we hear most often from people deciding whether to open an account. They focus on account data, local wallet references, mobile access and requests made through support. If your case involves a particular transaction or access condition, include the account detail that lets us locate it, and remember that access depends on local law.

It covers details used for account creation, phone verification, device access, payment matching, cookies, security and support. It also explains retention and requests for access, correction or deletion. The Privacy Policy applies when you use the site from Indonesia where local law permits.

Those wallet references help us identify and reconcile a payment linked to your account. We may use a transaction identifier or status, but you should not send a wallet PIN or banking password. The same approach applies to bank transfer and virtual account references.

Yes. Send an access request through the support path inside your account and include the profile detail needed to identify you. We may complete phone verification before responding, because a Privacy Policy request must not expose account data to an unverified contact.

Tell support which account detail is inaccurate and provide the corrected value through the account contact path. We may ask for a verification step before changing it. This keeps your profile consistent across login, phone checks and payment status records.

Yes. We may process basic browser, operating system and connection signals to maintain a session, investigate login trouble or protect account access. We do not use that process to access unrelated files on your phone, and cookie controls remain available in your browser.

Retention depends on why the record exists. Account, transaction, security or support records may remain while needed for those purposes or where local law requires storage. You can ask support about a particular record, and we explain when deletion cannot be completed.

Use the support contact path inside your account and describe the privacy issue in clear terms. For wallet matters, include the DANA, OVO, GoPay or QRIS reference if relevant. Do not include passwords, wallet PINs or full banking login details.