> For the complete documentation index, see [llms.txt](https://docs.onside.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onside.io/console/account-and-platform/onside-legal-documents.md).

# Onside Legal Documents

Access Onside’s legal documents: Terms of Use, Privacy Policy, Developer Agreement, Data Processing, and compliance policies—latest versions and change history.

To use the Onside Developer Console and publish apps on the Onside Store, you must agree to our legal terms. We recommend you review these documents carefully.

### Key Documents

* **Free Apps Agreement:**
  * These specific terms govern your access to and use of the Onside Developer Console, including your responsibilities, content management, and other critical aspects of publishing. You accept these during the final step of the Developer Console registration process.
* **General Onside Terms of Use:**
  * These are the overall terms that apply to the use of all Onside services, including the Onside Store by end-users and general platform usage.
  * You can access the full document here: [Onside Terms of Use](https://onside.io/terms-of-use)
* **Onside Privacy Policy:**
  * This document details how Onside collects, uses, shares, and protects your personal information and the data of your users.
  * You can access the full document here: [Onside Privacy Policy](https://onside.io/privacy-policy)

***

It is important that you understand these terms. If you have any questions regarding these documents, please feel free to contact our support team.


---

# 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.onside.io/console/account-and-platform/onside-legal-documents.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.