Reference

target4d Privacy Policy for Account Data

target4d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, use DANA or QRIS, and contact our support route.

Account dataWallet recordsCookie choicesPolicy requests

Explore Our Lobby Read FAQ

How DANA And QRIS Appear In Policy Records

target4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details needed to create and protect your account, such as your contact details, verification status, sign-in events, device signals and support messages. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain payment references and

1
status data rather than unnecessary wallet credentials. We use these records to match an account action, check a receipt and investigate a stalled status. Cookies and similar browser storage help keep sign-in sessions working and help us understand policy-page use. We restrict internal access according to
2
work needs and retain records for the period needed for account support, security checks and legal duties. Account availability and any eligibility assessment depends on local law. You can ask us to explain a record, correct certain details or clarify a retention question through the support
3
path below.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where To Ask About Privacy Policy Changes

A clear contact route matters when a record looks unfamiliar or your account details need correction.

SIX DATA CONTROLS

Six Controls Behind Your Account Privacy

We handle this policy area through practical account controls rather than broad promises. Your records move through account creation, phone verification, wallet status checks and support handling, while browser cookies remain part…

Collection at account opening

We collect the contact and verification details needed for account access, then connect those details to sign-in activity so a phone verification step can be checked when you return.

Device and session signals

A mobile browser may create session and device signals that help us recognise an account path, investigate repeated sign-ins and protect the transition from login to the lobby.

Cookie choices

Cookies can keep a session active and remember page settings. You can manage browser cookie controls, though limiting them may interrupt sign-in or parts of the policy request path.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use transaction references and status details to match account actions without asking for private wallet credentials.

Retention checks

We retain account, support and payment-reference records only while they serve account assistance, security review or a legal requirement, then assess whether continued storage still has a clear reason.

Requests and corrections

You can contact support to ask what personal details relate to your account, request a correction or question a retention decision; we may verify account ownership before responding.

Privacy Policy Questions For Indonesian Accounts

These Privacy Policy answers address the checks people commonly make before opening an account or using a mobile session. We keep each response tied to account records, payment references, cookies and contact steps. If your question concerns a particular record, mention the account step, device path or wallet reference so our support route can investigate it accurately.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, wallet references and retention. It also explains how to ask for access, correction or clarification.

Our policy uses payment references and status information for DANA and QRIS activity. Do not send a wallet PIN or security code to support; those credentials should remain with you.

Phone verification helps connect the person opening an account with the contact detail used for access. It can also help us check an unusual sign-in or a request about account records.

Open the support chat from your account area and state that you want a personal-data request. We may ask for account details that confirm ownership before preparing a response.

Yes. Send the specific detail you believe is wrong through the account support route, along with a safe way to verify ownership. We will assess the requested correction against account records.

Cookies can maintain your sign-in session and save page settings. Your browser controls can restrict them, but doing so may interrupt account access or the policy contact process.

Account availability and related processing depends on local law. If you are unsure whether access is available in your location, contact support before sending additional account or payment details.

target4d Privacy Policy for Account Data

Where To Ask About Privacy Policy Changes

Six Controls Behind Your Account Privacy

Collection at account opening

Device and session signals

Cookie choices

Wallet references

Retention checks

Requests and corrections

Privacy Policy Questions For Indonesian Accounts

01 What does the target4d Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS PIN?

03 Why does target4d need phone verification?

04 How can I request my personal data under the Privacy Policy?

05 Can I ask target4d to correct account information?

06 How do cookies affect my Privacy Policy choices?

07 Does the Privacy Policy apply everywhere in Indonesia?

Related Pages