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

# Marketing & communications

Service messages, promotional marketing and how to opt out.

## Service messages

We send messages you need in order to use our services, such as order confirmations, licence details, project updates, subscription renewals, security notices and replies to support requests. These are not marketing, and you cannot opt out of them while you use the service. Where there is a choice, you can tell us how you would like to be contacted.

## Promotional marketing

Promotional marketing includes messages about new products, offers, discounts and services.

* **Email, text and WhatsApp marketing** are covered by PECR. We only send them to individuals who have agreed. Existing customers may also receive them where they bought, or asked about buying, something similar from us, were given an easy way to opt out when we collected their details, and are given an easy way to opt out in every message. This is known as the "soft opt-in".
* **Discord announcements** in our community server can be seen by its members. You can change your Discord notification settings or leave the server at any time. We do not send unrequested promotional direct messages through our bot.
* **Product announcements** on our Tebex store, websites and documentation are not sent to individuals.

You can opt out of marketing at any time by using the unsubscribe link or instructions in the message, or by emailing <mattwright@districtstudio.xyz>. We keep a record of your opt-out so that we do not contact you again.

{% hint style="info" %}
**Questions about your information?** Email <mattwright@districtstudio.xyz>.
{% 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://docs.districtstudio.xyz/privacy-policy/marketing.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.
