> For the complete documentation index, see [llms.txt](https://onza.gitbook.io/onza/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onza.gitbook.io/onza/onzaplus/legal-disclaimer.md).

# Legal Disclaimer

### ⚖️ Legal Disclaimer — ONZA+ <a href="#legal-disclaimer-onza" id="legal-disclaimer-onza"></a>

The information provided regarding **ONZA+** is for **informational purposes only** and does not constitute an offer, solicitation, recommendation, endorsement, or invitation to purchase, sell, or subscribe to any securities, financial instruments, digital assets, investment products, or financial services in any jurisdiction.

ONZA+ is a **technology license providing access to AI-powered automation infrastructure** operating within digital market environments. It is **not an investment product, financial service, or capital guarantee**.

The information presented may include **illustrative examples, forward-looking statements, projections, estimates, targets, or expectations**. Such statements are inherently subject to business, economic, technological, and market uncertainties. Actual outcomes may differ materially from those described.

No representation or warranty, express or implied, is made by **ONZA+, its affiliates, directors, officers, representatives, or partners** regarding the accuracy, completeness, or reliability of the information provided. Users should not rely solely on this information when making financial, technological, or commercial decisions.

Nothing contained within the ONZA+ documentation, platform, or materials constitutes:

• Financial advice • Investment advice • Legal advice • Tax advice • Portfolio management services • Brokerage services

Users are responsible for conducting their **own independent research and due diligence** and should consult qualified professional advisers before making any financial or commercial decisions.

Participation in digital technology ecosystems, automation systems, or digital asset environments involves **inherent risks**, including but not limited to:

• Market volatility • Technological or infrastructure risks • Regulatory changes • Operational uncertainties • Potential financial loss

Any references to past performance, historical data, simulations, or scenario examples are provided for **illustrative purposes only** and do **not guarantee future results**.

This material may contain **proprietary and confidential information** belonging to ONZA+. Unauthorized reproduction, distribution, disclosure, or dissemination of this material, in whole or in part, is strictly prohibited without prior written consent.

This information is **not intended for distribution or use in jurisdictions where such distribution would be restricted or unlawful** under applicable laws or regulations. Each user is responsible for ensuring compliance with the laws and regulatory requirements of their jurisdiction.

By accessing, reviewing, or using ONZA+ materials or services, the user acknowledges that they have **read, understood, and agreed to the terms of this Legal Disclaimer**.

© ONZA+ — All Rights Reserved


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://onza.gitbook.io/onza/onzaplus/legal-disclaimer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.