Reference

naga178 Privacy Policy, Clearly Set Out

naga178 Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and return to the lobby from a mobile device.

Account dataWallet recordsCookie choicesAccess requests
naga178 naga178 Privacy Policy, Clearly Set Out
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact path helps when you need an answer about the Privacy Policy, an account record, or a wallet reference.

Account access Use our listed support contact when the phone verification step blocks access or you need to confirm which account details are attached to your profile. We may ask for a limited identity check before discussing personal records, and we will not ask you to disclose your password.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, include the transaction date and reference shown in your account. This lets us match the wallet event while limiting the personal data shared through the support conversation.
Privacy requests Ask through the same listed contact route to access, correct, or question the use of your personal data. Tell us which request you are making and the account email or phone detail, so our team can respond to the right record.
DATA PRACTICES

Inside naga178 Privacy Handling

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

Account details

We handle the name, contact detail, phone verification result, and login records needed to maintain your account. You can ask us to correct inaccurate information through the listed support route, and we may verify the request before making a change.

Cookie controls

Cookies can keep your session available as you move from mobile login to the lobby and help us understand technical performance. Your browser provides controls for cookie storage; changing them may affect sign-in continuity or certain page functions.

Account protection

We use phone verification, session details, and device signals to help protect account access. If a sign-in looks unusual, we may pause a request and ask for an account check before discussing personal data or changing contact details.

Payment matching

A DANA, OVO, GoPay, or QRIS reference helps us connect a wallet event to the correct account. Bank transfer and virtual account records serve the same matching purpose, while payment credentials remain with the relevant payment service.

Retention requests

We retain records only for the operational, dispute, fraud-prevention, or legal reason that applies to them. When you ask about deletion, we explain which records can be removed and which must remain under an applicable requirement.

Policy changes

When we change this Privacy Policy, we update the policy page and identify the revised subject in the published text. Check the page before opening an account or continuing access, which depends on local law and your location.

Privacy Policy Questions naga178 Answers

These Privacy Policy answers focus on the account and wallet questions you are most likely to have before using naga178. They explain the records connected to phone verification, mobile sessions, local payment references, cookies, and requests sent through our listed support contact. Where a legal right or access condition varies by location, it depends on local law.

It covers account details, phone verification, login and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use. It also explains retention, access requests, corrections, deletion limits, and how policy changes are presented.

We use the verification result to confirm account access, help with recovery, and reduce the risk of an unauthorised change to your contact details. We do not need your phone password. A request to discuss account data may require a limited identity check.

Yes. The Privacy Policy covers the payment reference, amount status, date, and account match needed to reconcile DANA or QRIS activity. It can also cover OVO, GoPay, bank transfer, and virtual account references. Payment credentials remain with the relevant payment service.

Use the support contact published on our site and identify the account email or phone detail connected to your request. State that you want access to your personal data under the Privacy Policy. We may verify your identity before supplying records or explaining limits.

You can request a correction when an account detail is inaccurate, and you can ask whether deletion applies to a particular record. Our response depends on the record's purpose, an open payment or account matter, and local law. We explain any retention reason.

Cookies can keep your mobile session connected as you move from login to the lobby and help us measure technical performance. Your browser settings let you remove or restrict them. Some restrictions can interrupt session continuity, so you may need to verify again.

Yes. Send your question through the listed support contact and identify the policy point, account detail, or wallet reference involved. We will route it for a privacy response and explain the applicable process. Access or eligibility for naga178 depends on local law.