> For the complete documentation index, see [llms.txt](https://nexon-3.gitbook.io/nexon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexon-3.gitbook.io/nexon-docs/part-vi-assurance/08-compliance.md).

# Compliance & Legal Posture

Operational separation, disclosure discipline, responsible-party mapping, and the jurisdiction gates for current and long-term products.

NEXON is the first flagship project on the NEX exchange. XO and EXON are NEXON project assets. **A similar name, an integration or an account connection cannot be used to imply authorship, approval, liability or principal protection that no document supports.**

## Operational separation today

The NEX exchange is the compliant spot layer for XO and EXON spot activity and the daily EXON release display. The Staking Platform separately applies XO staking, term bonuses, referral rewards, leadership bonuses and reward withdrawal. **Exchange licences, controls or disclosures cannot be used to imply regulatory approval of a staking return.**

Every long-term product needs its own responsible-party analysis:

| Product                  | Where responsibility lands                                              |
| ------------------------ | ----------------------------------------------------------------------- |
| PayFi orchestration      | Orchestration does not itself provide each underlying regulated service |
| Wallet custody           | Depends on the custody model actually implemented                       |
| Prediction-market access | Depends on the independent protocol and the user's jurisdiction         |
| Marketplace              | Suppliers are responsible for goods and services                        |
| Stablecoin Card          | Depends on an eligible licensed issuer/operator                         |

## Four classes of statement, four ways to write them

This is the **format discipline** this paper applies to all external copy:

| Class                            | How it must be written                                                                                                             |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Confirmed current parameter**  | State the value, source, effective version, and whether it is adjustable                                                           |
| **Calculation with assumptions** | Write the price and execution assumption into the sentence itself ("At 2.0 U, monthly ROI is 54.79%"), with no separate disclaimer |
| **Long-term direction**          | Label it as direction, and name the specifications, operators and eligibility still required                                       |
| **Open field**                   | Keep it visibly Open; never complete it from a conflicting document                                                                |

Market outcomes form their own class: never written as guarantees, and never given a separate disclaimer — the assumption goes into the sentence, and the sentence stops there.

## Product and jurisdiction gates

KYC, AML, sanctions screening, custody, exchange execution, payment, card issuance, financial promotion, data processing and any regulated real-world activity follow the applicable terms of the responsible party. Availability can depend on residence, citizenship, account status, product classification, merchant category and local law.

**Before a route is approved, the user should know six things**: which entity executes each leg, which terms apply, what data is shared, how costs are calculated, whether the action is reversible, and which dispute path controls. One general ecosystem statement does not replace product-specific disclosure.

## Token-language discipline

XO's Value Anchor role establishes no equity, debt, deposit status, current voting right or income guarantee. EXON's Circulation Engine role does not make it a current universal payment or fee token. **Future rights and utilities require published product terms and jurisdictional review.**

Likewise, "fixed supply," "programmatic purchase" and "burn" cannot be written as price assurance. The 0.3% – 1.0% per-settlement yield and the worked examples are mechanism parameters and arithmetic, never written as a promised return.

## Data and AI

AI-Native PayFi and social features may process financial intent, identity references, transaction context and communications. Product design has to define lawful basis, data minimization, retention, deletion, cross-border transfer, provider access and user rights. **Model output is treated as assistance, not as legal, tax or investment advice.**

*Previous:* [*Security & Risk*](/nexon-docs/part-vi-assurance/07-security-and-risk.md) *· Next:* [*Roadmap*](/nexon-docs/part-vi-assurance/09-roadmap.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nexon-3.gitbook.io/nexon-docs/part-vi-assurance/08-compliance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.