> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/13.-disclaimer/13.1-legal-disclaimer.md).

# 13.1 Legal Disclaimer

This white paper is not an offer to sell or solicit the purchase of securities, nor is it an investment solicitation or contractual proposal in any jurisdiction.

GET is not classified as a "securities" or "investment product" under applicable laws, and ownership does not confer rights equivalent to shares or equity interests.

As cryptocurrency regulations vary across jurisdictions, the acquisition and use of GET may be restricted in certain countries or regions.

Users are responsible for checking and complying with the laws and regulations of their respective jurisdictions.\
This project is not authorized or approved by any governmental or financial authority, and future regulatory changes may affect GET’s legal status.

This document does not provide legal, investment, or tax advice. Users are advised to consult qualified professionals when making related decisions.


---

# 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://docs.global-entertainment-token.org/13.-disclaimer/13.1-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.
