Reference

nagacuan Privacy Policy for Your Account Data

Your account details, wallet references and device signals are handled under one clear Privacy Policy, so you can understand what we collect before opening an account.

Account dataWallet referencesCookie choicesAccess requests
nagacuan nagacuan Privacy Policy for Your Account Data
CONTACT ROUTE

Privacy Policy Help From the Account Path

A clear contact path helps when a Privacy Policy question concerns your login, wallet status or stored account record. Use the support route shown inside your account and include the email or phone detail linked to your profile. We can then locate the relevant record without asking you to send a wallet PIN or full payment credential.

Team online

Account data request

Ask us to explain the account data connected with your profile. Include your registered contact detail so we can match the request to the correct account before replying.

Wallet status question

If a DANA, OVO, GoPay or QRIS reference looks unclear, send the transaction status shown in your account. We use that reference to investigate without requesting your wallet PIN.

Login privacy help

When a mobile browser keeps a session or blocks a cookie, contact us through the account support route. Tell us your device path and the screen where the Privacy Policy question appears.

DATA PRACTICE

Six Privacy Checks Behind Your Login

We keep this policy practical by tying each data practice to a visible account step. The checks below explain what happens around login, cookies, wallet references and requests to change or remove…

What we collect

We use account details, login events, device signals and transaction references to provide access and investigate account questions. Data collection is limited to the purpose described in this Privacy Policy.

Cookie controls

Cookies can keep a session active and remember selected settings on your browser. You can adjust browser cookie controls, though changing them may affect how the account access page behaves.

Account security

Login checks use account credentials, session activity and device signals to identify unusual access. Keep your contact detail current and do not send passwords or wallet PINs through support.

Retention approach

We retain records only for account operation, security checks, support handling and legal duties that apply to the service. Retention can differ when a local rule requires a longer record period.

Access or changes

You can ask what personal data is linked to your account, request a correction or ask about removal where local law permits. We may verify account ownership before making a change.

Contact ownership

Send privacy questions through the support route shown in your account, using the registered phone or email detail. This helps us discuss your record with the correct account holder.

Privacy Policy Answers For nagacuan Accounts

These Privacy Policy answers focus on the searches we hear around account creation, wallet references, cookies and data requests. If your situation is not covered, open the support route connected to your account and describe the exact screen or payment status you can see.

It covers account details, login activity, device signals, cookies, payment references and support records. It also explains why we use each category and how you can ask about your personal data.

No wallet PIN should be sent through our support route. For DANA and OVO activity, we use the transaction reference and status needed to connect the payment event with your account.

Device and session signals help us identify unusual account access and investigate a login question. A phone browser and a desktop browser may create different session signals during the same account path.

Cookies can remember a session and selected settings, while browser controls let you change cookie behaviour. Blocking them may require another login or affect the way policy choices are displayed.

Yes, you can contact us through the account support route to ask what data is linked to your profile or request a correction. We verify account ownership before discussing or changing records.

We keep records for account operation, security, support and legal duties, then remove or restrict them when the applicable purpose ends. The period can vary because it depends on local law.

Use the support contact shown inside your account and include your registered phone or email detail. For a QRIS or GoPay query, add the visible reference and status, not private wallet credentials.