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

# Legal

- [Privacy Policy](https://docs.brewfather.app/legal/privacy-policy.md): How Warpkode AS collects, uses, discloses, retains, and protects personal data in Brewfather, and the choices available to users worldwide.
- [Terms of Service](https://docs.brewfather.app/legal/tos.md): Terms governing use of the Brewfather application, websites, subscriptions, content, integrations, and related services.
- [Mobile App License Notice](https://docs.brewfather.app/legal/eula.md): Mobile application licence notice and app-store terms for the Brewfather iOS and Android applications.
- [API Terms of Service](https://docs.brewfather.app/legal/api-terms-of-service.md): Terms for the Brewfather API, Connected Apps, MCP and AI-agent access, webhooks, device endpoints, credentials, and API Data.
- [Refund Policy](https://docs.brewfather.app/legal/refund-policy.md): Refund, cancellation, renewal, withdrawal, and billing rules for Brewfather subscriptions purchased through Paddle, Apple, or Google.
- [Affiliate Terms](https://docs.brewfather.app/legal/affiliate-terms.md): Terms governing participation in the Brewfather Affiliate and Partner Programme, including attribution, commissions, promotion, disclosure, and enforcement.
- [3rd Party Licenses](https://docs.brewfather.app/legal/3rd-party-licenses.md): Third-party and open-source software notices for Brewfather.
- [Account Deletion](https://docs.brewfather.app/legal/account-deletion.md): How to delete a Brewfather account, cancel a separately managed subscription, and understand active-system, backup, legal-retention, and third-party effects.


---

# 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.brewfather.app/legal.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.