Reference

dot 4d Privacy Policy For Your Account

The dot 4d Privacy Policy explains what we collect when you open an account, use the lobby, or check a wallet status, and why each detail is needed.

Account clarityWallet recordsDevice controlsPolicy access
dot 4d dot 4d Privacy Policy For Your Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear contact route matters when you want to understand a Privacy Policy decision or correct an account detail.

Account support path Open the support contact route from your signed-in account and choose the privacy subject that matches your request. We can then compare your phone verification status with the account record without requesting your login password.
Payment record check For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, share the transaction reference and date shown in your receipt. We use that narrow detail to trace the wallet record and avoid collecting unrelated documents.
Access correction request If your name, phone detail, or device access record needs correction, describe the change through the available support channel. We may ask for an account check before making an update, so another person cannot alter your profile.
SIX DATA SAFEGUARDS

What Our Privacy Policy Covers

We treat privacy as an operating task rather than a footer link. The Privacy Policy sets out how account data, wallet references, device signals, cookies, support messages, and security records move through…

Account details

We use the details you provide during account opening to create your profile and complete phone verification before access. Keeping the phone number current helps us match a privacy request to the correct account and reduces mistaken changes.

Device signals

Login may create a device or session record so we can notice an unusual access pattern. On mobile, this supports the path from login to the lobby; it does not give us access to unrelated files, photos, or messages on your device.

Wallet activity

A payment reference can be linked to your account when you use DANA, OVO, GoPay, QRIS, bank transfer, or virtual account steps. We retain the status needed to investigate a receipt or cashier question without treating wallet data as public.

Cookies and sessions

Cookies and session tools help keep you signed in, remember necessary choices, and connect a request to the right page. You can manage browser controls, but disabling required cookies may interrupt phone verification, account access, or a saved session.

Security handling

We limit account access through login checks and do not ask you to disclose a password or wallet PIN in a support message. If a session appears unusual, we may pause the request while we confirm that you control the linked account.

Retention and changes

We keep records only while they serve account support, security, dispute handling, or a legal duty. Where local law permits, send a request to correct, access, or remove eligible data through support, and we will explain any limit before acting.

Privacy Policy Answers For dot 4d

These Privacy Policy answers address the account and wallet questions you may search before opening access. We keep each answer tied to a practical route, including phone verification, mobile sessions, payment references, cookies, and support requests. If a request depends on a legal requirement, we will explain that boundary in the response.

It covers account details, phone verification, device and session signals, cookies, support messages, security records, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains retention, correction requests, and how to contact us.

We use your phone number to create and identify your account, complete the phone verification step before access, and connect a privacy request to the right profile. Keep it current so we can distinguish your request from another person’s account request.

Yes. It covers necessary device and session signals used to support login, recognise unusual access, and keep the mobile path connected to the lobby. We do not use this process to read unrelated files, photos, contacts, or messages on your device.

We may link a payment reference, status, amount, and date to your account so support can check a receipt or wallet issue. The Privacy Policy treats these as account records, and we ask for a reference rather than a wallet PIN or password.

Where local law permits, you can ask to access or correct eligible account data through the signed-in support path. Include your linked phone detail and describe the requested change. We may verify account control before sharing or changing any record.

We keep data for the period needed to provide account support, protect login sessions, resolve payment or account disputes, or meet a legal duty. When a record no longer serves one of those purposes, our handling follows the applicable retention process.

Use the support contact route available after you log in and label the request as privacy-related. For wallet questions, add the payment reference and date; for account changes, include your verified phone detail. Access depends on local law and account checks.