Safeguarding & Child Protection Policy
1. What this policy is
Dance competitions and festivals are full of children. This policy explains how the HubHero platform supports safeguarding, what everyone using it is responsible for, and what happens when a concern is raised. It forms part of our Terms of Service and our Acceptable Use Policy.
It does not replace your own safeguarding policy. Organisers and schools must have their own policy, their own training and their own named people. This describes what our software does to support that.
2. What we are, and what we are not
We are a software provider. We do not run events, supervise children, employ chaperones or carry out DBS checks. Those duties sit with the organiser and the schools, and nothing here moves them onto us.
What the platform does:
- records chaperone and DBS status, so an organiser can see at a glance who is cleared and who is not;
- lets an organiser name a welfare or safeguarding officer for an event;
- captures guardian consent for performers under 18, including consent for photography, video and audio;
- handles age bands and age groups, so children compete against their own age;
- restricts medical and welfare notes to the people who need them;
- keeps an audit log of safeguarding-related actions, so it can be shown later who did what and when.
3. What organisers must do
- Have a written safeguarding and child protection policy, and a named safeguarding lead present at the event.
- Set chaperone ratios and DBS requirements for your event, record them in the platform, and enforce them at the door.
- Check that consent is in place before any photography, video or audio — see the IP & Media Licence.
- Control access backstage and to changing areas.
- Hold the child performance licences and local authority approvals your event needs.
- Act on a concern promptly, and report it to the police or the local authority designated officer where the law or good practice requires.
4. What schools and studios must do
- Look after the welfare of the performers you enter, for the whole time they are at the event.
- Provide accurate guardian, emergency, medical and consent information, and keep it up to date.
- Meet the organiser's chaperone, DBS and safeguarding requirements.
- Never enter a child, or allow their image to be captured, without the consent required.
- Tell the organiser immediately if a child in your care is missing, hurt or at risk.
5. Chaperones and DBS
Chaperone records held in the platform include the person's name, contact details and DBS certificate reference and status. The organiser is responsible for verifying a DBS certificate — the platform records what it is told, it does not check it. A record in the platform is not evidence that a check was done.
DBS and child performance licence evidence is kept after the event, and survives a request for erasure, because safeguarding and licensing obligations require it. What is kept is described in our Privacy Policy.
6. Children's data
Data about children is handled as set out in our Privacy Policy and, where we hold it for you, our Data Processing Agreement. In short: guardian consent is required for the data of performers under 18 and for any photography, video or audio of them; medical and welfare notes are restricted; and children's data is never used for marketing or profiling.
7. Raising a concern
If a child is at immediate risk of harm, contact the police on 999, or your local authority's safeguarding team. Do not wait for a reply from us or from anyone else.
For anything else:
- Tell the event organiser's safeguarding lead — they are the people at the venue and they can act now.
- Tell us at hello@hubhero.io if the concern involves the platform: an image that should not be there, an account behaving badly, or data someone should not be able to see.
Tell us what happened, when, which event, and which people or accounts are involved. Send it from an address we can reply to.
8. What we do when a concern reaches us
- We acknowledge it and give it to a named person here.
- We contain it first. Where a child may be at risk we restrict or remove the content, or suspend the account, before we investigate — we do not wait to be sure.
- We tell the organiser's safeguarding lead, unless doing so would itself put a child at risk.
- We preserve the record — the audit log, the media and the account history — so the people who have to investigate can.
- We cooperate with the police, the local authority and any regulator, and we give them what the law entitles them to.
- We tell you what we did, unless we are told not to by an authority.
Where a concern also involves personal data — data seen by someone who should not have seen it — we handle it as a possible personal data breach as well, under our Data Processing Agreement and Privacy Policy. That means the ICO within 72 hours where the law requires it.
9. Review
We review this policy as good practice and the law develop, and whenever an incident tells us it needs to change. The current version is always the one on this page, dated at the top.
10. Contact
Safeguarding concerns about the platform: hello@hubhero.io. Data protection: privacy@hubhero.io.