← All legal documents

Data Processing Agreement

Organisers and schools (data controllers) · Last updated 2026-09-09

1. What this agreement is

This Data Processing Agreement ("DPA") is the Article 28 contract between you and HubHero Ltd, company number 17027106, registered in England and Wales. It applies whenever we process personal data on your behalf.

It forms part of our Terms of Service. If you are an organiser it also forms part of your Organiser Agreement; if you are a school, of the School & Studio Terms.

In this DPA you are the controller and HubHero is the processor. Personal data, processing, data subject, controller, processor and personal data breach have the meanings given in the UK GDPR and the Data Protection Act 2018.

2. What we are the processor for, and what we are not

You decide what personal data goes into the platform and why. Performers, pupils, guardians, chaperones, judges, entries, results, consents and media are your data. We process them only for you.

We are a controller in our own right for a narrow set of data — your account, your billing, our support conversations with you, and our own marketing. That data is governed by our Privacy Policy, not by this DPA. The two documents describe different data and must never be read as contradicting each other.

3. The details of the processing

  • Subject matter — providing the Services to you.
  • Duration — for as long as you use the Services, plus any retention period we have agreed or the law requires.
  • Nature and purpose — hosting, storing, organising, displaying and transmitting personal data so we can deliver competition management, studio operations, ticketing, communications, media handling and related features.
  • Types of personal data — names and contact details; performer and pupil details including date of birth and age group; guardian details for under-18s; safeguarding, chaperone and DBS information; medical, dietary or accessibility notes where you choose to collect them; photographs, video and audio; payment and order information; messages sent through the platform.
  • Categories of data subject — organisers, schools and studios and their staff, performers and dancers including children, parents and guardians, judges, chaperones, ticket buyers and other attendees.

Special category data (health and medical notes) and data about children are both in scope. Section 9 says what that means in practice.

4. Your obligations as controller

You must:

  • have a lawful basis for everything you put into the platform, and where you rely on consent, obtain it properly and be able to evidence it;
  • give your performers, pupils, parents and staff the privacy information the law requires you to give them;
  • make sure your instructions to us are lawful;
  • keep the data you enter accurate, and correct it when you are told it is wrong;
  • deal with data subject rights requests that concern your data — we help, but the decision is yours.

5. Our obligations as processor

We will:

  • process personal data only on your documented instructions — this DPA, your use of the Services' features, and anything else you tell us in writing — unless the law requires otherwise, in which case we tell you first unless the law forbids it;
  • tell you if, in our opinion, an instruction breaches UK data protection law;
  • make sure everyone we authorise to process the data is under a duty of confidentiality;
  • put appropriate technical and organisational security measures in place (section 7);
  • engage sub-processors only on the terms in section 6;
  • help you answer data subject requests — access, rectification, erasure, restriction, portability and objection — taking into account the nature of the processing and the tools available in the platform;
  • help you with security, breach notification, data protection impact assessments and consultation with the ICO, taking into account what we know;
  • at your choice, delete or return the personal data at the end of the Services, except where the law requires us to keep it;
  • make available the information you need to demonstrate compliance with Article 28, and allow for and contribute to audits, on reasonable notice, at reasonable frequency and subject to confidentiality.

6. Sub-processors

You give us general authorisation to use sub-processors to run the Services — our hosting, database, authentication, email, payment and media processing providers. The current list, what each one does and where it holds data, is in our Privacy Policy. That list is the single source of truth; it is not repeated here so the two cannot disagree.

Each sub-processor is bound by data protection obligations no less protective than this DPA, and we remain responsible to you for what they do. We will tell you before we add or replace one, and you may object on reasonable data protection grounds. If we cannot resolve your objection, you may stop using the affected part of the Services.

7. Security

We protect your data with:

  • encryption in transit and at rest;
  • row-level security in the database, so each tenant's data is isolated;
  • role-based access, so a person sees only what their role needs;
  • least-privilege administrative access, with audit logging of sensitive actions — safeguarding, scoring and financial actions are auditable inside the platform;
  • authentication and session management through our identity provider.

We review these measures as the Services change. We may improve them, and we will not reduce the overall level of protection.

8. Personal data breaches

If we become aware of a personal data breach affecting your data, we tell you without undue delay, and in any event within 72 hours of becoming aware. We give you what you need to meet your own duty to notify the ICO and, where required, the people affected: what happened, which categories and roughly how many records, the likely consequences and what we are doing about it.

We do not notify the ICO or your data subjects on your behalf unless you ask us to in writing — that is a controller decision and it is yours.

Report a suspected breach to privacy@hubhero.io immediately.

9. Children and special category data

The platform exists to run children's dance competitions, so children's data is not an edge case here.

  • Data about performers and pupils under 18 is processed on your instructions and never used by us for marketing, profiling or any commercial purpose of our own.
  • Medical, welfare and accessibility notes are special category data. You are responsible for the explicit consent or other Article 9 condition that allows them to be collected. We store them with restricted access.
  • Consent, chaperone and DBS records are handled as set out in the Safeguarding & Child Protection Policy.
  • Photographs, video and audio of children are handled as set out in the IP & Media Licence.

10. International transfers

Our infrastructure is in the UK, the European Union and the United States. Where personal data leaves the UK, we rely on an appropriate safeguard under Chapter V of the UK GDPR — adequacy regulations, or standard contractual clauses with the UK International Data Transfer Addendum. Ask us and we will tell you which safeguard covers a particular provider.

11. Deletion and return

When you stop using the Services, tell us whether you want your personal data deleted or returned. We will do it within a reasonable period. We keep only what the law requires us to keep — for example financial records, and the safeguarding evidence described in our Privacy Policy — and we keep that no longer than necessary.

Retention periods that apply while you are using the Services are listed in the Privacy Policy.

12. Liability

Liability under this DPA is subject to the limits in our Terms of Service. Nothing in this DPA limits either party's liability where the law does not allow it to be limited.

13. Contact

Data protection questions, audit requests and breach reports: privacy@hubhero.io. Our ICO registration number is ZC108539.