Reference

nagapetir Privacy Policy for Indonesia Accounts

Our nagapetir Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, or connect DANA, OVO, GoPay and QRIS.

Clear collection purposesWallet data boundariesDirect privacy requests

Explore Our Lobby Read FAQ

How Wallet Data Is Used Here

nagapetir Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect only the account and transaction details needed to operate your requested access and keep a useful record of privacy actions. During registration, we may receive your name, phone number, verification result and login details. When you select DANA, OVO, GoPay or QRIS, we process

1
payment references, status responses and receipt details rather than treating your wallet password as our account data. Bank transfer and virtual account references may also appear in transaction records. Your mobile browser can provide device, session and diagnostic data so we can keep sign-in working and
2
identify unusual access. Where local law permits, we retain records for the period needed for account support, dispute handling, security checks and legal duties. Eligibility and access depends on local law. This Privacy Policy applies to data handled through nagapetir pages and the account paths connected
3
to them.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP ROUTE

Get Privacy Help Near Account Access

A clear request path matters when your account record or wallet reference needs attention.

Account data request Ask through account help for a copy, correction or explanation of personal data connected with your nagapetir profile. Include your registered phone number so we can match the request.

Wallet record question For DANA, OVO, GoPay or QRIS records, provide the receipt reference and date. We can check the status trail while keeping wallet PINs and passwords outside the request.

Access concern If a mobile sign-in or account verification detail looks wrong, use the account support path before sharing anything further. We may ask for identity details already attached to your profile.

DATA HANDLING PRACTICE

Your Data Path From Login Onward

We handle privacy as part of the account path, from phone verification through wallet status and later support.

Account details

We use your phone number, verification result and account identifiers to create access, confirm requests and connect you with the right account record. We do not need your wallet PIN for these steps.

Cookies and sessions

Cookies and similar browser storage can remember a login session, preserve page settings and help diagnose repeated sign-in failures. You can manage browser storage through your device settings.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may produce reference numbers and status records. We use them to reconcile your request, not to collect wallet passwords.

Account protection

Phone verification before account access helps connect a request with the correct profile. Keep your sign-in details private, and contact account help if a session or verification event seems unfamiliar.

Retention period

We keep account, payment and support records only as long as needed for the stated purpose, account disputes, security checks or legal duties. The applicable period can depend on local law.

Change request

To request correction, access or deletion where local law permits, send the account phone number, requested action and relevant record date through account help. We may verify ownership first.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account, wallet and device questions we hear most often. They are written for your nagapetir access path, including mobile sign-in, phone verification and local payment references. If a request depends on a specific legal right, eligibility or retention rule, the outcome depends on local law.

It covers personal data handled through account creation, phone verification, mobile browser sessions, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

No. We may receive a payment reference and status response for DANA or OVO, but your wallet password and PIN should remain with the wallet provider. Never include them in an account request.

A mobile browser can provide session, device and diagnostic details that help maintain sign-in, remember necessary settings and identify unusual access. Browser storage can be managed through your device settings.

Use the account help path and provide the phone number linked to your profile, the request you want handled and any relevant date. We may verify account ownership before releasing or changing records.

You can request correction or deletion where local law permits. We assess the request against account support, dispute, security and legal retention needs, then explain which records can be changed.

Retention depends on the purpose of the record, including reconciliation, support, dispute handling and legal duties. The applicable period depends on local law and the type of account or payment reference.

Start with account help and include your registered phone number plus a clear description of the data concern. For QRIS or bank transfer questions, add the receipt reference without sharing passwords.

nagapetir Privacy Policy for Indonesia Accounts

Get Privacy Help Near Account Access

Your Data Path From Login Onward

Account details

Cookies and sessions

Payment references

Account protection

Retention period

Change request

Privacy Policy Questions From Indonesia

01 What does the nagapetir Privacy Policy cover?

02 Does nagapetir store my DANA or OVO password?

03 Why does the Privacy Policy mention my device?

04 How can I request my nagapetir account data?

05 Can I ask for correction or deletion under this Privacy Policy?

06 How long does nagapetir retain payment records?

07 Where can I ask a Privacy Policy question?

Related Pages