Reference

Open naga101 Privacy Policy Before Access

naga101 Privacy Policy gives you a clear account of how we handle your account details, wallet references and device signals before you open the lobby.

Account dataWallet recordsDevice choicesPolicy requests
naga101 Open naga101 Privacy Policy Before Access
REQUEST ROUTES

Reach Us About Privacy Changes

A privacy question should have a clear route, especially when it concerns a phone check, wallet reference or device record. Use the contact path presented with your naga101 account and include the email or phone detail connected to the request, without sending a password or wallet PIN. We use those account markers to locate the right record and may ask for another account step before changing or disclosing personal data. Access remains subject to local law.

Team online

Access request

Ask us which account, device and payment-status details we hold about you. Include your account phone number so we can match the request, then complete any identity step we require before sending a response.

Correction request

Tell us when your account name, phone detail or wallet reference needs correction. We compare the request with the account record, update eligible fields and keep a trace of the change for account protection.

Deletion question

Contact us when you want to ask about removing personal details. We assess the request against account security, transaction records and legal retention duties, then explain which data can be removed and which must remain.

DATA PRACTICE

Check How We Handle Your Records

Privacy work is part of each account step, from phone verification to a QRIS status check on your mobile browser.

Account details

We collect details such as your phone number, login data and verification result when you create or protect an account. We use them to identify the account, support requested changes and reduce mistaken disclosure during a privacy request.

Wallet references

A DANA, OVO, GoPay or QRIS status can create a reference connected to your account activity. We use that reference to match payment state and account support, while avoiding any request for your wallet PIN.

Device signals

Your phone or computer may send browser type, session data and technical error details when you open the lobby. These signals help us keep account access working and investigate a failed phone check without treating them as your password.

Cookies

We use cookies and related storage to maintain a login session, remember necessary choices and detect unusual account activity. Browser controls can remove or restrict them, but doing so may interrupt the path from phone verification to the lobby.

Retention

We keep personal and transaction-related records only for the period needed for account operation, security, dispute handling or legal duties. The Privacy Policy explains why some records cannot be removed immediately after an account or wallet question.

Policy contact

Send a privacy request through the account contact path and identify the account detail involved. We may ask you to complete a phone verification step before discussing records, which helps prevent another person from receiving your data.

Ask naga101 About Privacy Policy

These Privacy Policy answers address the account questions you are most likely to ask before opening naga101 in Indonesia. They cover the data connected to phone verification, wallet status, cookies, device use, retention and requests to change or remove records. Where access or eligibility is discussed, it depends on local law.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment-status references and contact requests. It explains how we use those records for account access, security, reconciliation and legal duties when you use the service where local law permits.

We use your phone number to create and protect the account, complete a phone verification step and match a privacy request to the correct record. Do not send your password or wallet PIN through a contact request, even when asking about account data.

Yes. The policy includes references created when DANA, OVO, GoPay, QRIS, bank transfer or virtual account status is connected to your account. These references help us reconcile an account action and respond to a payment-status question without collecting your wallet PIN.

Cookies and related storage can keep your session active, remember necessary choices and help detect unusual access. You can restrict them in your browser, but the path from phone verification to the lobby may stop working or require another account step.

Yes. Send a correction request through the account contact path and identify the phone, account name or wallet reference that needs attention. We compare the request with the account record, complete an identity check when needed and update eligible details.

You can ask us to remove personal data through the contact path. We assess the request against account security, transaction reconciliation and legal retention duties. Some records may need to remain for those reasons, and we explain the result of our assessment.

Retention depends on the type of record and the reason we hold it. Account, security and transaction references may remain for account operation, dispute handling or legal duties. The Privacy Policy describes these purposes and the route for asking about a specific record.