> 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/ongoing-compliance/internal-privacy-compliance.md).

# Internal Privacy Compliance Checklist

Operational checklist for keeping District Studio's privacy practices compliant.

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

| Document detail |                                                           |
| --------------- | --------------------------------------------------------- |
| Business        | District Studio                                           |
| Document type   | Internal — not for public publication                     |
| Version         | \[REQUIRES CONFIRMATION — suggested 1.0]                  |
| Owner           | \[REQUIRES CONFIRMATION — person responsible for privacy] |
| Last reviewed   | \[REQUIRES CONFIRMATION]                                  |
| Next review     | \[REQUIRES CONFIRMATION]                                  |

## 1. How to use this checklist

* Tick each item only when it has been completed **and** the evidence described has been saved.
* Store evidence in a private location. \[REQUIRES CONFIRMATION — for example a private folder or private GitBook space.]
* Items marked **(Before publication)** should be completed before the public privacy documents go live.
* Review the whole checklist at least annually, and whenever a new service, provider or product is introduced.
* Outstanding facts are listed in [Privacy Documentation — Missing Information & Business Decisions](https://docs.districtstudio.xyz/internal/before-publication/privacy-missing-information.md).

## 2. Governance and ICO registration

* [ ] **Confirm the legal entity acting as controller** (Before publication)
  * *What to do:* Confirm whether District Studio is a sole trader or a company, and the legal name.
  * *How to verify:* Companies House record or HMRC self-assessment registration saved as evidence.
* [ ] **Record the ICO data protection fee decision**
  * *Decision (18 November 2026):* District Studio considers it does not need to pay the fee.
  * *What to do:* Save the result of the [ICO fee self-assessment](https://ico.org.uk/for-organisations/data-protection-fee/self-assessment/) that supports this, and look at it again if the business grows, takes on staff, or starts processing data in new ways.
  * *How to verify:* ICO registration certificate and reference saved; reference inserted into section 2 of the Data Protection & Privacy Policy (public space); renewal date in calendar.
* [ ] **Record the DPO decision**
  * *What to do:* Document why a DPO is or is not required.
  * *How to verify:* Short written note saved with evidence.
* [ ] **Name the person responsible for privacy**
  * *What to do:* Assign responsibility for requests, complaints and incidents.
  * *How to verify:* Name recorded at the top of this checklist.
* [ ] **Monitor legal changes**
  * *What to do:* Check ICO updates on the Data (Use and Access) Act 2025, including final cookies (storage and access technologies) guidance and any change to the ICO's name and structure.
  * *How to verify:* Entry in the review log (section 23) at each review.

## 3. Privacy notices

* [ ] **Resolve all placeholders in the public documents** (Before publication)
  * *What to do:* Replace every `[REQUIRES CONFIRMATION]`, `[CONFIRM RETENTION PERIOD]` and `[IMPLEMENTATION REQUIRED]` marker, or remove statements that do not apply.
  * *How to verify:* Search each published file for `[` placeholders; none remain.
* [ ] **Link the privacy policy from every service** (Before publication)
  * *What to do:* Add a link from districtstudio.xyz, bot.districtstudio.xyz, the Tebex store footer or description, the Discord server (for example an information channel), and the Discord Developer Portal privacy policy URL field.
  * *How to verify:* Screenshot of each link.
* [ ] **Check the policy matches practice**
  * *What to do:* Compare every statement in the policy against how District Studio actually operates.
  * *How to verify:* Annual sign-off in the review log.
* [ ] **Legal review**
  * *What to do:* Arrange review of the completed documents by a qualified adviser. \[LEGAL REVIEW RECOMMENDED]
  * *How to verify:* Adviser's comments saved and addressed.

## 4. Data inventory and data mapping

* [ ] **Create a data inventory (record of processing activities)** (Before publication)
  * *What to do:* Complete the table below for every system. Small organisations may be exempt from some record-keeping under Article 30(5), but keeping one is strongly recommended and needed to support this documentation.
  * *How to verify:* Completed table, reviewed annually.

| System / activity                                | Personal data                               | Individuals           | Purpose                   | Lawful basis                   | Role (controller / processor)             | Location / provider      | Retention         | Shared with              |
| ------------------------------------------------ | ------------------------------------------- | --------------------- | ------------------------- | ------------------------------ | ----------------------------------------- | ------------------------ | ----------------- | ------------------------ |
| Tebex store                                      | Name, email, purchase, entitlement, IP      | Customers             | Sales, delivery, support  | Contract; legal obligation     | Controller (Tebex independent controller) | Tebex                    | \[CONFIRM]        | Tebex                    |
| Discord community and tickets                    | Discord IDs, messages, attachments          | Customers, prospects  | Support                   | Contract; legitimate interests | Controller                                | Discord; \[bot hosting]  | \[CONFIRM]        | Discord                  |
| District Studio bot — own records                | Discord IDs, guild IDs, subscriptions, logs | Server owners, users  | Operate service; security | Contract; legitimate interests | Controller                                | \[REQUIRES CONFIRMATION] | \[CONFIRM]        | Hosting provider         |
| District Studio bot — server-configured features | Tickets, applications, moderation records   | Server members        | Server owner's purposes   | Customer's basis               | Processor                                 | \[REQUIRES CONFIRMATION] | As configured     | Hosting provider         |
| Bot dashboard                                    | Discord OAuth2 profile, settings            | Server administrators | Account access            | Contract                       | Controller                                | \[REQUIRES CONFIRMATION] | \[CONFIRM]        | Hosting provider         |
| Main website                                     | IP, technical data, contact form            | Visitors              | Operate site; enquiries   | Legitimate interests           | Controller                                | \[REQUIRES CONFIRMATION] | \[CONFIRM]        | Hosting provider         |
| Business email                                   | Correspondence                              | Customers, suppliers  | Communication             | Contract; legitimate interests | Controller                                | \[REQUIRES CONFIRMATION] | \[CONFIRM]        | Email provider           |
| WhatsApp Business                                | Phone number, messages                      | Customers             | Communication             | Contract; legitimate interests | Controller                                | WhatsApp                 | \[CONFIRM]        | WhatsApp                 |
| Commissions and projects                         | Briefs, files, credentials                  | Customers             | Deliver projects          | Contract                       | Controller                                | \[REQUIRES CONFIRMATION] | \[CONFIRM]        | Storage provider; GitHub |
| Customer FiveM servers and databases             | Player identifiers, character data, logs    | Customers' players    | Development and support   | Customer's basis               | Processor                                 | Customer's host          | Project only      | None                     |
| Hosted customer websites and bots                | As per customer system                      | Customers' users      | Hosting                   | Customer's basis               | Processor                                 | \[REQUIRES CONFIRMATION] | As agreed         | Sub-processors           |
| Accounting                                       | Invoices, payments                          | Customers             | Tax and accounts          | Legal obligation               | Controller                                | \[REQUIRES CONFIRMATION] | \[CONFIRM — HMRC] | Accountant; HMRC         |

* [ ] **Draw a data flow map**
  * *What to do:* Show how data moves between Tebex, Discord, the bot, the websites, databases, email and storage.
  * *How to verify:* Diagram saved; updated when integrations change.

## 5. Retention schedule

* [ ] **Decide and record every retention period** (Before publication)
  * *What to do:* Complete the table. Base periods on purpose and legal requirements; do not keep data "just in case".
  * *How to verify:* Completed table; periods inserted into section 13 of the Data Protection & Privacy Policy (public space).

| Record type                              | Retention period               | Trigger (starts from)       | Justification                                         | Deletion method | Owner |
| ---------------------------------------- | ------------------------------ | --------------------------- | ----------------------------------------------------- | --------------- | ----- |
| Customer accounts                        | \[CONFIRM RETENTION PERIOD]    | Account closure             |                                                       |                 |       |
| Discord bot records (controller)         | \[CONFIRM RETENTION PERIOD]    |                             |                                                       |                 |       |
| Discord bot records (processor)          | \[CONFIRM RETENTION PERIOD]    | Bot removal / service end   |                                                       |                 |       |
| Support tickets and transcripts          | \[CONFIRM RETENTION PERIOD]    | Ticket closure              |                                                       |                 |       |
| Applications                             | \[CONFIRM RETENTION PERIOD]    | Decision                    |                                                       |                 |       |
| Purchase and licence records             | \[CONFIRM RETENTION PERIOD]    | Purchase                    |                                                       |                 |       |
| Accounting information                   | \[CONFIRM RETENTION PERIOD]    | End of tax / financial year | HMRC record-keeping rules \[LEGAL REVIEW RECOMMENDED] |                 |       |
| Development projects                     | \[CONFIRM RETENTION PERIOD]    | Delivery                    |                                                       |                 |       |
| Customer files                           | \[CONFIRM RETENTION PERIOD]    | Project completion          |                                                       |                 |       |
| Customer credentials                     | Delete at completion           | Project completion          | Security                                              |                 |       |
| Technical logs                           | \[CONFIRM RETENTION PERIOD]    | Creation                    |                                                       |                 |       |
| Database backups                         | \[CONFIRM RETENTION PERIOD]    | Creation                    |                                                       |                 |       |
| Security records                         | \[CONFIRM RETENTION PERIOD]    | Incident closure            |                                                       |                 |       |
| Marketing preferences / suppression list | While needed to honour opt-out | Opt-out                     | PECR                                                  |                 |       |
| Subscription information                 | \[CONFIRM RETENTION PERIOD]    | Subscription end            |                                                       |                 |       |
| Rights requests and complaints           | \[CONFIRM RETENTION PERIOD]    | Closure                     | Accountability                                        |                 |       |

* [ ] **Implement deletion**
  * *What to do:* Set a recurring calendar reminder or automated job to delete expired records. \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Deletion log entries at each run.

## 6. Cookie compliance

* [ ] **Audit cookies and similar technologies on both websites** (Before publication)
  * *What to do:* Use browser developer tools (Application tab) to list cookies, local storage and third-party requests on districtstudio.xyz and bot.districtstudio.xyz.
  * *How to verify:* Saved list with name, provider, purpose and duration.
* [ ] **Classify each item as strictly necessary, exempt, or consent-required**
  * *What to do:* Apply PECR as amended by the Data (Use and Access) Act 2025 and current ICO guidance. \[LEGAL REVIEW RECOMMENDED]
  * *How to verify:* Classification recorded against each item.
* [ ] **Implement consent where required**
  * *What to do:* Add a banner that blocks non-essential cookies until consent, with equally prominent accept and reject options and a way to withdraw. \[IMPLEMENTATION REQUIRED — only if consent-required cookies exist]
  * *How to verify:* Test in a private window that no non-essential cookies are set before consent.
* [ ] **Publish the cookie table** in section 12.3 of the privacy policy.
  * *How to verify:* Table matches latest audit.

## 7. Security measures

For each item, record **In place**, **Planned** or **Not applicable**. Do not describe a control as in place in public documents until it is ticked here.

* [ ] **Multi-factor authentication** on email, Discord, GitHub, Tebex, Render and other hosting, Namecheap, cloud storage and payment accounts.
  * *How to verify:* Screenshot of security settings for each account.
* [ ] **Password manager** used for all business credentials.
  * *How to verify:* Confirm all credentials are stored in it and not in plain text files or chat.
* [ ] **HTTPS** enforced on both domains and any hosted customer sites.
  * *How to verify:* Browser check; no mixed content.
* [ ] **Database access controls** — databases not publicly accessible; strong unique credentials; least-privilege users.
  * *How to verify:* Review of firewall / network rules and user permissions.
* [ ] **Encryption at rest** where providers support it.
  * *How to verify:* Provider documentation or settings recorded.
* [ ] **Secrets management** — tokens, API keys and passwords stored in environment variables or a secrets store, never committed to Git.
  * *How to verify:* Run a secret scan on repositories (GitHub secret scanning or equivalent); `.gitignore` covers `.env` and configuration files.
* [ ] **Discord bot token protection** — token stored securely and rotated if exposed.
  * *How to verify:* Token not present in any repository or shared file.
* [ ] **Updates** — servers, dependencies and devices patched regularly.
  * *How to verify:* Dependency alerts enabled; monthly update entry in log.
* [ ] **Monitoring** — logging of access and errors for hosted services.
  * *How to verify:* Logs available and reviewed after incidents.
* [ ] **Device security** — screen lock, disk encryption and up-to-date operating system on business devices.
  * *How to verify:* Device settings checked.
* [ ] **Secure file sharing** — customer files shared using access-controlled links, not public links.
  * *How to verify:* Review sharing settings on cloud storage.
* [ ] **Secure disposal** — data deleted from devices and storage before disposal or reuse.
  * *How to verify:* Disposal recorded.
* [ ] **Consider Cyber Essentials** certification. (Recommendation)
  * *How to verify:* Decision recorded. Do not claim certification unless obtained.

## 8. Secure credential management

* [ ] **Define the approved method for receiving customer credentials** (Before publication)
  * *What to do:* Choose a secure method (for example password manager sharing or a one-time secret link) and state it in section 6.1 of the privacy policy. \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Method documented; customers told in onboarding messages.
* [ ] **Ask for limited accounts** rather than owner credentials where platforms allow (txAdmin, hosting panels, databases, website CMS).
  * *How to verify:* Onboarding template includes the request.
* [ ] **Delete credentials at project completion** and remind customers to rotate them.
  * *How to verify:* Project close-out checklist includes credential deletion and a reminder message.
* [ ] **Never store credentials in Discord messages or ticket transcripts.**
  * *How to verify:* Periodic review of ticket transcripts; delete any credentials found.

## 9. Backup management

* [ ] **Document what is backed up**, where, how often and for how long.
  * *How to verify:* Backup register completed.
* [ ] **Encrypt backups** where possible.
  * *How to verify:* Provider settings recorded.
* [ ] **Test restoration** at least annually.
  * *How to verify:* Test result recorded.
* [ ] **Align backup retention with deletion commitments.**
  * *How to verify:* Backup period matches section 13 of the privacy policy.

## 10. Customer file management

* [ ] **Store customer files in one controlled location** per project.
  * *How to verify:* Folder structure documented.
* [ ] **Delete or archive files at project completion** according to the retention schedule.
  * *How to verify:* Close-out checklist entry.
* [ ] **Obtain written permission before portfolio use** of customer work or materials. \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Permission recorded per project.
* [ ] **Keep private GitHub repositories** for customer work.
  * *How to verify:* Repository visibility reviewed.

## 11. Employee and contractor access

* [ ] **List everyone with access to customer data or business systems.**
  * *How to verify:* Access list maintained.
* [ ] **Confidentiality agreements** for any staff, contractors or freelancers. \[IMPLEMENTATION REQUIRED — if applicable]
  * *How to verify:* Signed agreements saved.
* [ ] **Least-privilege access** — contractors get only what they need, on their own accounts.
  * *How to verify:* Account review.
* [ ] **Remove access promptly** when a person stops working with District Studio.
  * *How to verify:* Offboarding record.
* [ ] **Check whether any contractor is outside the UK** (international transfer).
  * *How to verify:* Recorded in section 14.

## 12. Third-party provider checks

For each provider, record purpose, data shared, role, location, transfer mechanism, DPA status, privacy policy link and status (active / not used).

| Provider                      | Active? | Purpose                 | Role                     | Location                 | DPA in place?        | Transfer mechanism | Privacy policy reviewed? |
| ----------------------------- | ------- | ----------------------- | ------------------------ | ------------------------ | -------------------- | ------------------ | ------------------------ |
| Discord                       | Yes     | Community, bot, support | Independent controller   | US                       | N/A (platform terms) | Discord's own      | \[ ]                     |
| Tebex                         | Yes     | Store                   | Independent controller   | \[REQUIRES CONFIRMATION] | N/A (creator terms)  | Tebex's own        | \[ ]                     |
| GitHub                        | \[ ]    | Source code             | Processor                | US                       | \[ ]                 | \[ ]               | \[ ]                     |
| GitBook                       | Yes     | Documentation           | \[REQUIRES CONFIRMATION] | \[REQUIRES CONFIRMATION] | \[ ]                 | \[ ]               | \[ ]                     |
| Render                        | \[ ]    | Hosting                 | Processor                | \[Region]                | \[ ]                 | \[ ]               | \[ ]                     |
| Namecheap                     | \[ ]    | Domains / DNS           | Processor / controller   | US                       | \[ ]                 | \[ ]               | \[ ]                     |
| WhatsApp Business             | \[ ]    | Communication           | Independent controller   | \[ ]                     | N/A                  | \[ ]               | \[ ]                     |
| Email provider                | \[ ]    | Email                   | Processor                | \[ ]                     | \[ ]                 | \[ ]               | \[ ]                     |
| VPS / dedicated hosting       | \[ ]    | Hosting                 | Processor                | \[ ]                     | \[ ]                 | \[ ]               | \[ ]                     |
| Database provider             | \[ ]    | Data storage            | Processor                | \[ ]                     | \[ ]                 | \[ ]               | \[ ]                     |
| Analytics                     | \[ ]    | Website analytics       | \[ ]                     | \[ ]                     | \[ ]                 | \[ ]               | \[ ]                     |
| Cloud storage                 | \[ ]    | Files and backups       | Processor                | \[ ]                     | \[ ]                 | \[ ]               | \[ ]                     |
| Payment providers (non-Tebex) | \[ ]    | Payments                | Independent controller   | \[ ]                     | N/A                  | \[ ]               | \[ ]                     |
| External APIs                 | \[ ]    | Integrations            | \[ ]                     | \[ ]                     | \[ ]                 | \[ ]               | \[ ]                     |
| Cfx.re (escrow)               | \[ ]    | FiveM delivery          | Independent controller   | \[ ]                     | N/A                  | \[ ]               | \[ ]                     |

* [ ] **Complete the table above** (Before publication)
  * *How to verify:* All cells completed; provider register in section 10.2 of the privacy policy updated to match.
* [ ] **Re-check providers annually** and when adding a new one.
  * *How to verify:* Review log entry.

## 13. Data Processing Agreements

* [ ] **Accept or download the DPA of every processor District Studio uses.**
  * *How to verify:* Copy or link saved for each provider in section 12.
* [ ] **Prepare a standard District Studio DPA** for customers. \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Template saved; referenced in section 14 of Data Processing & Customer Responsibilities (public space).
* [ ] **Incorporate processor terms into Terms of Service** so they are contractually binding. \[LEGAL REVIEW RECOMMENDED]
  * *How to verify:* Terms of Service reference the Data Processing & Customer Responsibilities document.
* [ ] **Offer a DPA** to customers whose hosted services contain end-user data.
  * *How to verify:* Signed DPAs filed.

## 14. International transfer checks

* [ ] **Identify each transfer outside the UK** (providers, contractors, APIs).
  * *How to verify:* Location column in section 12 completed.
* [ ] **Record the transfer mechanism** — UK adequacy regulations, UK Extension to the EU-US Data Privacy Framework (check the provider's certification on the DPF list), IDTA or UK Addendum.
  * *How to verify:* Mechanism recorded per provider.
* [ ] **Carry out transfer risk assessments** where relying on IDTA or Addendum, using the ICO's transfer risk assessment tool where helpful.
  * *How to verify:* Assessment saved.
* [ ] **Choose UK or EEA hosting regions** where practical. (Recommendation)
  * *How to verify:* Region settings recorded.

## 15. Tebex compliance checks

* [ ] **Review the current Tebex creator terms and** [**Tebex Privacy Policy**](https://www.tebex.io/privacy) to confirm Tebex's role as merchant of record and independent controller.
  * *How to verify:* Note of review date and conclusions.
* [ ] **Record what District Studio can see in the Tebex creator panel** (name, email, IP, country, username, custom fields).
  * *How to verify:* Screenshot (with personal data redacted) saved; section 7.3 of the privacy policy matches.
* [ ] **Document Tebex integrations** — webhooks, Discord role delivery, Cfx.re escrow, game server commands.
  * *How to verify:* Integration list saved; each storage location in the data inventory.
* [ ] **Minimise custom checkout fields** — collect only what is needed.
  * *How to verify:* Store configuration reviewed.
* [ ] **Link the District Studio privacy policy and terms from the Tebex store.**
  * *How to verify:* Screenshot.
* [ ] **Define how long Tebex-derived data is retained** in District Studio systems.
  * *How to verify:* Retention schedule entry.
* [ ] **Chargeback and refund evidence** — only share the minimum necessary with Tebex.
  * *How to verify:* Procedure note.
* [ ] **Confirm District Studio never receives card details.**
  * *How to verify:* Confirmed from Tebex panel and any other payment route.

## 16. Discord bot data handling

* [ ] **List every data field the bot stores**, with the database table and retention.
  * *How to verify:* Schema export annotated.
* [ ] **Record which gateway intents and permissions are enabled** and why.
  * *How to verify:* Developer Portal screenshot; justification documented.
* [ ] **Request only necessary OAuth2 scopes** for the dashboard (for example `identify` and `guilds`).
  * *How to verify:* OAuth2 URL reviewed.
* [ ] **Classify each feature as controller or processor.**
  * *How to verify:* Table in section 2.2 of Data Processing & Customer Responsibilities (public space) confirmed. \[LEGAL REVIEW RECOMMENDED]
* [ ] **Set the privacy policy URL** in the Discord Developer Portal.
  * *How to verify:* Screenshot.
* [ ] **Implement deletion on bot removal** (guild delete event) or a scheduled clean-up. \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Test removal from a test server; records deleted within the stated period.
* [ ] **Provide server owners with a way to export or delete their data.** \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Feature or documented request process.
* [ ] **Review automated moderation and application features** for solely automated significant decisions (UK GDPR Articles 22A–22D).
  * *How to verify:* Assessment recorded.
* [ ] **Ticket transcripts** — decide storage location, access and retention.
  * *How to verify:* Recorded in data inventory.
* [ ] **Comply with Discord's Developer Terms and Developer Policy.**
  * *How to verify:* Annual review entry.

## 17. Website data handling

* [ ] **Confirm what each website collects** (forms, accounts, logs, analytics).
  * *How to verify:* Data inventory entries.
* [ ] **Review contact form handling** — destination, provider, retention.
  * *How to verify:* Form provider recorded.
* [ ] **Check embedded third-party content** (fonts, scripts, widgets).
  * *How to verify:* Network requests reviewed during cookie audit.
* [ ] **Hosted customer websites** — list them, confirm DPAs and responsibilities.
  * *How to verify:* List and DPA status recorded.
* [ ] **Review log retention** on the hosting provider.
  * *How to verify:* Setting recorded.

## 18. Customer rights request procedure

* [ ] **Set up a rights request log** with: date received, requester, right, identity check, date of clarification request, deadline, extension (if any), actions taken, date completed. \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Log exists.
* [ ] **Follow the procedure:**
  1. Log the request on the day received.
  2. Verify identity proportionately (for example, reply from the linked email or Discord account).
  3. Clarify scope if needed — the deadline pauses while awaiting clarification.
  4. Search all systems in the data inventory with reasonable and proportionate effort: Tebex panel, Discord tickets, bot database, email, WhatsApp, storage, accounting.
  5. Apply any exemptions and redact third-party data.
  6. Respond within one month, or extend by up to two months for complex requests, telling the requester within the first month.
  7. Record the outcome.
  * *How to verify:* Log entries show deadlines met.
* [ ] **Processor requests** — pass to the relevant customer without undue delay.
  * *How to verify:* Log entry shows forwarding.

## 19. Complaints procedure

* [ ] **Set up a complaints log.** \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Log exists.
* [ ] **Acknowledge data protection complaints within 30 days**, investigate without undue delay, and inform the complainant of the outcome, as required following the Data (Use and Access) Act 2025.
  * *How to verify:* Log shows acknowledgement dates.
* [ ] **Include the ICO complaint route** in final responses.
  * *How to verify:* Response template includes ICO details.

## 20. Data breach procedure

* [ ] **Keep a breach log** for all breaches, reportable or not (Article 33(5)). \[IMPLEMENTATION REQUIRED]
  * *How to verify:* Log exists.
* [ ] **Follow the response steps:**
  1. **Identification** — record when and how District Studio became aware.
  2. **Investigation** — establish what happened and which data and people are affected.
  3. **Containment** — revoke tokens and credentials (including the Discord bot token), lock accounts, take systems offline, rotate secrets.
  4. **Risk assessment** — consider the type, sensitivity and volume of data and likely harm.
  5. **Customer notification** — where District Studio is a processor, notify customers without undue delay; where controller, notify individuals without undue delay if high risk.
  6. **ICO reporting** — within 72 hours of awareness where there is a risk to individuals, using the [ICO breach reporting service](https://ico.org.uk/for-organisations/report-a-breach/).
  7. **Remediation** — fix the cause.
  8. **Record keeping** — complete the breach log.
  * *How to verify:* Run a short tabletop exercise annually; record it in the review log.
* [ ] **Keep an emergency contact list** — hosting providers, Discord developer support, Tebex support, domain registrar.
  * *How to verify:* List saved.

## 21. Marketing compliance

* [ ] **Confirm whether any electronic marketing is sent.**
  * *How to verify:* Recorded.
* [ ] **Record consent or soft opt-in basis** for each marketing contact.
  * *How to verify:* Mailing list records.
* [ ] **Include an opt-out in every marketing message** and honour it promptly.
  * *How to verify:* Template check.
* [ ] **Maintain a suppression list.**
  * *How to verify:* List exists.
* [ ] **No unsolicited promotional DMs via the bot.**
  * *How to verify:* Code review.

## 22. Children's data

* [ ] **Decide a minimum age policy** for purchases, commissions, accounts and bot use. \[LEGAL REVIEW RECOMMENDED]
  * *How to verify:* Decision recorded and reflected in Terms of Service and section 16 of the privacy policy.
* [ ] **Assess whether the Children's Code applies** to the bot, dashboard and websites.
  * *How to verify:* Assessment saved.
* [ ] **Procedure for deleting information that should not have been collected.**
  * *How to verify:* Procedure documented; requests logged.

## 23. Review log

| Date                     | Reviewer                 | Sections reviewed | Changes made              | Next review              |
| ------------------------ | ------------------------ | ----------------- | ------------------------- | ------------------------ |
| \[REQUIRES CONFIRMATION] | \[REQUIRES CONFIRMATION] | All               | Initial checklist created | \[REQUIRES CONFIRMATION] |


---

# 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/ongoing-compliance/internal-privacy-compliance.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.
