> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/terms-of-service-tos.md).

# Terms of Service (ToS)

The terms that apply to every Daddy Studio purchase.

*Last updated: October 2, 2026*

By buying from the [Daddy Studio store](https://daddy-studio.tebex.io/) you agree to these terms and to the Tebex Terms and Conditions shown at checkout. Every product also ships with a `LICENSE` file, which says the same in more detail.

## 1. License

* You buy a **license to use** the product, not ownership of it.
* The license belongs to the person who bought it and is linked to the Cfx account used at checkout.
* You may run the product on the servers **you own or operate** for your community, including a private test or development server.
* Every other person, community or company needs its own purchase.

## 2. What is not allowed

* Sharing, reselling, leaking or giving away the files, paid or free, original or modified.
* Uploading them to public repositories, file hosts or Discord servers.
* Removing copyright notices or trying to bypass Cfx escrow.

Breaking these rules ends your license and access to the product.

## 3. Open Source edition

* You may change the code for use on your own servers.
* Your changed version is still covered by section 2, you may not share or sell it.
* We support the product as shipped. For problems with a modified copy we may ask you to test on an unmodified copy first.

## 4. Refunds

* Products are delivered instantly as digital files, so **all sales are final**.
* If a product does not work and we cannot fix it in a reasonable time, we may offer an **exchange** or store credit, at our discretion.
* Payment problems (failed payments, receipts) are handled by **Tebex Support**.

## 5. Support

* Support is given through tickets on our [Discord](https://discord.gg/NFKjbN9s2q). You need the **Customer** role, which you get by linking your Discord at checkout.
* We help with installation, bugs in our code and questions about the docs.
* We do not support conflicts with third party resources, outdated server artifacts or changes you made to the code.

## 6. Bans and chargebacks

* If your server or account is banned by Cfx.re, we are not responsible for the lost access and no refund is given.
* Opening a chargeback without contacting us first removes all your licenses and access to our community.

## 7. Digital delivery

Delivery starts the moment the product is granted to your Keymaster account. Where the law gives a right of withdrawal for digital goods, it ends when delivery starts.

{% hint style="info" %}
Questions about these terms? Ask us on [Discord](https://discord.gg/NFKjbN9s2q).
{% endhint %}


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/terms-of-service-tos.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.