Reference

nagaempayer Privacy Policy For Your Account

nagaempayer Privacy Policy explains how we collect, use and protect the details connected with your account, including login records and DANA, OVO, GoPay or QRIS payment status.

Account dataWallet recordsCookie choicesPrivacy requests
nagaempayer nagaempayer Privacy Policy For Your Account
PRIVACY HELP

Where To Ask About Your Data

A clear contact route helps when you want to ask what we hold, why a record appears or how to correct an account detail.

Policy request Use the privacy contact route to ask for access to personal data linked with your nagaempayer account. We may ask for an account step, such as phone verification, before releasing details so a third party cannot receive your login or wallet history.
Correction request If your phone number, account name or payment reference needs correction, tell us which field is inaccurate and why. We compare the request with the account record and may check the related DANA, OVO, GoPay or QRIS entry.
Security concern If you notice an unfamiliar login, device session or cashier reference, contact support through the account help path and change your password from the account settings area. Share the time and device type, not your password or wallet PIN.
HANDLING DETAILS

How nagaempayer Handles Privacy Choices

Privacy controls work best when they match the way you actually use your account. We separate account verification, payment reconciliation and technical security records, then keep access limited to the people and…

Account verification

Before we discuss account data, we may use the phone verification step already linked to your account. This helps confirm that the request comes from you rather than someone who only knows a username or has seen a payment receipt.

Payment references

We retain the transaction reference, amount status and selected rail needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet PIN or full banking password to check a receipt.

Cookies and sessions

Cookies and session signals help keep your signed-in path stable and protect pages from suspicious activity. You can manage browser cookie settings, although removing necessary cookies may interrupt account access or require you to verify the device again.

Device security

When you move from phone login to the lobby, we may record device type, browser details, approximate network data and session time. These signals help us identify unusual access without treating your device as permission to read unrelated files.

Retention decisions

We keep records only for the period needed for account support, payment reconciliation, security checks and applicable legal duties. When a record is no longer needed, our processes remove it, restrict it or separate it from active account use.

Change requests

To request a copy, correction or deletion review, contact us through the privacy route and describe the account record involved. We assess the request against security and legal needs, then explain any part that must remain for a defined purpose.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we hear most often before an account is opened. They cover the records created during phone verification, wallet status checks, mobile sessions and support requests, while keeping the focus on what you can ask us and how we confirm the right account owner.

It covers account details, phone verification, login and device records, cookie use, support messages and payment references. DANA, OVO, GoPay, QRIS, bank transfer and virtual account statuses may be stored to reconcile activity and protect your account.

We use your phone number for account identification and the verification step before access or a privacy request is completed. It also helps us distinguish your account from another person when a wallet receipt or login concern is discussed.

Yes. Send a request through the privacy contact path and identify the account email or phone number involved. We may ask you to complete phone verification before sharing data, and we explain any record that cannot be released for security or legal reasons.

We use payment references and status results to match your account activity with a receipt or cashier event. We do not need a wallet PIN. If you ask about a missing status, provide the reference and approximate time rather than private wallet credentials.

Yes. When you sign in from a phone, we may record device type, browser session, login time and related security signals. We do not use this access to read unrelated files, contacts or private content stored on your device.

Contact support through the privacy route and name the field that needs correction, such as a phone number or account detail. We compare the request with the account record and may confirm ownership before changing information connected with payment history.

You can request a deletion review through the privacy contact path. We assess each record against account support, payment reconciliation, security and applicable legal duties. If some data must remain, we explain the purpose and restrict it where our process allows.