> 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/fivem-development.md).

# FiveM development

Server details, databases, logs and credentials in FiveM work.

District Studio develops custom FiveM scripts and resources for ESX, QBCore, QBox and standalone setups. We also build and configure FiveM servers, create gameplay systems, jobs, mechanics and admin tools, and provide installation, optimisation, database integration, maintenance and troubleshooting.

To do this we may use:

* **server IP addresses, ports and identifiers**, to work on the right server;
* **framework information and resource lists**, to make sure everything is compatible;
* **configuration files and resource details**, to build or install resources;
* **database information**, including its structure and, where unavoidable, contents that may include player data such as identifiers, character names, in-game money or inventories;
* **server logs and diagnostics**, to find and fix errors;
* **access credentials**, such as txAdmin, hosting panel, SFTP and database logins and server licence keys; and
* **server files** you provide.

Where a database or log contains information about players on your server, we handle it on your behalf as a processor, and we only access what the task needs.

{% hint style="warning" %}
**Protect your credentials.** Database logins, server keys and hosting accounts give full access to systems that may hold personal information.
{% endhint %}

We ask customers to:

* create a separate account with limited permissions for District Studio, where the platform allows, instead of sharing owner logins;
* send credentials privately, through a method we agree with you, and never in public Discord channels or ticket titles; and
* change or remove the access you gave us once the work is finished.

We use credentials only for the agreed work, do not share them unless that is essential to the work, and delete our copies when the work is complete.

{% 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/fivem-development.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.
