Reference

Privacy Policy For Your naga123 Account

Our Privacy Policy explains how we collect, use and protect details connected with your naga123 account, including phone verification, device access and wallet records.

Account dataCookie choicesPayment recordsAccess requests
naga123 Privacy Policy For Your naga123 Account
CONTACT DATA HELP

Three Ways To Ask About Privacy

A direct request helps us locate the right account record without asking you to repeat the whole history. When you contact us about this Privacy Policy, include the account phone number or the payment reference you want checked, but do not send a password or wallet PIN. We use the account support route for access questions, correction requests and cookie concerns. If your issue involves a DANA or QRIS receipt, keep the receipt available so we can compare its status with the account record.

Team online

Account request

Use the support path attached to your naga123 account to ask which personal details we hold or to request a correction. We may ask for a phone verification step before discussing account data, so another person cannot obtain details by presenting only a username.

Payment record

For a DANA, OVO, GoPay or QRIS question, provide the relevant receipt reference and approximate transaction date through support. We use those details to find the matching payment record, explain its status and avoid exposing unrelated account activity.

Access concern

If a login or device session looks unfamiliar, contact us through the account help route and describe the device path, such as mobile browser or desktop. We can use that report to check session details and guide the next account-security step.

SIX DATA PRACTICES

What We Do With Your Account Data

Privacy controls work best when each data use has a clear purpose. We separate account identification from payment reconciliation, keep cookie choices tied to the device that made them, and use security…

Collection

We collect details you enter for an account, such as your phone contact, together with records created when you log in, complete phone verification or contact support. We aim to collect only what is needed for account access, payment matching, security checks and a specific request.

Payment handling

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry helps us match a payment event to your account. We retain the reference and status needed for reconciliation, while avoiding requests for your wallet PIN or full banking login details.

Device records

When you open naga123 on a mobile browser or desktop, technical session details can help us recognise a login pattern and investigate an unfamiliar access event. These records support account protection and are not a reason to read unrelated content on your device.

Cookies

Cookies can keep a session working, remember a consent choice and help us understand whether a page request succeeded. You can manage cookie settings in your browser; removing necessary cookies may require you to repeat login or phone verification.

Retention

We keep account, payment and support records only for as long as their purpose requires, unless a legal duty calls for a longer period. When a retention period ends, we delete, anonymise or restrict the record according to its format and operational need.

Your requests

You may ask for a copy, correction, restriction or deletion of eligible personal details where local law permits. Send the request through account support, identify the record clearly and complete any verification needed before we change or disclose private account data.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions we expect you to ask before opening naga123. They cover the data created by phone verification, mobile access, cookies, payment references and support requests. If your situation is not covered, use the account support path and describe the exact record or device involved. Access and eligibility depend on local law, so our response may also explain which local requirement applies to your request.

The Privacy Policy covers account details, phone verification, login and device records, cookies, payment references, support messages and retention. It explains why we use each category, how we protect it and how you can ask about, correct or remove eligible data where local law permits.

Phone verification links an account request to the person controlling the contact number and helps prevent another person from discussing private account data. We may use the same check before changing account details or answering a request about DANA, QRIS or another payment record.

Yes. The Privacy Policy covers the payment reference, status and account link created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account records. We do not ask for your wallet PIN or full banking login details.

On a mobile browser, cookies can keep your session active, remember a cookie choice and show whether a page request completed. You can remove or block them through browser settings, although necessary cookies may be needed to log in or repeat phone verification.

Where local law permits, you can request a copy of eligible personal data through account support. State the account contact and the record you want, such as a login event or QRIS receipt reference. We verify the request before releasing details linked to your account.

You can ask us to correct inaccurate details or delete eligible records through the account support path. Some payment, security or legal records may need to remain for a required period. We will explain the reason if a record cannot be removed immediately.

We keep records for the period needed to operate the account, reconcile a payment, investigate security or answer support, unless a legal duty requires longer retention. After that period, we delete, anonymise or restrict the record according to its format and purpose.