Reference

nagadewa Privacy Policy For Your Account

nagadewa Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet activity.

Account detailsWallet recordsCookie choicesContact requests
nagadewa nagadewa Privacy Policy For Your Account
HELP WITH YOUR DATA

Three Clear Routes For Privacy Questions

A clear support route helps you act on the Privacy Policy instead of searching through account screens. We can help you identify which details relate to phone verification, a wallet reference or a device session. When your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, include the relevant receipt or status reference without sending a password. You can also ask us to clarify a data request before you send it.

Team online

Account access

If phone verification or a remembered device prevents you from reaching your account, contact our account support route and describe the sign-in step that stops. We use the account details you provide to locate the issue, then explain what information is needed before making a change.

Wallet records

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and the status shown in your account. For bank transfer or virtual account questions, the same route helps us match the record without asking you to disclose your password or private wallet PIN.

Privacy requests

To ask about access, correction or removal of personal details, contact support with your account identifier and the request you want handled. We may ask for a phone verification step so we do not disclose account data to somebody who cannot confirm control of it.

OUR DATA CONTROLS

Six Practical Rules Behind Our Privacy Policy

We apply the Privacy Policy at the points where your account creates useful records: phone verification, wallet status, device sessions and support messages.

Collected details

We may receive your account name, phone number, verification result, sign-in details and messages sent to support. Payment references can identify a DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction, while wallet PINs and passwords should remain private to you.

Purpose of use

We use account and transaction details to provide access, confirm a phone step, show wallet status, investigate a receipt and answer a request about your data. The same records can help us identify an unusual session before we discuss account details with you.

Cookies and devices

Cookies and similar device signals help keep your session connected as you move from login to a mobile lobby or from desktop access to Live Baccarat Table. You can manage browser cookie settings, though changing them may affect sign-in continuity and saved preferences.

Account protection

Phone verification supports account protection, and we do not need your password or wallet PIN to investigate a payment reference. Keep those credentials private, sign out on shared devices and contact us if a session or account detail does not look familiar.

Retention approach

We keep records only for the operational, legal or dispute-handling purpose described in the Privacy Policy, including transaction checks and support history. Retention can differ by record type, so your request should name the account detail or payment reference you want us to assess.

Changing your details

If your phone number, contact detail or account data needs correction, send a specific request through support. We first confirm account control, then explain whether the change can be made directly or whether a transaction or security record must remain for its stated purpose.

Privacy Policy Questions About nagadewa

These Privacy Policy answers cover the account questions you are most likely to have before opening an account or sending a support request. We keep each answer tied to a real data point, such as phone verification, device access or a DANA receipt. If your situation is different, contact us with the smallest useful detail and we will explain the next step.

It covers account details, phone verification, sign-in and device data, cookies, support messages and payment references. That includes records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those records are needed for account access or transaction support.

We use your phone number for account identification and the clear verification step required before account access. It can also help us confirm that a privacy or wallet request comes from the account holder. We do not ask you to provide a password or wallet PIN in support messages.

The policy treats payment details as transaction references and status records rather than public profile content. A QRIS or DANA receipt may be used to check a pending status, while bank transfer and virtual account references can help match an account request to the correct transaction.

Yes. Send a correction request through the support route and identify the account detail that needs attention, such as a phone number or contact record. We may complete a phone verification step first, then explain whether the correction can be made without affecting a required transaction or security record.

Cookies help keep your session connected and remember certain browser settings as you move between login and the lobby. You can adjust cookie controls in your browser. If you block necessary cookies, phone verification, account access or the return to a mobile session may not work as expected.

Retention depends on the type of record and its operational, legal or dispute-handling purpose. Transaction references, verification records and support history may need different periods. Ask us about a named record, such as a GoPay status or account message, and we will explain the applicable handling.

Our Privacy Policy describes the handling used for supported Indonesia access, but access or eligibility depends on local law. Where local law permits, you can contact us about account data, device records or wallet references. We will explain any location-specific restriction that affects your request.