Why Safeguarding Matters: Protecting Young Musicians

Built In, Not Bolted On

When I started planning James Music Academy, I knew many of the people wanting to learn would be teenagers. According to Ofcom's research, 97% of UK children aged 12-15 go online, with many seeking educational content.

That's a responsibility I take seriously. Safeguarding wasn't something we added later to tick a compliance box — it was part of v1.0 from the very first day. In fact, 17 of our 53 initial requirements were specifically about safeguarding and parental involvement.

Understanding UK Requirements

The UK has comprehensive child protection regulations for online services. Two key frameworks guide our approach:

The ICO Age Appropriate Design Code

The ICO Children's Code sets out 15 standards for online services likely to be accessed by children:

• Best interests of the child — Primary consideration in all decisions
• Age-appropriate application — Different protections for different ages
• Transparency — Privacy information in language children understand
• Parental controls — Tools for parents to manage their child's experience
• Data minimisation — Only collect data that's genuinely needed

DBS Requirements

The Disclosure and Barring Service provides criminal record checks for people working with vulnerable groups. For one-to-one work with under-18s, an Enhanced DBS check is required. Every mentor on James Music Academy holds one. No exceptions.

How We Built It

Age Verification at Registration

When someone under 18 signs up, the entire flow changes:

• We require a parent or guardian's email address
• The account is created but marked as "pending consent"
• The parent receives a verification email with clear information
• The student cannot book sessions or access full features until consent is given

This aligns with GDPR Article 8 on children's consent and data processing.

Parents as Partners

Parents aren't just gatekeepers — they can be active participants. Research from the Education Endowment Foundation shows that parental engagement adds an average of +4 months educational progress.

When a parent creates their own account, they get their own dashboard:

• All upcoming and past sessions
• Their child's goals and progress
• Ability to comment on goals and add encouragement
• Calendar feeds so they always know what's scheduled

We even built a flexible relationship model — multiple parents can be linked to one student, and a parent can have multiple children on the platform. Real families are complicated, and our database schema reflects that.

Immutable Consent Records

Under UK law, consent records need to be retained. Our system keeps:

• Timestamp of consent
• What information was presented
• The parent's verified identity
• IP address and device information

These records are immutable — they can't be modified after creation — and retained for 7 years as recommended by ICO guidance.

Visible DBS Status

Every mentor's DBS status is displayed prominently — in the site footer, on mentor profiles, and on booking pages. Parents shouldn't have to dig around for this information.

The Technical Foundation

Building safeguarding properly required specific data architecture decisions:

• ParentStudent junction table — Supports multiple parents per student and vice versa
• ConsentRecord model — Immutable audit trail with snapshot of consented terms
• User age calculation — Dynamic, recalculated from date of birth
• Blocked account states — Under-18 accounts locked until parental approval

These weren't afterthoughts. They were part of the v1.0 database schema from the start.

Why This Matters to Me

When I was learning music as a teenager, I had mentors who looked out for me. People who gave their time because they believed in what I could become. That shaped who I am today.

I want to create that same environment for the next generation — but in a way that's appropriate for online learning. That means building trust through transparency, involving families, and taking safety as seriously as the music itself.

This approach is part of how we're building the platform from the ground up with the right foundations.