Reference

Privacy Policy for your naga11 account

Our Privacy Policy explains how we collect, use and protect the details connected with your naga11 account.

Clear data purposesWallet record contextCookie choicesAccount request path
naga11 Privacy Policy for your naga11 account
CONTACT ROUTES

Privacy Policy help beside account support

A direct support route helps when you have a question about the Privacy Policy or cannot identify a record in your account. We ask you to use the account support path first, include the phone number linked to your profile, and describe the request without sending a password or wallet PIN. Our team can then match the question to the relevant account step, payment reference or cookie setting. If access is unavailable, use the contact route shown on the naga11 site and keep your message focused on privacy.

Team online

Account help

Use the account support path when you need to ask about phone verification, a login record or personal details connected with your profile. Include the relevant account identifier, but never include your password, one-time code or DANA, OVO, GoPay or QRIS security PIN.

Wallet records

For a question about a wallet or transfer reference, tell us whether the record relates to DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use that context to locate the right transaction detail without asking you to disclose private wallet credentials.

Policy requests

Send requests about access, correction or removal through the contact route listed with our support service. We may ask for an account check before releasing personal data or changing it, because confirming the requester protects your profile from an unauthorised change.

DATA PRACTICES

What we do with your account data

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Data collected

We may handle details you provide during account opening, including contact information and phone verification data. We can also receive account activity such as login events, device details and selected payment references. The Privacy Policy explains the purpose connected with each category.

Cookie controls

Cookies help the site remember browser settings and keep parts of your session working. You can inspect cookie controls in your browser and ask support how a setting affects the site. Removing cookies may require you to repeat login or phone verification on that device.

Account security

We use account checks such as phone verification and review of unusual login signals to reduce the chance of another person entering your profile. Keep your password and one-time codes private, and contact support quickly if a device or login event does not look familiar.

Wallet references

Payment records can show a method or reference connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those references for account and status questions; we do not need your wallet PIN to handle a Privacy Policy request.

Retention choices

We retain personal data for the period needed for the stated account purpose, security checks, support history or applicable legal duties. When you ask why a record remains, we can explain its category and the request path available under the current Privacy Policy.

Change requests

You can contact us to ask for correction, access or another permitted change to information held for your account. Give enough detail for us to find the record, complete the identity check we request, and tell us how you want the response delivered.

Privacy Policy answers for naga11 accounts

These Privacy Policy answers focus on the questions you are most likely to have before opening or using an account. They explain the practical link between your account, device, cookies and Indonesian wallet records. If your situation is not covered, use the support route and refer to the specific detail you want us to check. Account access remains where local law permits.

The naga11 Privacy Policy covers personal details used for account opening, phone verification, login and support. It also explains device signals, cookies, payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, plus retention and requests to access or correct data.

Phone verification helps connect an account with the person requesting access and supports security checks when a login looks unusual. We use the related phone detail for the stated account purpose described in the Privacy Policy. Never send your one-time code to support or anyone else.

Yes. The Privacy Policy covers payment references associated with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. These references help us answer account or status questions. They do not require us to receive your wallet PIN or banking password.

Cookies can remember browser preferences and support parts of your session on mobile or desktop. Your browser provides controls for reviewing or removing them. After removal, you may need to sign in again or repeat phone verification. The Privacy Policy explains why each cookie category is used.

You can contact us through the policy request route to ask about access or correction. State the account detail you want checked and complete the identity step we request. We may limit a response where another person's privacy, account security or local law requires it.

Retention depends on the purpose of the record, such as account support, security checks, payment reference handling or a legal duty. The Privacy Policy does not treat every record alike. Ask us about a specific category and we can explain why it remains and what request path applies.

Account access depends on local law and the account checks required for your profile. Where local law permits, you can use the normal login and phone verification path. If access fails or a device signal is unfamiliar, contact support without sharing your password or security code.