Reference

nau4d Privacy Policy For Your Account

Your account details, device signals and wallet records receive clear handling rules under the nau4d Privacy Policy, so you can understand what supports login, DANA or QRIS status…

Clear collection purposesWallet record controlsDevice access choicesPolicy request path
nau4d nau4d Privacy Policy For Your Account
REQUEST HELP

Privacy Support For Wallet And Login Records

A privacy request should be easy to separate from a stalled wallet or login matter, so we keep the request path focused on the record you want us to check. Tell us the account identifier, the email or phone detail connected to it, and the action you are asking for. If you are in Semarang or elsewhere in Indonesia, use the support route shown on our site and do not send a full password, wallet PIN or one-time code.

Team online

Account record request

Ask us to locate the account details connected with your phone verification or login history. Include the account identifier and the specific record you want checked; we may ask for a safe confirmation step before releasing private account material.

Wallet receipt query

For a DANA, OVO, GoPay or QRIS receipt, send the reference and approximate transaction date rather than your wallet PIN. We use those details to match the payment status while keeping unrelated account activity outside the request.

Correction or removal

If a profile detail is outdated or you want us to assess removal, state the field and reason clearly. We explain what can change, what must remain for payment or legal records, and which step follows your request.

HANDLING PRACTICES

Inside nau4d Data Handling Choices

The policy is practical: it connects each data category with an account action, a reason for handling and a route for your request.

Account security records

We use login events, phone verification status and selected device signals to identify unusual account access and help with recovery.

Cookies and browser storage

Cookies or similar browser storage can remember session settings and help the lobby load after you move between account pages.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a deposit or withdrawal request with your…

Device behaviour

When you switch from a mobile browser to desktop, we may record session and device signals needed to keep account…

Retention decisions

We keep records only for the period needed for account assistance, payment reconciliation, security checks or legal duties.

Change request path

You can ask for a copy, correction, restriction or deletion assessment through support.

Privacy Policy Answers For nau4d

These Privacy Policy answers address the searches we expect before you open an account or ask us to inspect a record. They cover collection, wallet references, cookies, device signals, retention and request verification, with Indonesia access wording kept clear where local law applies.

It covers account details, phone verification, login events, device signals, browser storage, payment references and support messages. It explains why we handle each category, how long records may remain, and how you can ask for access, correction or a deletion assessment.

DANA and QRIS references help us match a payment status with the correct account request. The same approach applies to OVO, GoPay, bank transfer and virtual account records. We need the reference and status for reconciliation, not your wallet PIN.

Yes, you can ask us to identify the personal records connected with your account. Provide the account identifier, the phone or email detail linked to access, and the categories you want checked. We may complete a confirmation step before sending private material.

Send a correction request through the support path with the account identifier, the field that is wrong and the replacement detail. We check the request before changing it. Payment or legal records may need to remain unchanged, and we explain that outcome.

We may use cookies or similar browser storage for session continuity, settings and account-page loading. You can manage these controls in your browser. Clearing them can sign you out or require another phone verification step when you return.

Retention depends on the purpose: account assistance, payment reconciliation, security checks and legal duties can each require a different period. Our Privacy Policy does not promise one universal timeframe. You can ask support which category applies to a specific record.

You can request deletion or ask us to assess whether a record can be removed. We first verify the account request, then check whether payment reconciliation, security or legal duties require continued retention. Access or eligibility depends on local law.