Reference

naga100 Privacy Policy for Your Account

naga100 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesAccess requests
naga100 naga100 Privacy Policy for Your Account
PRIVACY CONTACTS

Where To Ask About Personal Data

Privacy questions should reach the support route linked to your account, so we can match the request with the correct phone verification and activity record. Tell us whether you need access, correction, deletion consideration or an explanation of a wallet reference. Do not send a wallet PIN or full password in a message. We may ask for account identifiers before discussing private details, and we handle requests according to the current Privacy Policy and local requirements.

Team online

Account support

Use the account support channel when you want to ask what contact details, phone verification records or login events are connected with your naga100 account. We may request a matching account detail before releasing private information.

Payment records

For a DANA, OVO, GoPay or QRIS reference, send the date, amount reference shown to you and account identifier, while hiding wallet credentials. We use those details to locate the relevant record without asking for your PIN.

Privacy request

Ask through support when you want to correct account data, question a cookie choice or request a retention explanation. We will confirm the scope, check whether local law affects the request and reply through the account contact path.

DATA HANDLING

Six Practical Privacy Controls

We apply the Privacy Policy through ordinary account actions rather than hidden settings. Your phone verification supports account access, device signals help us investigate unusual login activity, and…

Account collection

When you open an account, we collect the details needed for the account path, including contact information and phone verification…

Device signals

A phone or desktop session can create technical records such as device type, browser details and login time.

Cookie choices

Cookies can keep a session active or remember a setting, depending on your browser choices.

Payment references

DANA, OVO, GoPay and QRIS can return a transaction reference or status used to match your cashier activity.

Security checks

Phone verification and account activity checks help us respond when login details or wallet status stalls.

Retention requests

You can ask why a record remains stored, request a correction or ask whether deletion is available.

Privacy Policy Questions About naga100

These Privacy Policy answers focus on the account and payment situations you are most likely to search before opening an account. They cover phone verification, cookies, wallet references, device access and requests to change stored details. If your situation is not listed, contact support from the account path and include only the minimum detail needed to locate your record.

The naga100 Privacy Policy covers account details, phone verification, login activity, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security handling and how to ask for access or correction.

We do not ask you to place a DANA or QRIS password in your naga100 account fields. The Privacy Policy concerns transaction references and status information needed to match a receipt, while your wallet credentials remain handled through the relevant payment service.

Phone verification links an account access request with the contact detail you provide. We use its status to help confirm ownership and investigate login issues. If you ask about that record, support may request a matching account detail before discussing private information.

Yes, you can contact support and request access to, or correction of, the account data covered by the Privacy Policy. State the account identifier and the detail you believe is wrong. We verify ownership, check local requirements and explain the available result.

Cookies may keep your session active or remember a browser preference on a phone or desktop. You can remove them through browser settings. After removal, the account access step may appear again, and the Privacy Policy explains the purposes connected with those cookies.

Payment references help us match a DANA, OVO, GoPay, QRIS, bank transfer or virtual account status with the correct account and support case. We retain them for the operational, security or legal reasons described in the Privacy Policy, not as wallet passwords.

You can ask support whether deletion is available for a particular record. We assess the request under the Privacy Policy and local requirements because some account, security or payment records may need to remain for a stated period. We will explain the decision.