> 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/information-we-collect.md).

# Information we collect

The types of personal information we may collect, where it comes from, and why.

We collect only what we need for the service you use. We do not collect every category below from everyone.

## Information categories

<details>

<summary>Identity information</summary>

* **What:** name, username, display name, business name.
* **How:** from you when you enquire, order or sign up; from Tebex when you buy; from Discord when you talk to us or use our bot.
* **Why:** to identify you, provide our services and issue invoices.
* **Shared with:** our service providers ([Sharing & international transfers](https://docs.districtstudio.xyz/privacy-policy/sharing-and-transfers.md)).
* **Kept:** for as long as you are a customer, then as part of our business records ([Data retention](https://docs.districtstudio.xyz/privacy-policy/data-retention.md)).

</details>

<details>

<summary>Contact information</summary>

* **What:** email address, telephone or WhatsApp number, Discord username, billing or business address.
* **How:** from you; from Tebex when you buy.
* **Why:** to talk to you about orders, projects and support.
* **Shared with:** our email and messaging providers.
* **Kept:** while we have an ongoing relationship with you, and for a limited time afterwards in case of follow-up questions.

</details>

<details>

<summary>Account information</summary>

* **What:** dashboard login, account settings, linked Discord account, account status.
* **How:** when you create or use an account on our websites or dashboards.
* **Why:** to provide and secure your account.
* **Shared with:** our hosting and database providers.
* **Kept:** while your account is active, then deleted or anonymised once it is closed ([Data retention](https://docs.districtstudio.xyz/privacy-policy/data-retention.md)).

</details>

<details>

<summary>Discord information</summary>

* **What:** Discord User ID, username, display name, avatar, Server (Guild) ID, Channel and Role IDs, server name, and messages sent to our bot or in our support tickets.
* **How:** from Discord, through the permissions you or a server owner give our applications, and through Discord login when you sign in to a dashboard.
* **Why:** to run our bot and support channels, manage entitlements and provide dashboard features.
* **Shared with:** our hosting and database providers; Discord.
* **Kept:** while the bot or service is in use, then deleted ([Data retention](https://docs.districtstudio.xyz/privacy-policy/data-retention.md)).

</details>

<details>

<summary>Purchase information</summary>

* **What:** products bought, order and transaction references, purchase dates, licence and entitlement details, refund and dispute status.
* **How:** from Tebex and any other payment method you use.
* **Why:** to deliver products, confirm ownership, provide updates and support, and handle refunds and disputes.
* **Shared with:** Tebex; our accounting records.
* **Kept:** for as long as your licence or product support lasts, and for as long as tax law requires.

</details>

<details>

<summary>Billing information</summary>

* **What:** billing name and address, invoice details, payment status.
* **How:** from you; from Tebex or other payment providers.
* **Why:** to issue invoices and meet tax and accounting obligations.
* **Shared with:** accountants and professional advisers; HMRC where required.
* **Kept:** for as long as HMRC record-keeping rules require.

</details>

<details>

<summary>Transaction information</summary>

* **What:** payment amount, currency, type of payment method, and fraud-check results from the payment platform. We do not receive full payment card details.
* **How:** from Tebex and payment providers.
* **Why:** accounting, fraud prevention and handling disputes.
* **Shared with:** Tebex; payment providers.
* **Kept:** as for billing information.

</details>

<details>

<summary>Technical information</summary>

* **What:** IP address, browser and device type, operating system, timestamps, pages visited, error reports, access logs.
* **How:** automatically when you use our websites, dashboards, APIs or bot.
* **Why:** to run, secure and troubleshoot our services.
* **Shared with:** our hosting and infrastructure providers.
* **Kept:** for a short period needed for security and troubleshooting, then deleted automatically.

</details>

<details>

<summary>Server information</summary>

* **What:** FiveM server IP address and port, server identifiers, licence keys, framework (ESX, QBCore, QBox or standalone), resource lists, server configuration, server logs, database structure.
* **How:** from you when you ask for development or support; from licence checks where a product uses them.
* **Why:** to develop, install, configure, optimise and support resources and servers.
* **Shared with:** our hosting providers where relevant.
* **Kept:** for the length of the project or support request and any aftercare period.

</details>

<details>

<summary>Website information</summary>

* **What:** domain and DNS details, hosting details, website content, CMS data, analytics and technical logs for customer websites.
* **How:** from you when we build, host or maintain your website.
* **Why:** to develop, host and maintain your website.
* **Shared with:** hosting, domain and DNS providers.
* **Kept:** for the length of the project or hosting arrangement.

</details>

<details>

<summary>Support conversations</summary>

* **What:** ticket messages, emails, WhatsApp messages, screenshots, attachments, bug reports and logs you send us.
* **How:** from you, through any support channel.
* **Why:** to resolve your request and improve our services.
* **Shared with:** our email, messaging and hosting providers.
* **Kept:** while your request is open and for a limited time afterwards in case the issue comes back.

</details>

<details>

<summary>Files you send us</summary>

* **What:** server files, configuration files, database exports, images, reference files, brand assets, logos, documents.
* **How:** from you, as part of a project or support request.
* **Why:** to do the work you asked for.
* **Shared with:** our file storage providers.
* **Kept:** for the length of the project and aftercare period, then deleted.

</details>

<details>

<summary>Project information</summary>

* **What:** briefs, quotes, specifications, progress updates, feedback, revisions, deliverables.
* **How:** from you, and from our work on your project.
* **Why:** to deliver, document and support the project.
* **Shared with:** our file storage and source code hosting providers.
* **Kept:** for the aftercare period, and for as long as needed to deal with any legal claims.

</details>

<details>

<summary>Subscription information</summary>

* **What:** plan, start and renewal dates, status (active, cancelled or suspended), entitlements, linked servers.
* **How:** from the billing platform and from your use of the service.
* **Why:** to provide and manage subscription features.
* **Shared with:** the billing platform; our hosting and database providers.
* **Kept:** while the subscription is active, and for a short period after it ends ([Subscriptions & memberships](https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/subscriptions.md)).

</details>

<details>

<summary>Marketing preferences</summary>

* **What:** whether and when you opted in to or out of marketing.
* **How:** from you.
* **Why:** to respect your choices.
* **Shared with:** our email or messaging providers, if we send marketing.
* **Kept:** for as long as needed to honour your choice.

</details>

<details>

<summary>Security information</summary>

* **What:** login attempts, access records, suspected abuse, fraud signals, and enforcement actions on our services.
* **How:** automatically, and from our investigations.
* **Why:** to protect our services, customers and end users.
* **Shared with:** our hosting providers; the authorities where the law requires.
* **Kept:** for as long as needed to investigate and prevent the issue happening again.

</details>

<details>

<summary>Access credentials</summary>

* **What:** passwords, API keys, tokens, database credentials, server keys and hosting logins you give us for a project.
* **How:** from you, only where needed for the work.
* **Why:** to carry out development or support.
* **Shared with:** no one, unless it is essential to the work.
* **Kept:** only until the work is finished, then deleted ([Security & data breaches](https://docs.districtstudio.xyz/privacy-policy/security-and-breaches.md)).

</details>

## Special category information

District Studio does not intentionally collect special category information. You or your end users may still include it in support messages, tickets, application forms or files. If that happens, we use it only as far as needed to deal with the request or provide the service. Please do not send it unless it is necessary.

If a customer sets up an application form or other system that collects special category information from their own users, the customer is responsible, as controller, for having a lawful basis and a valid condition under UK GDPR Article 9. See [Data Processing & Customer Responsibilities](https://docs.districtstudio.xyz/for-customers/customer-data-processing.md).

## Information from third parties

We may receive personal information from:

* **Tebex**, when you buy from our store ([Tebex store & purchases](https://docs.districtstudio.xyz/privacy-policy/tebex-store.md));
* **Discord**, through our bot, our community server and Discord login;
* **payment providers**, about payment status, refunds and disputes;
* **customers**, who may give us information about their own end users so that we can carry out a project (for example, a database export); and
* **public sources**, such as a business website, where relevant to an enquiry.

## If you do not provide information

Some information is needed to deliver what you have asked for. Without it we may not be able to complete an order or project, verify a licence or provide support.

{% 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/information-we-collect.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.
