Reference

neng4d Privacy Policy for Your Account Data

Our Privacy Policy explains how we handle the details connected to your neng4d account, from phone verification before account access to wallet records for DANA, OVO, GoPay and…

Account dataWallet recordsDevice choicesPolicy access
neng4d neng4d Privacy Policy for Your Account Data
HELP WITH YOUR DATA

Reach Support About Privacy Questions

A clear contact path matters when a name, phone detail or payment reference needs attention. Sign in and use the support route beside your account and cashier area; tell us which record you mean, such as a QRIS receipt or phone verification result. We use the details in your request to confirm ownership, investigate the matter and reply with the next policy step.

Team online

Account support route

Open support from your signed-in account when you need to ask about stored profile details, phone verification or a correction request connected with your Privacy Policy rights.

Wallet record enquiry

Include the relevant DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference so we can locate the payment record without asking for your wallet password.

Privacy request details

State whether you want access, correction, deletion or an explanation of data use. We may ask for account confirmation before discussing personal records through the support path.

YOUR DATA CONTROLS

Privacy Choices Across Account And Device

Our handling process separates account identity, wallet references and technical session data so each request can be checked against the right record.

Account security

Phone verification is checked before account access, and we use sign-in and session details to detect unusual activity. Do not share your password or verification code with anyone contacting you.

Payment separation

A DANA, OVO, GoPay or QRIS reference helps us reconcile a cashier record, while bank transfer and virtual account details support matching. We do not request your wallet login credentials.

Cookie controls

Cookies can remember session status and selected settings so your privacy choices remain available while browsing. You can manage or clear cookies through your browser controls, though some account functions may need them.

Device signals

We may record browser type, device indicators, language and session timing to protect account access and diagnose errors. These details help us distinguish a normal mobile return from unusual sign-in activity.

Retention approach

We keep personal records only for the period needed for account operation, security checks, payment reconciliation and legal duties. Transaction records may need longer storage than optional profile settings.

Change requests

Ask through the signed-in support route to view, correct or remove eligible data. We verify the account owner first and explain any record that must remain for security or legal reasons.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before account creation or a data request. Each response points you toward the relevant account step, wallet record or support route, with access and eligibility handled where local law permits.

It covers account details, phone verification, wallet references, device and browser signals, cookies, security checks, retention and requests to access or change eligible personal data.

We use the verification result to connect you with the correct account and protect sign-in access. It also helps support confirm ownership before discussing private account details.

Yes. The policy covers DANA and QRIS references used to match cashier activity, along with OVO, GoPay, bank transfer and virtual account records. We do not need wallet passwords.

You can request a correction through the signed-in support route. Tell us which detail is wrong, such as a phone number or account setting, and we will verify ownership before updating it.

Cookies can retain session status and selected settings while you browse. Your browser lets you clear or manage them, but removing required cookies may affect sign-in or policy preference storage.

Retention depends on the purpose of each record. Security and payment reconciliation may require longer storage, while eligible settings can be removed when no account or legal need remains.

Use the support route inside your account and specify access, correction, deletion or an explanation request. We confirm ownership first and explain any data that must remain under local law.