Reference

Open naga15 --login with clear Legal terms

naga15 --login puts account terms, access conditions and data choices in one Legal page, so you can check the rules before opening an account.

Account termsData choicesLocal access
naga15 --login Open naga15 --login with clear Legal terms
LEGAL HELP ROUTES

Ask about Legal access and account records

A clear support path helps when a Legal question affects your account, identity check or payment record.

Account access Use the account support route when phone verification blocks entry or your Legal access…
Payment record For a DANA, OVO, GoPay or QRIS query, send the payment reference and approximate…
Policy request If you want a copy, correction or clarification of a Legal record, state the…
DATA AND ACCOUNT CARE

Protect your Legal choices across devices

We treat policy work as an account operation, not a vague promise. Our process covers the details needed for phone verification, payment reconciliation and access decisions, while giving you a route to…

Data collection

We collect account details needed to create access, complete phone verification and check payment references. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be linked to a transaction, while unrelated details are not needed for that check.

Cookie choices

Cookies can help keep an account session active and remember settings between the mobile browser and desktop path. Your browser controls can remove or restrict them; some account functions may then require another login or may not retain the selected setting.

Account security

Phone verification is required before account access, and we do not ask for your password through a policy request. Keep your login details private, sign out on shared devices and contact support if an unfamiliar access event appears.

Record retention

We keep account, payment and support records for the period needed to operate the account, address disputes and meet applicable legal duties. If you ask how a record is retained, include its date or reference so we can locate the relevant entry.

Change requests

You can ask us to correct an inaccurate account detail or explain the data connected with a payment reference. Submit the request through the account support route and identify the field or record; we may verify ownership before applying any change.

Policy contact

For a Legal question that is not about a specific payment, describe the clause or access condition in your message. We will use the contact detail on your account to respond, and location matters because access depends on local law.

Browse answers about Legal and access

These Legal answers address the questions you may have before creating an account or sending a data request. They cover eligibility, payment records, cookies, phone verification and corrections, so you can choose the next step with the current policy in view. Where the wording does not settle your situation, use the account support route.

Legal covers account access, phone verification, data handling, cookies, payment records and requests to correct or explain stored details. It also sets out location conditions for Indonesia, including the rule that access depends on local law and is available where local law permits.

Access from Indonesia depends on local law. Before opening an account, check the current Legal wording for your location and complete phone verification only where local law permits. If your eligibility is unclear, send a region-specific question through the account support route.

Phone verification helps connect account access to the contact detail supplied at registration and reduces confusion when a login needs checking. We may use that verified detail alongside a DANA, OVO, GoPay or QRIS reference when resolving an account or payment question.

A DANA or QRIS payment reference can be used to locate a transaction, confirm its status and address a support request. We ask you to share the reference rather than a password, and we handle the record under the data and retention terms on this page.

Yes. Send a correction request through the account support route, name the field that is inaccurate and use the contact detail connected with your profile. We may verify account ownership before changing the record, especially when it relates to payment or access.

Cookies can retain a session or selected setting between account visits, including on a mobile browser. You can restrict them through browser controls, but the account may ask you to log in again or may not remember a setting after removal.

Use the support route shown inside your account and describe the clause, access condition or record involved. Include your registered contact detail and any transaction reference, but never send a password. We use the request to direct the question to the relevant policy process.