Safeguarding in school esports works best when it's woven into everyday participation. When schools approve who plays, match communication happens where adults can see it, and students know where to go for help, organisers have a better chance of picking up problems early. Privacy belongs in the same conversation. Student information needs particular care, so what a platform asks them for, and who can see it, is a safeguarding decision too.

Why is prevention the first pillar of school esports safeguarding?

Prevention starts with a competition where adults are present and expectations are clear from the first message. On School Esports, which we built independently drawing on national federation expertise, student-created teams need teacher approval in teacher-validated events, and teachers can see their teams' match chats. That's deliberate. My aim is to encourage better behaviour by making adult oversight clear from the outset and creating spaces that support a strong safeguarding culture.

A teacher being able to read a chat helps with oversight, but it doesn't guarantee how anyone behaves or mean every message is read as it arrives. It helps set the tone early and gives adults something to work with if a concern comes up.

Prevention also starts before anyone registers. School esports is still a young space, so it's worth asking a few questions about the people behind a competition. A good answer will depend on where you are and what your school requires.

  • Who runs the competition, and who is accountable for it?
  • What evidence can they show that student data is protected?
  • Which publisher permissions or licences cover the games being played?
  • What safeguarding policies cover adults who interact with students, and are those adults police vetted or checked in a similar way?
  • If your country has a national esports federation, is the competition sanctioned by it? And which local or federation safeguarding guidance does the operator follow?

How should students report concerns in school esports?

If you're running a league, give students a private way to raise a concern and tell them who will review it. Speaking up shouldn't become a public argument between two teams. Ask for evidence that helps someone understand what happened, leaving out unrelated private details.

Teachers matter most here. They connect the online competition with the student's school environment, so follow-up can carry on after the match room closes. On School Esports, teachers have read-only access to their teams' chats, and authorised administrators or referees can join a chat room when needed. My aim with the moderation and reporting tools we built into the platform is for teachers to hear about poor behaviour and follow it up in real life. The School Esports demo conduct and chat guide describes staff reviewing competition reports and asks students to tell their teacher about school or wellbeing concerns as well.

Those are different responsibilities. Competition staff review what happened in the match, and authorised competition administrators make decisions about event sanctions under the competition's rules. Teachers and schools make decisions about school discipline and the wider safeguarding response. A report or alert is a starting point. On its own, it doesn't impose a penalty, change a result or resolve the concern, and it can't guarantee that every adult sees it or responds. Be clear about who reviews a report, when a teacher is brought in, and when a concern needs to go through the school's own safeguarding process. The platform's tools support that work, while teachers, schools and organisers remain responsible for student safety.

What student information should a school esports platform show?

Only what the match needs. Opponents need enough information to identify the right players, but they don't need students' emails or surnames. The School Esports demo privacy notice says standard opponent-facing roster views don't display student email addresses or last names.

Whatever platform you're considering, check which student details it asks for and why each field is needed. Each extra field gives the league another piece of information to protect.

Can students under 13 take part in school esports?

It depends on the competition and the services students need to use. Before you register younger students, check the age rules for the tournament platform and the game. Ask whether the rules cover student accounts, teacher-managed roster records, or both, and what permissions your school needs. Don't assume school or parental permission overrides a service's age restrictions. For School Esports, confirm the current age rules for your competition and registration route before entering younger students' details.

When comparing platforms, ask what student information is collected, who can see it, where it's processed and stored, and how long it's kept. Check how security, deletion requests and any required permissions are handled. The New Zealand Privacy Commissioner's guidance on digital technologies in education offers a useful due diligence checklist. Involve your school's privacy lead in the decision and check the requirements that apply where your school operates. If the provider's policies don't give you a clear answer, sort that out before registration.

What happens to student data after the season ends?

Privacy doesn't stop when the season does. Retention, evidence handling and deletion requests remain part of running a league, alongside the day-to-day work of keeping matches safe. Base your retention plan on why each record is needed, rather than assuming everything is deleted at the end of the season. In New Zealand, information shouldn't be kept longer than its lawful purpose requires.

The privacy policy on the main School Esports site says match chat messages and images are kept for a limited period after the match, then deleted automatically. It doesn't specify that period. For reported misconduct, a snapshot of the chat may be kept for review, safeguarding, moderation or compliance. That snapshot is evidence about a student and needs the same care as any other safeguarding record. Results and standings may also be kept to preserve competition integrity.

The School Esports demo site publishes a separate privacy notice with more detailed retention periods for chat and conduct records, distinguishing deletion from removal of identifying details. Published notices can differ, so check which participant notice and retention schedule apply to your competition before registration.

The School Esports privacy policy names the league's organisation partner as the primary agency responsible for competition information. Requests about a student's information can go to that partner or to info@schoolesports.org. If you run a league, someone in your organisation needs to own those requests and know how long evidence from reported incidents is kept. A deletion request needs to be assessed alongside any lawful reason to retain records.