Reference

api naga login Legal access terms

api naga login Legal terms explain how you open, use, secure, and close an account in Indonesia.

Account termsData requestsLocal-law accessWallet records
api naga login api naga login Legal access terms
CONTACT ROUTES

Legal questions on account access

A clear contact path helps when a Legal question concerns login, phone verification, wallet status, or a data request. Start from the support contact shown in your account area and include the email or phone detail linked to your account, the relevant date, and any payment reference. We use those details to locate the correct record without asking you to send a password or security code. If access is restricted, the support team can explain the available next step where local law permits.

Team online

Account access

For a login or phone-verification question, contact us through the support route shown in your account area. Include your registered contact detail and the approximate time of the issue, but never send your password or one-time security code.

Wallet records

If DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity needs checking, provide the payment reference and status shown at the cashier. We can match that reference with the account record without requesting private wallet credentials.

Data requests

For a copy, correction, or removal request, use the same account support contact and identify the exact record involved. We may ask for phone verification before discussing personal data, so the request reaches the correct account holder.

DATA PRACTICE

How we handle Legal data requests

We handle Legal matters through account-linked records rather than informal messages. Login details, phone verification, cashier references, and support requests are separated by purpose so we can check access and resolve a…

Data handling

We use account details to provide access, check phone verification, connect payment references, and respond to Legal requests. We ask only for details relevant to the issue, and we do not need your wallet password to inspect a DANA or QRIS status.

Payment records

A cashier record can show the selected rail, reference, amount status, and account link. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account entries are used to trace a transaction question, not to collect your private wallet login.

Cookies

Cookies can keep a session active, remember basic access choices, and help us identify an interrupted login. You can clear them in your browser settings, although doing so may require phone verification again before account access continues.

Account security

Keep your password private and complete phone verification only through the account access flow. Our support contact will not need your password or one-time code, and a request about personal data may require a check against the registered contact detail.

Record retention

We retain account, cashier, and support records for the period needed to handle disputes, security checks, Legal duties, and account history. If you ask for removal, we explain which records can be deleted and which must remain under applicable rules.

Changes and contact

To correct a name, phone detail, or other account record, contact us through the support path shown after login. State what is wrong and what should replace it; we may verify the request before changing information tied to wallet activity.

Legal answers for api naga login

These Legal answers address the account and data questions that commonly arise before access. We keep the wording practical: what you agree to, how payment records are identified, how cookies affect login, and how to ask for a change. If a matter depends on location or eligibility, the applicable position depends on local law.

The Legal page covers account access, phone verification, payment references, cookies, security, retention, and requests about personal data. It also explains that access and eligibility depend on local law, so the available account path may differ by location.

Phone verification may be required before account access or before we discuss account-linked data. Use the contact detail registered on your account, and never send a password or one-time code to support. The exact access position depends on local law.

DANA and QRIS records can include a payment reference, selected route, status, and account link. We use those details to trace a cashier question or disputed status. We do not need your private wallet password to check the related record.

Yes. Send the request through the support contact shown in your account area, identify the incorrect field, and state the replacement detail. We may verify your registered phone or email before changing information connected with account or wallet records.

Cookies can preserve your session and remember basic access choices. Clearing them through your browser may sign you out or trigger phone verification again. Cookie use does not replace your account security duties, including keeping login details private.

We keep account, cashier, and support records for the period needed for security checks, disputes, Legal duties, and account history. A removal request may not cover every record; we explain the reason when a record must remain.

Use the support contact displayed in your account area and include your registered contact detail, the relevant date, and a clear description of the request. For payment questions, add the DANA, OVO, GoPay, QRIS, or bank reference shown at the cashier.