Reference

naga303 Privacy Policy for Indonesia Accounts

Our naga303 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account recordsWallet referencesDevice and cookie usePrivacy requests
naga303 naga303 Privacy Policy for Indonesia Accounts
PRIVACY CONTACT PATH

Reach Us About Privacy Questions

A clear contact path helps you ask what we hold, why we use it, or how to correct an account detail.

Account support route Open the support path after login and choose a privacy request. Include your registered phone number only through the account form, so we can match the request without exposing private details.
Wallet receipt check For DANA, OVO, GoPay or QRIS questions, attach the payment reference and status shown in your account. We use those details to trace the record without asking for your wallet password.
Access correction request If your phone, device record or account detail is wrong, tell us through the privacy contact path. We may verify ownership before changing information connected with your naga303 account.
DATA HANDLING

Browse Our Account Privacy Steps

We keep this policy practical by linking each data use to an account action you can recognise.

Account creation

When you open an account, we use the details you submit to create your profile and send account-related notices. Phone verification can be required before access to private account pages.

Sign-in security

We review sign-in time, browser and device signals to identify unusual account access. If a session looks different, we may request another account step before showing private wallet or profile details.

Cookie controls

Cookies can remember session settings and help us understand whether a page loads correctly. You can adjust browser cookie controls, though switching them off may affect login and policy-request pages.

Payment references

Our records can contain DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. We use status and reconciliation details for the requested transaction, not unrelated wallet activity.

Retention periods

We keep account, security and payment records only for the period needed for account operations, dispute checks, legal duties or security review. When no reason remains, records move toward deletion or anonymisation.

Change requests

You can ask us to correct eligible account data or explain its use through the privacy contact route. We verify the request first, then reply with the available action and any legal reason for limits.

Ask About naga303 Privacy Policy

These answers address the searches we most often expect before an account is opened. Each response stays focused on the naga303 Privacy Policy, including account access, local wallet references, cookies, correction requests and the conditions that apply where local law permits.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and protect the account, send account notices and complete phone verification. We may verify ownership before discussing private records or changing account details.

Yes. The policy covers QRIS, DANA, OVO and GoPay references connected with your account, including status and reconciliation details. We do not ask for your wallet password through our support route.

Cookies can keep a sign-in session active and help us identify page-loading issues. You can change browser settings, but disabling cookies may prevent account access or make a privacy request harder to submit.

You can contact us through the privacy support path to ask what eligible account data we hold or to request a correction. We verify ownership first and explain any restriction required by local law.

We retain records for account operations, security checks, transaction disputes or legal duties only as long as needed for those purposes. Records may then be deleted or changed into a form that cannot identify you.

Use the support route displayed after login and select the privacy subject. Include your account identifier and the specific request, such as wallet status, cookie use, correction or access, where local law permits.