> 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/how-we-use-information/graphics-and-design.md).

# Graphics & design

Briefs, brand assets, artwork and portfolio permission.

District Studio creates custom graphics, logos, branding, posters, banners, FiveM liveries, EUP and clothing designs, UI and UX designs, website and Discord graphics, digital artwork and other commissions.

We may use:

* **project briefs** describing what you need;
* **images, reference files and brand assets you send us**, which may include pictures of people, names or other personal information;
* **revisions and feedback**; and
* **final artwork and source files**.

We use the materials you send only to complete your commission, and do not share them with anyone other than the providers that store files for us.

**Portfolio and publication.** We do not publish or showcase your work, or the materials you sent us, in a portfolio, on social media or anywhere else without your permission. If you give permission, you can withdraw it at any time for future use by contacting us. We will remove the work from places we control. We cannot always remove copies that others have already shared.

{% 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/how-we-use-information/graphics-and-design.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.
