> 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/internal/before-publication/privacy-missing-information.md).

# Missing Information & Business Decisions

Everything District Studio must confirm or decide before the privacy documentation is published.

{% hint style="danger" %}
**Internal document.** Not part of District Studio's public privacy documentation.
{% endhint %}

| Document detail |                                          |
| --------------- | ---------------------------------------- |
| Document type   | Internal pre-publication assessment      |
| Applies to      | District Studio                          |
| Status          | Draft — not for publication              |
| Version         | \[REQUIRES CONFIRMATION — suggested 0.1] |
| Prepared        | 18 November 2026                         |

## 1. Purpose of this document

This document lists every item that District Studio must confirm, decide or implement before the following documents are published on GitBook:

* Data Protection & Privacy Policy (public space)
* Data Processing & Customer Responsibilities (public space)
* [Internal Privacy Compliance Checklist](https://docs.districtstudio.xyz/internal/ongoing-compliance/internal-privacy-compliance.md)

The published documents contain placeholders in the following form:

| Placeholder                  | Meaning                                                                                                                             |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| `[REQUIRES CONFIRMATION]`    | A fact about District Studio that has not been provided and must not be guessed.                                                    |
| `[IMPLEMENTATION REQUIRED]`  | A practice that the policy describes but which District Studio must put in place before, or as soon as possible after, publication. |
| `[LEGAL REVIEW RECOMMENDED]` | A point where the law is nuanced, recently changed, or depends on facts that a qualified adviser should check.                      |
| `[CONFIRM RETENTION PERIOD]` | A retention period that District Studio must decide and document.                                                                   |

Every placeholder should be resolved, or a conscious decision recorded, before the documents are made public. A privacy notice that describes practices District Studio does not actually follow creates more legal risk than a shorter, accurate notice.

## 2. How to use this document

For each item, the tables below set out:

1. **What needs confirming** — the question.
2. **Why it matters** — the legal or practical reason.
3. **What to provide** — the information needed to complete the documentation.
4. **Type** — **Legal requirement**, **Operational requirement** or **Recommendation**.
5. **Risk if not addressed** — the likely consequence.

When an item is resolved, update the relevant placeholder in each document and record the change in the version history in section 21 of the Data Protection & Privacy Policy (public space).

## 3. Legal research summary

The documentation has been drafted against the following UK legal framework. The position stated is as understood on the preparation date and should be checked by a qualified adviser before publication. \[LEGAL REVIEW RECOMMENDED]

| Instrument                                                                                                          | Relevance to District Studio                                                                                                                                                                                                                                                                                                                                 | Official source                                                                         |
| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- |
| UK General Data Protection Regulation (UK GDPR)                                                                     | Core principles, lawful bases, rights, controller and processor duties, breaches, international transfers.                                                                                                                                                                                                                                                   | [legislation.gov.uk — UK GDPR](https://www.legislation.gov.uk/eur/2016/679/contents)    |
| Data Protection Act 2018 (DPA 2018)                                                                                 | Supplements UK GDPR, including exemptions, the age of 13 for children's consent to online services, and offences.                                                                                                                                                                                                                                            | [legislation.gov.uk — DPA 2018](https://www.legislation.gov.uk/ukpga/2018/12/contents)  |
| Data (Use and Access) Act 2025 (DUAA)                                                                               | Amends UK GDPR, DPA 2018 and PECR. Most data protection amendments came into force on 5 February 2026 under the Commencement No. 6 Regulations (SI 2026/82). The complaints-handling provisions (section 103) were scheduled for 19 June 2026. Changes to the ICO's governance structure (the move to an "Information Commission") are commenced separately. | [legislation.gov.uk — DUAA 2025](https://www.legislation.gov.uk/ukpga/2025/18/contents) |
| Privacy and Electronic Communications Regulations 2003 (PECR)                                                       | Cookies and similar technologies, electronic marketing (email, SMS and similar), and security of electronic communications. DUAA introduced new cookie exemptions and raised maximum PECR penalties to UK GDPR levels.                                                                                                                                       | [legislation.gov.uk — PECR](https://www.legislation.gov.uk/uksi/2003/2426/contents)     |
| Data Protection (Charges and Information) Regulations 2018                                                          | Requirement for most controllers to pay an annual data protection fee to the ICO unless exempt.                                                                                                                                                                                                                                                              | [ICO — Data protection fee](https://ico.org.uk/for-organisations/data-protection-fee/)  |
| Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 and Consumer Rights Act 2015 | Not data protection law, but relevant to digital content sales, cancellation rights and refunds which the privacy documentation references.                                                                                                                                                                                                                  | [legislation.gov.uk](https://www.legislation.gov.uk/)                                   |

Key changes introduced by DUAA that are reflected in the documentation:

* **Recognised legitimate interests** — a new lawful basis (UK GDPR Article 6(1)(ea)) for specified purposes such as crime prevention, safeguarding and responding to emergencies, without a full balancing test.
* **Subject access requests** — confirmation that controllers need only carry out "reasonable and proportionate" searches, and a statutory "stop the clock" while awaiting identity verification or clarification.
* **Complaints** — controllers must have a process to receive data protection complaints, acknowledge them within 30 days and respond without undue delay.
* **Automated decision-making** — revised Articles 22A to 22D, replacing the previous general restriction with safeguards.
* **Cookies** — new exemptions from consent for certain low-risk purposes, including some analytics/statistical purposes and website appearance or functionality, subject to conditions (such as giving users clear information and a simple means to object). \[LEGAL REVIEW RECOMMENDED] — the ICO's final storage and access technologies guidance should be checked.
* **International transfers** — a revised "data protection test" for transfers, replacing the previous "essentially equivalent" standard.
* **PECR penalties** — increased to the UK GDPR maximum.

ICO guidance consulted in preparing these documents includes the ICO's guidance on the UK GDPR, the right of access, personal data breaches, international transfers, cookies, direct marketing, the Age Appropriate Design Code (Children's Code), and controllers and processors. Links are given in the relevant sections of each document.

Commentary sources used to check commencement dates (secondary sources, to be verified against legislation.gov.uk):

* [Kennedys — DUAA commencement dates and planned guidance for 2026](https://www.kennedyslaw.com/en/thought-leadership/article/2026/the-data-use-and-access-act-2025-commencement-dates-and-planned-guidance-for-2026)
* [DLA Piper — Commencement of the data protection provisions in the DUAA](https://privacymatters.dlapiper.com/2026/02/uk-commencement-of-the-data-protection-provisions-in-the-data-use-and-access-act/)
* [Hill Dickinson — DUAA changes come into effect](https://www.hilldickinson.com/our-view/articles/data-use-and-access-act-changes-to-uk-data-protection-law-come-into-effect/)

## 4. Confirmed information

The following has been confirmed by District Studio and is used throughout the documentation.

| Item                       | Confirmed value                                                                                                                                                                                                                                                                 |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Trading name               | District Studio                                                                                                                                                                                                                                                                 |
| Main website               | <https://districtstudio.xyz/>                                                                                                                                                                                                                                                   |
| Discord bot website        | <https://bot.districtstudio.xyz/>                                                                                                                                                                                                                                               |
| Tebex store                | <https://district-studio.tebex.store/> (existing, live sales channel)                                                                                                                                                                                                           |
| Business and privacy email | <mattwright@districtstudio.xyz>                                                                                                                                                                                                                                                 |
| Business telephone         | 07852879877                                                                                                                                                                                                                                                                     |
| Location                   | United Kingdom                                                                                                                                                                                                                                                                  |
| Legal status               | Sole trader — proprietor Matthew Wright                                                                                                                                                                                                                                         |
| Email provider             | Google Workspace                                                                                                                                                                                                                                                                |
| Domain and DNS             | Namecheap                                                                                                                                                                                                                                                                       |
| Support channels in use    | Discord tickets, WhatsApp Business, website contact form, telephone (calls not recorded)                                                                                                                                                                                        |
| ICO fee                    | Decision 18 November 2026: District Studio considers it is not required to pay. Keep a note of the reason (item 5.4).                                                                                                                                                           |
| Documentation platform     | GitBook                                                                                                                                                                                                                                                                         |
| Service lines              | FiveM development; website development; Discord bots and services (including District Studio's own bot and subscriptions); graphics, branding and digital design; digital products and software; custom orders and commissions; customer support; subscriptions and memberships |

Everything else in the documentation that describes specific providers, systems, periods or controls is either clearly marked as unconfirmed or is a general statement of legal duties.

## 4A. Commitments now stated in the published documents

The public documents were rewritten on 18 November 2026 so they make no unconfirmed factual claims. Retention is described by criteria, and providers by type, which UK GDPR Article 13 allows. The published wording does make these commitments, which District Studio must keep:

| Commitment                                                                                               | Where it is stated                    | What to do                                                                                                                                                         |
| -------------------------------------------------------------------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Customer data in hosted services deleted within 30 days of the service ending                            | Data Processing, section 11.2         | Set a reminder or automated clean-up.                                                                                                                              |
| Bot server data deleted within 30 days of the bot being removed                                          | Data Processing, section 11.3         | Handle the guild-remove event, or run a regular clean-up.                                                                                                          |
| Customers told about a breach within 48 hours                                                            | Data Processing, section 12           | Keep the breach procedure ready.                                                                                                                                   |
| 14 days' notice of new sub-processors, posted in Discord                                                 | Data Processing, section 9.1          | Post before adding a provider.                                                                                                                                     |
| Consent asked for before any non-essential cookies                                                       | Privacy Policy, section 12.3          | Complete the cookie audit (item 8.1).                                                                                                                              |
| No advertising or cross-site tracking cookies                                                            | Privacy Policy, section 12.3          | Confirm during the cookie audit.                                                                                                                                   |
| No solely automated significant decisions                                                                | Privacy Policy, section 18.1          | Confirm bot auto-moderation is configured by server owners.                                                                                                        |
| Contact form messages go to business email                                                               | Privacy Policy, section 6.7           | Confirm the form's delivery route.                                                                                                                                 |
| Security measures listed in section 14.2                                                                 | Privacy Policy, section 14.2          | Turn on 2-step verification on all business accounts, and confirm the other items.                                                                                 |
| Tebex checkout shows the digital-content waiver ("supply starts immediately; I lose my right to cancel") | Refund Policy, section 2.3            | Check the Tebex checkout shows this and the buyer must tick it. If not, add it to the store's checkout terms. Without it, consumers keep a 14-day right to cancel. |
| Proportionate refunds for consumer cancellations of new custom work and subscriptions within 14 days     | Refund Policy, sections 2.4 and 2.5   | Legal requirement; handle cancellation requests in this way.                                                                                                       |
| Ownership defaults for custom work (graphics transfer on full payment; code licensed)                    | Terms of Service, section 7           | Change in the Terms, or state otherwise in quotes.                                                                                                                 |
| 7-day acceptance window for delivered custom work                                                        | Terms of Service, section 6.3         | Change if a different period is wanted.                                                                                                                            |
| Governing law: England and Wales                                                                         | Terms of Service, section 18          | Change if District Studio is based in Scotland or Northern Ireland.                                                                                                |
| Names of providers given on request                                                                      | Privacy Policy, sections 8.2 and 10.2 | Keep the provider register current.                                                                                                                                |

The public documents now contain no placeholders.

## 5. Business identity and registration

| #   | What needs confirming                                                     | Why it matters                                                                                                                                                                                                                                                                                               | What to provide                                                                                                                                                                                      | Type                                    | Risk if not addressed                                                                                 |
| --- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| 5.1 | **Legal structure** — sole trader, partnership, limited company or other. | UK GDPR Article 13 requires the identity of the controller. The legal entity is the controller, not the trading name.                                                                                                                                                                                        | Legal structure and, for a sole trader, the name of the individual trading as District Studio.                                                                                                       | Legal requirement                       | Privacy notice fails to identify the controller; contracts and DPAs name the wrong party.             |
| 5.2 | **Registered company name and number**, if a limited company.             | Required to identify the controller; companies must also show this on websites under the Companies Act 2006 disclosure rules.                                                                                                                                                                                | Exact registered name, company number, country of registration.                                                                                                                                      | Legal requirement (if a company)        | Inaccurate controller identity; Companies Act non-compliance.                                         |
| 5.3 | **Registered office or business contact address.**                        | Article 13 requires controller contact details. An email address alone is generally acceptable for contact, but a postal address is expected for formal correspondence and some rights requests. A sole trader may use a business or service address rather than a home address. \[LEGAL REVIEW RECOMMENDED] | A postal address that District Studio is willing to publish, or a decision to publish email only.                                                                                                    | Legal requirement / Recommendation      | Individuals and the ICO cannot send formal correspondence; reduced credibility with business clients. |
| 5.4 | **ICO data protection fee status** and registration reference.            | Most organisations processing personal data must pay an annual fee to the ICO unless exempt. A business that processes customer data electronically for its services is unlikely to be exempt. Fees are tiered by size and turnover.                                                                         | Whether the fee has been paid, the registration number, the tier and the renewal date. Use the [ICO fee self-assessment](https://ico.org.uk/for-organisations/data-protection-fee/self-assessment/). | Legal requirement (unless exempt)       | ICO can issue fixed penalties for non-payment; register entry is publicly searchable.                 |
| 5.5 | **Whether a Data Protection Officer (DPO) is required or appointed.**     | A DPO is mandatory only for public authorities or where core activities involve large-scale regular and systematic monitoring or large-scale special category data. District Studio is unlikely to require one, but the decision should be recorded.                                                         | Confirmation that no DPO is required, or the DPO's details.                                                                                                                                          | Legal requirement (record the decision) | Policy may wrongly name or omit a DPO.                                                                |
| 5.6 | **Who is responsible for privacy** in practice.                           | Accountability principle; needed for the internal checklist and rights requests.                                                                                                                                                                                                                             | Name or role of the person responsible (likely the business owner).                                                                                                                                  | Operational requirement                 | Requests and incidents are not handled within statutory timescales.                                   |
| 5.7 | **Staff, contractors or freelancers** who access customer data.           | Determines access controls, confidentiality agreements and whether any contractor is a processor.                                                                                                                                                                                                            | Number and role of people with access; whether any are outside the UK.                                                                                                                               | Operational requirement                 | Uncontrolled access; undisclosed international transfers.                                             |

## 6. Infrastructure and hosting

| #    | What needs confirming                                                                                                                                         | Why it matters                                                                                                                                      | What to provide                                                                                            | Type                        | Risk if not addressed                                                                   |
| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------- | --------------------------------------------------------------------------------------- |
| 6.1  | **Which hosting providers are actually used**, and for which service (main website, bot website, Discord bot, APIs, customer-hosted projects).                | Processors must be identified in records of processing and, by category, in the privacy notice.                                                     | A list of each service and where it is hosted. Render is mentioned in the brief — confirm what runs on it. | Legal requirement           | Inaccurate privacy notice; undisclosed processors.                                      |
| 6.2  | **Whether VPS or dedicated servers are used**, the provider, and what runs on them.                                                                           | Same as above; also affects security responsibilities.                                                                                              | Provider names, purpose of each server.                                                                    | Legal requirement           | As above.                                                                               |
| 6.3  | **Hosting and data storage locations** (country or region) for each provider.                                                                                 | Determines whether international transfer rules apply.                                                                                              | The region selected in each provider's dashboard (for example Render region, VPS data centre).             | Legal requirement           | Transfers made without a lawful mechanism; inaccurate transfer statements.              |
| 6.4  | **Database infrastructure** — PostgreSQL is mentioned. Confirm provider (self-managed, Render Postgres, other), location, and what data each database stores. | Databases are where most personal data will reside; needed for the data inventory and retention.                                                    | Database list, provider, region, data stored.                                                              | Legal requirement           | Unknown data stores cannot be secured, searched for access requests or purged.          |
| 6.5  | **Cloud storage** used for customer files, assets or backups.                                                                                                 | Customer-supplied files may contain personal data; storage location and access controls must be known.                                              | Provider (for example Google Drive, OneDrive, Dropbox, S3) and what is stored.                             | Legal requirement           | Customer files retained indefinitely or exposed through shared links.                   |
| 6.6  | **Backup arrangements** — what is backed up, where, how often, how long kept, whether encrypted.                                                              | Backups must be covered by retention and deletion processes.                                                                                        | Backup schedule, provider, retention and encryption.                                                       | Operational requirement     | Deleted data persists in backups beyond the stated period; backups lost in an incident. |
| 6.7  | **Domain and DNS provider** — Namecheap is mentioned. Confirm it is the registrar and DNS host for both domains.                                              | Registrars may process the business owner's personal data (WHOIS) but usually little customer data. DNS providers may process visitor IP addresses. | Registrar and DNS provider for each domain; whether WHOIS privacy is enabled.                              | Recommendation              | Inaccurate provider register.                                                           |
| 6.8  | **Error reporting and monitoring tools** (for example Sentry, Better Stack, UptimeRobot, provider-native logs).                                               | These may capture IP addresses, user identifiers and request data.                                                                                  | Tools used and what they capture.                                                                          | Legal requirement (if used) | Undisclosed processors; excessive logging.                                              |
| 6.9  | **Application and access log retention** for websites, APIs and the bot.                                                                                      | Logs contain IP addresses and identifiers and must have a retention period.                                                                         | Where logs are kept and for how long by default.                                                           | Legal requirement           | Indefinite retention breaches the storage limitation principle.                         |
| 6.10 | **Source code hosting** — GitHub. Confirm whether customer data, credentials or configuration files are ever committed, and whether repositories are private. | Secrets or personal data in repositories is a common source of breaches.                                                                            | Confirmation that repositories containing customer work are private, and that secrets are excluded.        | Operational requirement     | Exposure of customer credentials or data.                                               |

## 7. Commerce and payments

| #   | What needs confirming                                                                                                                                                                                                                         | Why it matters                                                                                                                                     | What to provide                                                                                                                                                                              | Type                                          | Risk if not addressed                                              |
| --- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ------------------------------------------------------------------ |
| 7.1 | **Tebex configuration** — which products are sold, whether customers log in with FiveM (Cfx.re), Discord or another identity, and which data fields Tebex passes to District Studio.                                                          | Determines what District Studio receives from Tebex and must therefore disclose and protect.                                                       | Screenshot or list of the Tebex webstore settings: login method, checkout fields, integrations (Discord, FiveM Escrow/Keymaster, webhooks), and the data visible in the Tebex creator panel. | Legal requirement                             | Privacy notice inaccurate about data received from Tebex.          |
| 7.2 | **Tebex's role** — Tebex generally acts as the reseller / merchant of record for webstore sales, which supports treating it as an independent controller for checkout and payment data. Confirm by reviewing the current Tebex Creator terms. | The controller/processor split must be stated accurately.                                                                                          | Confirmation that the current Tebex creator agreement describes Tebex as reseller or merchant of record. Review [Tebex Privacy Policy](https://www.tebex.io/privacy).                        | Legal requirement \[LEGAL REVIEW RECOMMENDED] | Responsibility for checkout data misdescribed.                     |
| 7.3 | **Whether Tebex webhooks or APIs** send purchase data to District Studio systems (for example the Discord bot, a database or dashboard).                                                                                                      | Creates an additional data flow and storage location.                                                                                              | List of Tebex integrations and what each stores.                                                                                                                                             | Legal requirement                             | Undisclosed storage; no retention period.                          |
| 7.4 | **FiveM asset escrow / Cfx.re Keymaster** — whether scripts are delivered through Cfx.re asset escrow, and what data Cfx.re shares.                                                                                                           | Cfx.re (operated as part of Rockstar Games / Take-Two group) may be another independent controller in the delivery chain. \[REQUIRES CONFIRMATION] | Whether escrow is used; what District Studio sees in Keymaster.                                                                                                                              | Legal requirement (if used)                   | Incomplete third-party disclosure.                                 |
| 7.5 | **Payment providers for sales outside Tebex** — for example custom commissions, website projects and bot subscriptions. Is payment taken via PayPal, Stripe, bank transfer, Tebex or another method?                                          | Each payment route has different data flows and controllers.                                                                                       | Every payment method used and for which services.                                                                                                                                            | Legal requirement                             | Invented or missing payment providers.                             |
| 7.6 | **Whether District Studio ever receives or stores card details.**                                                                                                                                                                             | The documentation states District Studio does not receive full card details. This must be true.                                                    | Confirmation.                                                                                                                                                                                | Legal requirement                             | Misleading statement; PCI DSS obligations if card data is handled. |
| 7.7 | **Invoicing and accounting tools** (for example spreadsheets, Xero, QuickBooks, FreeAgent, Wave).                                                                                                                                             | Accounting records contain personal data and have statutory retention requirements.                                                                | Tools used and where invoices are stored.                                                                                                                                                    | Legal requirement                             | Accounting data retained without a documented period.              |
| 7.8 | **Refund, cancellation and chargeback procedure** for digital products and commissions.                                                                                                                                                       | The privacy documentation refers to processing for refunds and disputes; consumer law governs digital content cancellation.                        | Link to District Studio's terms of sale or refund policy. \[REQUIRES CONFIRMATION]                                                                                                           | Operational requirement                       | Inconsistency between privacy and sales terms.                     |
| 7.9 | **Bot subscription billing** — how subscriptions for the District Studio bot are sold and managed (Tebex subscriptions, Discord's own premium apps, Stripe, other).                                                                           | Determines controllers and what subscription data District Studio holds.                                                                           | Billing method and what status data is synced to the bot.                                                                                                                                    | Legal requirement                             | Subscription section inaccurate.                                   |

## 8. Websites, cookies and analytics

| #   | What needs confirming                                                                                                                                                  | Why it matters                                                                                                          | What to provide                                                                                                                  | Type                                                                      | Risk if not addressed                               |
| --- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------------------------- |
| 8.1 | **Cookies and similar technologies** set by districtstudio.xyz and bot.districtstudio.xyz.                                                                             | PECR requires clear information and, unless an exemption applies, prior consent.                                        | A cookie audit: name, provider, purpose, duration for each cookie and local storage item. Browser developer tools can list them. | Legal requirement                                                         | PECR breach; fines now up to UK GDPR levels.        |
| 8.2 | **Analytics** — whether any analytics tool is used (for example Google Analytics, Plausible, Umami, Cloudflare Web Analytics, Vercel Analytics, Render metrics).       | Analytics cookies usually require consent unless the new DUAA statistical exemption applies and its conditions are met. | Tool name, configuration and whether it sets cookies.                                                                            | Legal requirement                                                         | Unlawful tracking; inaccurate cookie section.       |
| 8.3 | **Consent mechanism** — whether a cookie banner or consent management platform exists.                                                                                 | Required where non-exempt cookies are used.                                                                             | Description or screenshot.                                                                                                       | Legal requirement (if non-exempt cookies used) \[IMPLEMENTATION REQUIRED] | PECR breach.                                        |
| 8.4 | **Embedded third-party content** (Discord widgets, YouTube embeds, Google Fonts, CDN scripts, Tebex widgets).                                                          | Embedded content can set cookies and transfer IP addresses to third parties.                                            | List of embeds and external scripts.                                                                                             | Legal requirement                                                         | Undisclosed third-party tracking.                   |
| 8.5 | **Website contact forms** — whether one exists, where submissions go (email, database, form service such as Formspree, Netlify Forms, EmailJS).                        | Form services are processors.                                                                                           | Form provider and destination.                                                                                                   | Legal requirement                                                         | Undisclosed processor.                              |
| 8.6 | **Customer accounts and dashboards** — whether bot.districtstudio.xyz or the main site has user accounts, and how login works (Discord OAuth2, email/password, other). | Determines account data held and security obligations.                                                                  | Login method, OAuth scopes requested, data stored per account.                                                                   | Legal requirement                                                         | Account section inaccurate; excessive OAuth scopes. |
| 8.7 | **Customer websites hosted by District Studio** — whether District Studio hosts or manages websites for clients after delivery.                                        | District Studio would be a processor for that data.                                                                     | List of hosted client sites and services provided.                                                                               | Legal requirement                                                         | No DPA in place.                                    |

## 9. Discord bot and software services

| #    | What needs confirming                                                                                                                                                                     | Why it matters                                                                                                         | What to provide                                                                     | Type                                                          | Risk if not addressed                                                   |
| ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------- |
| 9.1  | **Discord bot data storage** — what the District Studio bot stores (user IDs, guild IDs, ticket transcripts, applications, moderation logs, command logs), where and for how long.        | Core to the bot section and retention schedule.                                                                        | A list of database tables or collections and their fields.                          | Legal requirement                                             | Inaccurate notice; data kept indefinitely.                              |
| 9.2  | **Privileged gateway intents** — whether the bot uses the Message Content, Server Members or Presence intents.                                                                            | Determines whether message content and member lists are processed; Discord also requires disclosure and justification. | Intents enabled in the Discord Developer Portal.                                    | Legal requirement                                             | Policy overstates or understates processing; Discord policy breach.     |
| 9.3  | **Ticket transcripts** — whether transcripts are generated, where they are stored (Discord channel, database, file host) and who can access them.                                         | Transcripts may contain sensitive personal data and attachments.                                                       | Transcript method and storage.                                                      | Legal requirement                                             | Uncontrolled retention of support conversations.                        |
| 9.4  | **Controller/processor position for the bot** — in which features District Studio decides the purpose (controller) and in which it acts on the server owner's configuration (processor).  | Determines who must answer rights requests and provide notices to server members.                                      | Confirmation of feature list and configuration options. \[LEGAL REVIEW RECOMMENDED] | Legal requirement                                             | Rights requests mishandled; server owners unaware of their obligations. |
| 9.5  | **Bot terms of service and privacy page** — whether bot.districtstudio.xyz already has terms or a privacy page, and the URL given in the Discord Developer Portal.                        | Discord requires verified apps to provide a privacy policy URL.                                                        | URLs of existing pages.                                                             | Legal requirement (Discord platform requirement)              | Inconsistent policies; Discord verification issues.                     |
| 9.6  | **Custom bots delivered to clients** — whether District Studio hosts them after delivery or hands them over.                                                                              | Determines ongoing processor responsibilities.                                                                         | Default arrangement for custom bots.                                                | Operational requirement                                       | Unclear ongoing responsibility.                                         |
| 9.7  | **Third-party APIs** used by bots, websites or scripts (for example OpenAI or other AI APIs, Steam, Roblox, translation services, image hosting, FiveManage).                             | Each API that receives personal data is a processor or independent controller and may involve international transfers. | List of APIs and what data each receives.                                           | Legal requirement                                             | Undisclosed transfers.                                                  |
| 9.8  | **Automated decision-making** — whether any bot feature makes decisions with significant effects without human involvement (for example automatic bans, automatic application rejection). | DUAA's revised Articles 22A–22D impose safeguards for significant decisions based solely on automated processing.      | Description of automated moderation and application features.                       | Legal requirement (if applicable) \[LEGAL REVIEW RECOMMENDED] | Rights not provided; complaints.                                        |
| 9.9  | **FiveM resources that collect player data** — whether any District Studio scripts log player identifiers, IPs or send telemetry to District Studio.                                      | If scripts send data back to District Studio, it becomes a controller or processor for player data.                    | Confirmation for each product.                                                      | Legal requirement                                             | Undisclosed collection from end users.                                  |
| 9.10 | **Licence verification** — whether products phone home for licence checks and what data is sent (server IP, licence key, identifiers).                                                    | This is processing by District Studio of customer and possibly server data.                                            | Description of licence system.                                                      | Legal requirement                                             | Undisclosed processing.                                                 |

## 10. Communications and support

| #    | What needs confirming                                                                                                                            | Why it matters                                                                                | What to provide                 | Type                            | Risk if not addressed              |
| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | ------------------------------- | ------------------------------- | ---------------------------------- |
| 10.1 | **Email provider** for <mattwright@districtstudio.xyz> (for example Google Workspace, Microsoft 365, Zoho, Namecheap Private Email).             | Processor; holds large volumes of customer correspondence.                                    | Provider and plan.              | Legal requirement               | Undisclosed processor.             |
| 10.2 | **WhatsApp Business** — whether it is actually used, on which number, and whether the WhatsApp Business app or the API (via a provider) is used. | WhatsApp/Meta is an independent controller for some data; the API route involves a processor. | Confirmation and set-up.        | Legal requirement               | Inaccurate communications section. |
| 10.3 | **Mailing list or newsletter tool**, if any (for example Mailchimp, Brevo, Discord announcements only).                                          | Marketing consent and opt-out records must be kept.                                           | Tool and how sign-ups occur.    | Legal requirement (if used)     | PECR breach.                       |
| 10.4 | **Support ticket systems** other than Discord (for example a helpdesk tool).                                                                     | Processor disclosure.                                                                         | Tool name or confirmation none. | Legal requirement               | Undisclosed processor.             |
| 10.5 | **Telephone use** — whether calls are recorded and whether the published number is a mobile used for WhatsApp.                                   | Call recording requires notice.                                                               | Confirmation.                   | Legal requirement (if recorded) | Unlawful recording.                |

## 11. Retention and deletion

All retention periods are placeholders. District Studio must decide them, document the reasoning, and be able to apply them.

| #     | Record type                                                                 | Suggested basis for deciding                                                                                                                                                                                                                             | Type                                   | Risk if not addressed                                   |
| ----- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- | ------------------------------------------------------- |
| 11.1  | Accounting and invoicing records                                            | HMRC generally expects business records to be kept for at least 5 years after the 31 January submission deadline of the relevant tax year (sole traders), or 6 years from the end of the financial year (limited companies). \[LEGAL REVIEW RECOMMENDED] | Legal requirement                      | Tax non-compliance or over-retention.                   |
| 11.2  | Purchase and licence records                                                | Duration of the licence or product support, plus a period to handle disputes and chargebacks.                                                                                                                                                            | Legal requirement (storage limitation) | Inability to verify ownership, or indefinite retention. |
| 11.3  | Customer accounts and bot dashboards                                        | While the account is active, plus a defined period after closure.                                                                                                                                                                                        | Legal requirement                      | Dormant accounts retained indefinitely.                 |
| 11.4  | Support tickets and transcripts                                             | Time needed to resolve the issue and handle follow-ups.                                                                                                                                                                                                  | Legal requirement                      | Sensitive messages kept indefinitely.                   |
| 11.5  | Discord applications and moderation records stored by District Studio's bot | Where District Studio is controller: decide period. Where processor: as configured by server owner.                                                                                                                                                      | Legal requirement                      | Unclear who deletes what.                               |
| 11.6  | Development project files and briefs                                        | Warranty/aftercare period plus a limitation period for contract claims (6 years in England and Wales). \[LEGAL REVIEW RECOMMENDED]                                                                                                                       | Legal requirement                      | Customer files kept indefinitely.                       |
| 11.7  | Customer credentials (server, hosting, database passwords)                  | Shortest possible: delete or require rotation at project completion.                                                                                                                                                                                     | Legal requirement (security)           | Credential compromise long after project ends.          |
| 11.8  | Technical and access logs                                                   | Short period suitable for security and troubleshooting.                                                                                                                                                                                                  | Legal requirement                      | Over-retention of IPs.                                  |
| 11.9  | Backups                                                                     | Rolling period aligned with live data retention.                                                                                                                                                                                                         | Operational requirement                | Deleted data persists.                                  |
| 11.10 | Marketing preferences and suppression lists                                 | Keep opt-out records for as long as needed to honour them.                                                                                                                                                                                               | Legal requirement                      | Re-contacting people who opted out.                     |
| 11.11 | Security incident and breach records                                        | UK GDPR Article 33(5) requires all breaches to be documented.                                                                                                                                                                                            | Legal requirement                      | Accountability failure.                                 |
| 11.12 | Rights request records                                                      | Period needed to evidence compliance.                                                                                                                                                                                                                    | Recommendation                         | Unable to respond to ICO enquiries.                     |

**What to provide:** a completed retention schedule using the template in section 5 of the [Internal Privacy Compliance Checklist](https://docs.districtstudio.xyz/internal/ongoing-compliance/internal-privacy-compliance.md).

## 12. Security

| #    | What needs confirming                                                                                                                                                                                                           | Why it matters                                                                                                                  | What to provide                                                                                                                                                                             | Type                         | Risk if not addressed                          |
| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- | ---------------------------------------------- |
| 12.1 | **Security controls currently in place** — multi-factor authentication on Discord, GitHub, email, Tebex, hosting and domain accounts; password manager; device encryption; HTTPS on both domains; database access restrictions. | Article 32 requires appropriate technical and organisational measures. The policy must not describe controls that do not exist. | A yes/no list against the controls in section 7 of the [Internal Privacy Compliance Checklist](https://docs.districtstudio.xyz/internal/ongoing-compliance/internal-privacy-compliance.md). | Legal requirement            | Misleading security statements; weak security. |
| 12.2 | **How customer credentials are received and stored** (Discord DMs, email, password manager sharing, encrypted vault).                                                                                                           | Credentials are high-risk data.                                                                                                 | Current practice.                                                                                                                                                                           | Legal requirement            | Credential leakage.                            |
| 12.3 | **Encryption** — at rest and in transit for databases, backups and storage.                                                                                                                                                     | The policy only refers to encryption "where implemented".                                                                       | Which systems are encrypted.                                                                                                                                                                | Recommendation               | Overstated claims.                             |
| 12.4 | **Security certifications** — none should be claimed unless held (for example Cyber Essentials).                                                                                                                                | Must not invent certifications.                                                                                                 | Certification details, or confirmation none.                                                                                                                                                | Legal requirement (accuracy) | Misrepresentation.                             |
| 12.5 | **Incident response readiness** — who decides whether to notify the ICO and customers, and how quickly.                                                                                                                         | Notifiable breaches must be reported to the ICO within 72 hours of becoming aware.                                              | Named person and contact route.                                                                                                                                                             | Legal requirement            | Late notification.                             |
| 12.6 | **Device security** — computers and phones used for business (screen lock, disk encryption, updates).                                                                                                                           | Most small business breaches involve lost or compromised devices or accounts.                                                   | Confirmation.                                                                                                                                                                               | Recommendation               | Data loss.                                     |

## 13. Contracts, processors and transfers

| #    | What needs confirming                                                                                                                                                                                                                                                                                                | Why it matters                                                                                                                             | What to provide                                                                       | Type                               | Risk if not addressed                      |
| ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------- | ---------------------------------- | ------------------------------------------ |
| 13.1 | **Data Processing Agreements with providers** — whether District Studio has accepted each provider's DPA (Render, email provider, database host, cloud storage, analytics).                                                                                                                                          | Article 28 requires a written contract with every processor. Most providers offer a standard DPA within their terms or as a click-through. | Confirmation and copies or links for each provider.                                   | Legal requirement                  | Unlawful use of processors.                |
| 13.2 | **Data Processing Agreements with customers** — where District Studio processes data on behalf of clients (hosted bots, hosted websites, databases).                                                                                                                                                                 | Article 28 equally applies where District Studio is the processor.                                                                         | Decision on adopting a standard DPA template. \[IMPLEMENTATION REQUIRED]              | Legal requirement                  | Client relationships lack required terms.  |
| 13.3 | **Customer terms of service** — whether written terms exist for commissions, subscriptions and products.                                                                                                                                                                                                             | The privacy documents reference terms that must exist and be consistent.                                                                   | Links to existing terms, or confirmation they need drafting.                          | Operational requirement            | Inconsistent or missing contractual basis. |
| 13.4 | **International transfer mechanisms** for each provider outside the UK — UK adequacy regulations (including the EEA and, for certified organisations, the UK Extension to the EU-US Data Privacy Framework), the International Data Transfer Agreement (IDTA) or the UK Addendum to EU Standard Contractual Clauses. | Transfers outside the UK must meet the UK GDPR Chapter V requirements.                                                                     | For each provider: country, mechanism relied on (often stated in the provider's DPA). | Legal requirement                  | Unlawful transfers.                        |
| 13.5 | **Portfolio permissions** — whether District Studio currently publishes client work, and whether permission is obtained.                                                                                                                                                                                             | Publishing work containing client branding, names or personal data requires permission.                                                    | Current practice and wording of any permission clause.                                | Legal requirement / Recommendation | Complaints, IP disputes.                   |

## 14. Customers, children and marketing

| #    | What needs confirming                                                                                                                                                                                                  | Why it matters                                                                                                                                                                                                                                                                                                 | What to provide                                                               | Type                                  | Risk if not addressed                                 |
| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------- | ----------------------------------------------------- |
| 14.1 | **Minimum age** — whether District Studio sets a minimum age for purchases, commissions, bot use or dashboard accounts. The documentation does not invent one.                                                         | Under DPA 2018 section 9, where consent is relied on for online services offered directly to a child, children aged 13 or over can consent themselves. Platform ages also apply (Discord's minimum age in the UK is 13; Tebex and payment providers set their own). Contract law also limits minors' capacity. | A decision, ideally recorded in terms of service. \[LEGAL REVIEW RECOMMENDED] | Legal requirement (decision)          | Uncertain treatment of under-18 customers.            |
| 14.2 | **Children's Code applicability** — whether any District Studio online service is likely to be accessed by children (the District Studio bot and dashboard may be, given Discord's user base).                         | The ICO's Age Appropriate Design Code applies to information society services likely to be accessed by under-18s in the UK. DUAA added a "children's higher protection matters" duty.                                                                                                                          | Assessment of likely users.                                                   | Legal requirement                     | ICO enforcement; design not appropriate for children. |
| 14.3 | **Marketing practices** — whether promotional emails or WhatsApp messages are sent, and whether consent or the soft opt-in is used.                                                                                    | PECR rules on electronic marketing.                                                                                                                                                                                                                                                                            | Description of current marketing.                                             | Legal requirement (if marketing sent) | PECR breach.                                          |
| 14.4 | **Special category data** — whether District Studio ever intentionally collects health, ethnicity, religion, sexual orientation or similar data (for example through custom application forms it designs for clients). | Requires an Article 9 condition. The default position in the documentation is that District Studio does not intentionally collect it.                                                                                                                                                                          | Confirmation.                                                                 | Legal requirement                     | Unlawful processing of sensitive data.                |
| 14.5 | **Policy dates and versioning** — effective date, review date, version numbering.                                                                                                                                      | Transparency and accountability.                                                                                                                                                                                                                                                                               | Dates to insert.                                                              | Operational requirement               | Users cannot tell which version applies.              |

## 15. Priority summary

Resolve these before publication:

1. Legal identity of the controller (5.1–5.3).
2. ICO data protection fee: decided not required; record the reasoning (5.4).
3. Actual hosting, database and storage providers and locations (6.1–6.5).
4. Tebex configuration and what District Studio receives (7.1–7.3).
5. Other payment methods and confirmation that card data is never received (7.5–7.6).
6. Cookie and analytics audit and, if required, a consent mechanism (8.1–8.3).
7. Discord bot data storage and intents (9.1–9.2).
8. Email provider (10.1).
9. Retention schedule (section 11).
10. Security controls actually in place (12.1–12.2).

Resolve soon after publication:

* Processor DPAs and transfer mechanisms (13.1, 13.4).
* Customer DPA template (13.2).
* Children's Code assessment (14.2).
* Remaining recommendations.

***

*This assessment is not legal advice. District Studio should consider having the completed documentation reviewed by a qualified UK data protection adviser before publication.* \[LEGAL REVIEW RECOMMENDED]


---

# 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/internal/before-publication/privacy-missing-information.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.
