LEGAL REFERENCE

Legal terms before you join

api naga puts your legal terms in front of the account flow so you can see what applies before you join for supported Indonesia regions. Open your account...

Terms scopePolicy contactsIndonesia accessAcceptance steps
api naga Legal terms before you join

Our legal posture for Indonesia

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

SUPPORT

Contact paths for policy questions

Legal questions deserve a direct route, not a generic queue. Use the contact path that matches your issue, include the page name...

Policy email Send us the clause, screenshot, or date you...
Chat handoff If a policy question appears while you are...
Document request Need the current terms, privacy text, or promo...
EDITORIAL CLARITY

How we check policy text

We write legal pages so you can understand the account relationship before you continue. Our checks focus on scope, acceptance, contacts, and regional wording. When wording changes, we...

Version control

Each policy page is tracked by date and purpose, so a changed clause can be matched to the page where...

Plain language pass

We reduce legal clutter where we can without removing important obligations. If a term affects your account, acceptance, records, or...

Regional wording

Indonesia access is described with supported-region wording and legal caveats where local law permits. This keeps availability language separate from...

Clause ownership

Policy sections are assigned internally before publication, so wording about accounts, promotions, records, and dispute steps has an owner who...

Change checks

Before a policy update goes live, we compare related pages for mismatched dates, conflicting contact paths, and duplicated wording that...

Accessible records

We keep key legal pages reachable from the account flow, footer, and support path. That way you can return to...

Consistency across policy pages

Our legal pages work together, so one page should not silently change the meaning of another. We check the terms, privacy text, promo rules, and contact wording as...

Terms page
The main terms explain account acceptance, eligibility where local law permits, service access, and dispute routing. Other policy pages should support those terms rather than create separate account promises.
Privacy page
Privacy wording covers how account and contact data may be handled. It stays aligned with the legal page so you can see when a request involves identity, records, or communication details.
Promo rules
Promotion wording has to match the wider account terms. If a reward rule includes timing, eligibility, or withdrawal conditions, we keep those details tied to the specific promo text.
Cookie text
Cookie wording explains site storage and preference signals. We align it with privacy and legal pages so tracking language does not drift into account obligations it was not meant to create.
Payment context
References to DANA, OVO, GoPay, and QRIS may support account context, but they do not override legal terms. Acceptance, records, and dispute wording remain controlled by the policy pages.
Support language
Contact pages should use the same policy labels you see here. That keeps your question tied to the correct clause and reduces confusion when you ask about account or promo wording.
Regional access
Where access depends on supported regions, we keep that wording consistent across legal pages. This prevents one page from sounding broader than the account terms actually allow.

Legal page signals you can see

This page is designed to show the legal signals that matter before you open an account. Look for dates, scope labels, contact routes, and regional wording...

Clear scope label

The page title and opening copy state that this is legal content, so you know the wording affects account terms, access, policy contacts, and acceptance rather than general lobby promotion.

Date awareness

Legal pages are easier to understand when you can tell whether the wording is current. We keep update context close to policy content so you can ask about the correct version.

Acceptance cues

When a clause affects joining or continued account use, the wording stays near the account flow. You should not have to hunt for the terms you are asked to accept.

Regional caveats

Indonesia access is framed with supported-region wording and where local law permits. This keeps the legal page honest about availability without turning the section into broad promotional copy.

Contact placement

Legal contact routes appear near policy content so you can raise questions about wording, dates, or clause scope. The goal is a cleaner record of what you asked and why.

Context chips

Short chips such as DANA, OVO, GoPay, and QRIS may appear as account context only. They help you connect policy language with the environment where terms are accepted.

Questions about our legal terms

You accept the relevant terms when the account flow asks you to continue after seeing the linked legal pages. If a later feature has separate rules, those rules apply to that feature.

Access may depend on supported regions and where local law permits. If the account flow is unavailable in your area, that does not create a right to access the service elsewhere.

Yes, policy wording may change when services, rules, or legal requirements change. We aim to keep the current version reachable so you can see which wording applies at the time.

Those names may appear as account context for supported regions, but they do not replace the legal terms. The policy wording governs acceptance, records, disputes, and any related account obligations.

A specific promo rule may control the narrow promotion it describes, while the broader account terms still apply around it. Keep the promo wording available if you ask us for clarification.

Yes. Contact us with the page name and the clause you need. We can direct you to the current wording and help identify whether a dated version is relevant.