Reference

naga1000 Privacy Policy For Your Account

naga1000 Privacy Policy explains how we collect, use and protect the account, device and wallet details you provide when you open an account or enter the lobby.

Account dataWallet detailsDevice choicesPolicy requests
naga1000 naga1000 Privacy Policy For Your Account
HELP WITH REQUESTS

Where To Ask About Privacy Policy

A clear contact route matters when you want to see, correct or question personal data. We ask you to begin from the account help path so we can connect your request to the correct profile without asking you to post private details in a public message. Include the email or phone number attached to your account, the subject of your request and any relevant payment reference. We can then explain the next verification step and keep the request connected to your account record.

Team online

Account access

If phone verification or a login record looks incorrect, contact us through account help and describe the affected device. We use the account details you submit to locate the record, confirm ownership and explain whether a correction is possible.

Wallet status

For a DANA, OVO, GoPay or QRIS reference, send the transaction date, amount and visible status from your account. Do not send a wallet password or full security code. We use the reference to check the related payment record.

Data request

To request a copy, correction or deletion assessment, state the exact data concern and the account contact attached to it. We may verify your identity first, then confirm what we can provide, change or retain under this Privacy Policy.

HANDLING YOUR RECORDS

Inside naga1000 Data And Access Controls

We keep this policy practical by tying each data practice to a visible account action. A phone check supports account access, device records help us investigate unusual sign-ins, and payment references let…

Data collected

We may receive your name, contact details, phone verification result, login events, device information, account activity, support messages and payment references. We collect these categories when they are needed to provide account access, identify a request or investigate a transaction status.

Purpose of use

We use account data to authenticate access, maintain the lobby, respond to support, trace payment references and identify suspicious account activity. We do not need your wallet password to check whether a DANA, OVO, GoPay or QRIS status is recorded.

Cookies and devices

Cookies and device signals can keep your session connected and help us recognise unusual sign-in patterns. You can review browser cookie controls on your device, although changing them may affect login continuity or the way account pages load.

Account security

Phone verification is completed before account access where required by our account flow. Keep your password, verification code and wallet credentials private. If a device no longer belongs to you, contact account help so we can assess the related access record.

Retention periods

We keep records for the period needed to operate your account, resolve a payment question, protect the service or meet applicable legal duties. When a record is no longer needed for those purposes, we assess it for deletion or further restriction.

Changes and contact

You may ask us to correct account details, explain a data use, provide an accessible copy or assess deletion. Include your account contact and request purpose through account help; we may verify ownership before changing or disclosing personal data.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the questions we expect before you open an account or send a data request. They cover the information connected to your login, device, payment reference and support contact, rather than describing unrelated lobby features. If your question is not listed, use account help and include the contact detail attached to your profile. We will tell you what verification is needed and whether local law affects the request.

The naga1000 Privacy Policy covers information connected to your account, including contact details, phone verification, login activity, device signals, support messages and payment references. It explains why we use those records, how long we retain them and how you can ask about access, correction or deletion.

Phone verification helps us connect account access to the contact detail you supplied and investigate disputed sign-ins. We may use the result when you open an account or recover access. Keep verification codes private, and contact account help if the displayed phone detail is wrong.

Yes. The Privacy Policy includes payment references linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account status. These references help us match a transaction question to your account. We do not ask for your wallet password to check a status.

You can ask for an accessible copy of personal data connected to your account through account help. Include your account email or phone number and describe the records you need. We may verify ownership before responding, and the result depends on local law and applicable retention duties.

Send a correction request through account help with the account contact, the field you believe is wrong and the accurate replacement. We may compare the request with your phone verification or account record before changing it. We will explain if a record must remain unchanged.

You may request a deletion assessment through account help. We first verify the account and identify the records involved. Some information may need to remain for security, payment disputes, account history or legal duties, so the outcome depends on local law and the reason for retention.

Where local law permits, we provide policy access through this page and handle data requests through account help. Your eligibility to use the account depends on local law. If you are unsure about a regional restriction, ask support before submitting personal or payment details.