> For the complete documentation index, see [llms.txt](https://docs.solcis.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solcis.ai/legal-centre/acceptable-use-policy.md).

# Acceptable use policy

Permitted and prohibited uses of Solcis.

## Purpose

This policy sets out how the Solcis software may and may not be used. It applies to everyone who uses Solcis and forms part of the Software Licence and Terms.

## Prohibited uses

You must not use Solcis to:

* break any applicable law or regulation, or infringe anyone's rights;
* remove, disable, or circumvent Solcis licensing, entitlement, metering, or integrity mechanisms, or self-issue a licence;
* reverse engineer the Software beyond what applicable law allows, or build or assist a competing product;
* interfere with the integrity, security, or intended operation of the Software or its evidence;
* process personal data without a lawful basis, or conduct unlawful profiling or tracking;
* rely solely on the Software's automated judgement for decisions that are high-risk to a person's rights, safety, or wellbeing, without the human oversight required by applicable law;
* introduce malware or other harmful code; or
* use the Software in breach of export control or sanctions laws.

## Consequences

Breach of this policy may lead to suspension or termination of your licence under the Software Licence and Terms, in addition to any other remedy.

## Contact

Report suspected misuse to <legal@solcis.ai>.


---

# 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.solcis.ai/legal-centre/acceptable-use-policy.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.