Reference

Open nagahoki303 Privacy Policy Details

nagahoki303 Privacy Policy explains what we collect when you create an account, sign in on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessYour data requests
nagahoki303 Open nagahoki303 Privacy Policy Details
HELP PATHS

Contact Us About Privacy Policy Questions

A clear support route matters when you want to ask about personal data rather than a wallet status. From your account, use the support path beside the cashier area and include the email or phone detail connected with your account. We can then locate the relevant record, explain the request process and direct payment questions without asking you to send a wallet password.

Team online

Account access

If phone verification or a mobile login leaves you unable to reach your account, use the account support path. We will ask for account details needed to check access without requesting your DANA or OVO password.

Wallet status

For a QRIS, GoPay or bank transfer status question, include the transaction reference shown in your account. This helps us separate payment records from unrelated profile data during a privacy request.

Data requests

To ask for a copy, correction or deletion review, contact support from the account linked to you. We may verify ownership before discussing personal data, including records created on a mobile device.

ACCOUNT SAFEGUARDS

See How nagahoki303 Handles Your Data

We handle privacy through practical account controls rather than vague promises. Login events, phone verification and payment references help us protect the account while keeping wallet credentials outside our support requests.

Data collection

We collect details needed to create and operate your account, verify the phone connected to it, record login activity and match DANA, QRIS or bank transfer references to the correct account.

Cookies and devices

Cookies and device signals can remember a session, identify unusual login behaviour and keep the mobile path consistent from sign-in to the lobby. You can ask support how these records relate to your account.

Account security

Phone verification and sign-in checks help us confirm account ownership before discussing personal data. We do not ask you to disclose a wallet PIN, password or one-time security code in support messages.

Retention period

We retain account, security and transaction records only for the period needed for account operations, dispute handling, legal duties and record accuracy. Ask support which category applies to your request.

Correction requests

If your contact detail or account record is wrong, send a correction request through the verified account route. Include the inaccurate field and the replacement detail so we can assess it precisely.

Deletion requests

You may ask how to remove eligible personal data from your account record. Some transaction or security records may need to remain for legal or operational reasons, which we will explain.

Find Privacy Policy Answers Before Access

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. Each response stays focused on data, account access, payment references and the steps available when you need clarification or a change.

It covers account details, phone verification, login and device records, cookies, lobby activity, payment references and your options to ask for access, correction or deletion where applicable.

Yes. The policy covers status and reference details connected with DANA, OVO, GoPay and QRIS. We use these records to match a transaction to your account, not to request wallet passwords.

Phone verification helps confirm account ownership before access or a data request is handled. It also helps us investigate unusual sign-in activity without asking you to share private wallet credentials.

Use the support path inside the account linked to you and state that you want a data request. We may confirm ownership first, then explain which records can be provided and in what form.

Yes. Send the correction through the verified account route and identify the field that needs changing. We will assess the request against account records, payment references and applicable retention duties.

Cookies can keep a session active and help recognise a device during the path from login to the lobby. You can contact support for details about cookie use and its connection to your account.

Yes. Account access, data handling and any request outcome depend on local law. Where local law permits, we explain your available choices and any records we must retain.