Reference

Privacy Policy for modal4d Accounts

Our Privacy Policy explains what account, device and wallet details we collect when you open modal4d, how we use them, and how you can ask about your records.

Account clarityWallet recordsCookie choicesAccess requests
modal4d Privacy Policy for modal4d Accounts
HELP WITH PRIVACY

Where To Ask About Your Data

A direct support request helps us connect a privacy question with the right account record without asking you to repeat the full story.

Account request Ask us to explain the personal details linked to your modal4d account, including the…
Wallet receipt For a DANA, OVO, GoPay or QRIS question, include the transaction reference and approximate…
Device access If a browser or phone session looks unfamiliar, tell us the device path and…
DATA HANDLING

Six Practical Privacy Commitments

Privacy is easier to assess when the handling steps are visible. We separate account access needs from payment investigation, explain why cookies appear, and keep requests tied to…

Account details

We use your account details for sign-in, phone verification, support identification and records connected to your account.

Payment matching

Payment data is used to match a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference with the correct…

Cookies

Necessary cookies can keep a login session, remember a selected language setting and maintain the route between account pages.

Security signals

We may examine device, browser, network and session signals when an access pattern appears unusual.

Retention

We keep account, support and transaction records only for as long as they are needed for the stated account, security…

Change requests

You can ask what personal data we hold, request a correction, question a use or ask about deletion where applicable.

Privacy Policy Questions For modal4d

These answers address the searches we most often associate with a Privacy Policy: what we collect, why wallet references appear, how cookies work and how to request a change. They are written for your account journey in Indonesia, while access and eligibility depends on local law. If your situation is not covered, send the support team the account context and the specific record you want clarified.

The modal4d Privacy Policy covers personal details, phone verification, device and browser signals, cookies, support messages and payment references connected with your account. It explains why we use each category, how we protect account access and how you can ask about, correct or delete eligible records.

Phone verification helps us connect account access with the contact detail you provided and adds a security check before private account records are shown. We may use that verified contact when handling a data request, but we do not need your password or full wallet credential.

Yes. The Privacy Policy includes references and status details linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account checks. We use those records to match a payment question to your account, investigate receipts and avoid exposing unrelated wallet information.

We use necessary cookies and related browser storage to keep a login session, retain required preferences and move you between account pages. You can adjust cookie controls in your browser. If you block necessary storage, you may need to sign in again or repeat part of the account path.

You can contact support to ask what personal data is linked to your account or to request a correction. State the verified account contact, identify the record and explain the change. We may confirm account ownership before sharing or editing private details.

We retain account, support, security and transaction records for the period needed for the purpose explained in the Privacy Policy, including account protection, payment checks, disputes or legal duties. When that purpose ends, handling may involve deletion, anonymisation or restricted retention where applicable.

Use the account support path and describe the privacy concern in plain English, whether it involves login access, a device session, a cookie or a wallet receipt. Include only the reference needed to locate the issue. We may ask for ownership checks before discussing account data.