Reference

melati4d Privacy Policy For Indonesia

Our Privacy Policy explains what we collect when you open a melati4d account, sign in from a phone, or use DANA and QRIS for account funding.

Clear data useWallet details explainedAccount access stepsPolicy contact path
melati4d melati4d Privacy Policy For Indonesia
CONTACT YOUR WAY

Privacy Help Near Account Access

A clear contact route matters when a Privacy Policy request concerns a locked login, a wallet reference or a device you no longer use.

Account help path Use the account help route when you want to ask what personal data we…
Wallet status request For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the transaction…
Device access concern If a phone, browser or sign-in location looks unfamiliar, contact us through the account…
DATA HANDLING MAP

Inside melati4d Privacy Controls

We apply this Privacy Policy to the practical records created while you use the account, including sign-in activity, wallet references and support messages.

Account records

We use account details to create and maintain your access, complete the clear phone verification step, and connect support requests to the correct profile. If a detail is wrong, tell us which field needs correction and provide enough account context for a safe match.

Cookies and devices

Cookies and device markers can keep a session working, remember selected settings and help identify unusual sign-ins. A phone used for Dragon Tower Mobile Play may create device activity in our records; ask support which marker relates to your request.

Wallet references

DANA, OVO, GoPay and QRIS actions can produce a reference, amount status and time record linked to your account. We use these fields to match the cashier event and investigate a receipt question, rather than storing more wallet access data than needed.

Account protection

Phone verification and sign-in records help us check that an account request comes from the right person. Never send a password, PIN or one-time code in a support message. If access looks unusual, report the device and time so we can review the event.

Retention requests

We keep records only for the period needed for account operation, payment matching, security checks and applicable legal duties. You can ask which category applies to your data and why it remains stored; where local law permits, we explain the available deletion route.

Policy changes

If this Privacy Policy changes, we will present the updated wording on the policy page and identify the relevant date. Check this page before opening an account or returning on a new device, especially when access depends on local law or your data request has an open status.

Privacy Policy Questions For melati4d

These Privacy Policy answers address the account and device situations you are most likely to face when using melati4d from Indonesia. We focus on the records that support phone verification, wallet status, sign-in protection and contact requests. If your situation is not covered, use the account help path with a short description and the relevant date, without sending passwords, PINs or one-time codes.

The Privacy Policy covers account details, phone verification, sign-in activity, device markers, cookies, support messages and payment references. It explains why we use each category, how it supports account access or status checks, and how you can ask about correction, retention or another available request.

We use the phone verification step to check account access and connect a request to the right profile. The related record can help us investigate an unfamiliar sign-in or account-help request. You should not send your verification code to support or any other person.

Yes. The Privacy Policy covers transaction references and status data connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those details to match a cashier event and handle a receipt or status request.

Use the account help path and state the account detail that needs correction, such as a contact field or device record. Include your account identifier and the reason for the request, but leave out passwords, PINs, wallet credentials and one-time codes.

Retention depends on the type of record and the reason it was created. Account access, payment matching, security checks and legal duties can require different periods. Ask support which category applies to your data and why it remains stored at the time of your request.

Yes. You can ask which cookies or device markers relate to your session, such as a phone used to open Dragon Tower Mobile Play. We use these records for session choices and access checks, and support can explain the relevant category without requesting your password.

Yes. Account access and any related eligibility depends on local law. Our Privacy Policy explains how we handle data for an account request, but it does not change the rules that apply in your location. Contact support if you need a policy clarification for your situation.