Reference

Legal terms for your naga368 account

naga368 Legal sets out how account access, identity checks, wallet records and policy requests work for you in Indonesia.

Indonesia access rulesPhone verificationPolicy contact pathWallet record clarity
naga368 Legal terms for your naga368 account
LEGAL HELP ROUTES

Get a clear answer on policy questions

A direct support route helps when a Legal question concerns your account name, phone verification, wallet record or access status. We ask you to contact us from the account area where possible, because that lets us connect your request with the correct account details. Include the relevant payment rail, such as QRIS or DANA, only when your question concerns a transaction. We do not ask you to post private account details publicly. Where local law permits, our support team can explain the applicable policy path without changing the published terms for one individual account.

Team online

Account contact

Use the contact route inside your account for a Legal question about access, phone verification or a correction request. Sending the request from your logged-in account helps us match the matter to the right record and reduces back-and-forth about which account needs attention.

Wallet status

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment reference and receipt details through the account support path. We can then check whether the record is pending, matched or needs clarification.

Access clarification

For an access question, tell us your location and the step where the account path stopped. We can point you to the relevant Legal wording and explain what information is needed, while eligibility remains dependent on local law and the applicable regional rules.

DATA AND POLICY CARE

How we handle your legal requests

Legal care is practical: we separate account identity details from the payment reference needed to investigate a wallet question, and we limit access to records to the people handling that request.

Data handling

We use account details to provide access, verify the account path and respond to Legal requests. When a wallet question names QRIS or bank transfer, we use the transaction reference needed for checking rather than requesting unrelated personal details.

Cookie choices

Cookies can keep the sign-in path working and help the account area remember necessary settings on your browser. You can review cookie controls in your device or browser settings, although disabling required cookies may affect account access steps.

Account security

Phone verification is part of our account access checks. Keep your phone number current and do not share access codes with another person. If a sign-in detail looks unfamiliar, use the account contact route so we can direct the security request correctly.

Record retention

We retain account, support and transaction records for the period needed for their stated purpose and applicable legal duties. When you ask about retention, tell us which record you mean, such as a QRIS receipt or a phone verification entry.

Correction requests

You can ask us to correct an inaccurate account detail through the logged-in contact path. Describe the field that needs changing and provide the replacement detail. We may verify ownership first so a change does not move an account into another person’s control.

Policy changes

If a Legal term changes, we will present the revised wording through the relevant policy area. Check the date and scope of the change before continuing. Questions about an updated clause can be sent from your account so our reply matches the correct policy version.

Questions about naga368 Legal

These Legal answers cover the points you are most likely to check before opening an account: local access, identity details, payment records, cookies, corrections and contact steps. Read the relevant answer first, then use the account support path if your situation needs a record-specific response. Access remains subject to local law.

naga368 Legal covers account access, eligibility wording, phone verification, data handling, cookies, payment records, correction requests and policy changes. It also explains how to contact us about a specific account matter. Access depends on local law, and the terms apply where local law permits.

Access for you depends on local law and where local law permits. Before opening an account, check the applicable regional rules and make sure your details are accurate. We may require phone verification before account access, and a policy question can be sent through the account contact path.

Phone verification helps connect the account path to the person requesting access and supports security checks when account details need attention. Keep your number current and protect the code. If verification stops you from entering the account area, contact us through the available support route.

We may use a DANA or QRIS reference, receipt detail and account record to investigate a payment-status question. Send only the relevant information through the account contact path. The record is handled for the stated support or account purpose and retained according to applicable obligations.

Yes, you can ask for a correction through the logged-in contact path. Name the account field that is inaccurate and provide the replacement detail. We may first verify account ownership, because a Legal data change must not redirect access or wallet records to another person.

Cookies can support sign-in continuity and necessary account functions on your browser or mobile device. You can manage them in your browser settings, but disabling required cookies may interrupt the access path. For a cookie-specific Legal question, contact us from the account area.

Check the current policy wording and its displayed date, then send your question through the account contact route. Mention the clause or access step that concerns you. We can explain the published wording, while any eligibility decision continues to depend on local law.