> 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/for-customers/customer-data-processing.md).

# Data processing for customers

When District Studio processes information on your behalf, and which services this covers.

<div align="center"><figure><img src="https://3989406933-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpUGRmPPvLXORDyWLvc5c%2Fuploads%2Fgit-blob-984945d22584bde6a35eec6dec5574943218e4b6%2Fdistrict-studio-logo.png?alt=media" alt="District Studio logo" width="140"><figcaption></figcaption></figure></div>

| Document detail |                  |
| --------------- | ---------------- |
| Business        | District Studio  |
| Version         | 1.0              |
| Effective date  | 18 November 2026 |
| Last updated    | 18 November 2026 |
| Next review     | November 2027    |

## Purpose and scope

This document explains how responsibilities for personal information are divided between District Studio and its customers when District Studio processes personal information **on a customer's behalf**.

It applies where District Studio builds, hosts, operates, maintains or supports software, bots, websites, databases, FiveM resources or integrations that process personal information about the customer's own users, players, members, staff or clients ("end users").

It supplements, and should be read with, the [Data Protection & Privacy Policy](https://docs.districtstudio.xyz/privacy-policy/privacy-policy.md), which explains how District Studio handles personal information as a controller for its own business.

This document describes District Studio's standard position. Where a written contract or Data Processing Agreement is agreed with a customer, that agreement takes priority.

## Controller and processor roles

### Definitions

Under UK GDPR:

* a **controller** determines the purposes and means of processing — it decides *why* personal information is processed and the essential elements of *how*;
* a **processor** processes personal information on behalf of a controller and only on its documented instructions.

The roles depend on what happens in practice, not on what a contract calls the parties. The ICO's guidance on [controllers and processors](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/controllers-and-processors/) explains the test.

### How the roles usually apply to District Studio

| Situation                                                                                                                                         | Customer's usual role                            | District Studio's usual role                                                       |
| ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ---------------------------------------------------------------------------------- |
| Customer's FiveM server database containing player data, accessed by District Studio for development or support                                   | Controller                                       | Processor                                                                          |
| Custom Discord bot built for a customer and hosted by District Studio                                                                             | Controller                                       | Processor                                                                          |
| Custom Discord bot built for a customer and handed over for the customer to host                                                                  | Controller                                       | Not involved after handover, except during support access (processor)              |
| District Studio's own bot: features configured by a server owner, such as ticket systems, application forms, moderation logs and welcome messages | Controller for their server's use of the feature | Processor                                                                          |
| District Studio's own bot: subscription and entitlement records, abuse prevention, service security, aggregate usage statistics                   | Not the controller                               | Controller                                                                         |
| Website hosted or maintained by District Studio for a customer, including contact forms and user accounts                                         | Controller                                       | Processor                                                                          |
| Website built and handed over, with no ongoing access                                                                                             | Controller                                       | Not involved after handover                                                        |
| Custom API or software hosted by District Studio for a customer                                                                                   | Controller                                       | Processor                                                                          |
| Third-party API integrated into a customer's system at the customer's request                                                                     | Controller                                       | Processor (during build or hosting); the third-party API provider has its own role |

Where District Studio uses information from a processor arrangement for its own purposes — for example, to investigate abuse of its own service — it acts as a controller for that limited purpose and only where permitted by law.

## Services covered

### Hosted Discord bots and customer Discord servers

Bots may process Discord User IDs, usernames, display names, Server (Guild) IDs, Channel IDs, Role IDs, messages, ticket transcripts, application submissions, moderation records and command logs.

The customer, as server owner or administrator, decides which features are enabled, what questions application forms ask, whether logs or transcripts are kept, and who in the server can view them. The bot can only access information that Discord makes available through the permissions and intents granted to it. District Studio cannot access information in servers or channels the bot has not been granted access to.

### Custom software and hosted applications

Software built or hosted by District Studio processes whatever personal information the customer's specification requires. The customer is responsible for deciding what information is collected.

### Websites

Websites may process visitor technical data, contact form submissions, user accounts, orders, analytics and content containing personal information. Where District Studio hosts or maintains the site, it processes this information on the customer's behalf.

### Databases

District Studio may design, migrate, optimise, back up or troubleshoot databases, including PostgreSQL and MySQL/MariaDB databases used by websites, bots and FiveM servers (for example via oxmysql). Database contents are the customer's data.

### FiveM resources and servers

FiveM servers commonly store player identifiers (such as Cfx.re, Discord, Steam, Rockstar licence identifiers and IP addresses), character data, chat or action logs and in-game economic data. When District Studio accesses a server, database or log files, it processes this information on the customer's behalf.

District Studio products sold through Tebex are installed and run by the customer on the customer's own server. District Studio does not receive player data from those products unless a product specifically sends data to District Studio, for example a licence check. Where a product does this, its documentation says what is sent.

### APIs and third-party integrations

Where District Studio integrates a third-party service into a customer's system (for example payment, messaging, AI, logging or game platform APIs), the customer chooses the integration and is responsible for its relationship with that provider, including any data processing terms required. District Studio will point out where an integration involves sharing personal information or international transfers, so far as reasonably apparent.

{% 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/for-customers/customer-data-processing.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.
