Under POPIA, a learner’s name, photograph, class, results and contact details are personal information of a child, and processing it is prohibited unless one of the specific grounds in section 35 applies. For a school or crèche website, the most important of those grounds is the prior consent of a competent person, usually a parent or guardian. Enrolment records and the information a school needs to run itself are generally covered by other grounds, but publishing learner photos, names and achievements on a public website needs parental consent, and the website itself needs to collect and store children’s information carefully.
School websites are among the most information-rich websites in any community. They carry photo galleries of sports days and prize-givings, news pages naming learners, online enrolment forms that collect identity numbers and medical details, and parent portals full of contact information. Many were built by a parent volunteer or a small supplier years ago, before POPIA came into force, and many have never been reviewed since. This guide sets out what the law requires and what a properly built school website looks like. It is practical guidance from a web agency, not legal advice; a school with a specific concern should consult an attorney with data protection expertise.
What POPIA Says About Children
POPIA treats children’s information as a separate category, distinct from special personal information, with its own prohibition. Section 34 says a responsible party may not process personal information concerning a child, and section 35 sets out the exceptions. A child is defined as a natural person under 18 who is not legally competent to take action or make decisions about themselves without the assistance of a competent person. A competent person is anyone legally competent to consent on the child’s behalf, typically a parent or legal guardian.
Section 35 allows processing where it is:
- carried out with the prior consent of a competent person;
- necessary for the establishment, exercise or defence of a right or obligation in law;
- necessary to comply with an obligation of international public law;
- for historical, statistical or research purposes, where the purpose serves a public interest and the processing is necessary for it, or obtaining consent is impossible or would involve a disproportionate effort, and sufficient guarantees protect the child’s privacy; or
- of information deliberately made public by the child with the consent of a competent person.
The Information Regulator can also authorise processing on application, where it is in the public interest and appropriate safeguards are in place, and in 2021 it published a guidance note on applying for that authorisation. The practical effect for schools is a division between information the school needs to function, which is usually covered by the ‘right or obligation in law’ ground (including a school’s statutory and contractual duties), and information the school chooses to publish or use for promotion, which needs consent.
Where Children’s Information Appears on a School Website
It is worth listing the places, because most schools underestimate how many there are.
| Website feature | Information involved | Usual basis |
|---|---|---|
| Homepage and marketing photos | Learners’ images, often identifiable | Parental consent |
| Event and sports galleries | Images, sometimes with names, teams and dates | Parental consent |
| News, results and achievements | Names, grades, results, awards | Parental consent |
| Online enrolment and application forms | Names, ID numbers, addresses, medical and family details | Needed to enrol; secure handling required |
| Parent portals and newsletters | Learner and parent contact details, class lists | Running the school; access control required |
| Livestreams and video | Images and voices of learners | Parental consent |
| Staff pages | Adults, not children, but still personal information | Staff consent or legitimate basis |
Photos and Galleries: Getting Consent Right
Photos are where most school websites carry the most risk and where the fix is most straightforward.
Collect consent properly, once a year
Consent must be given by a competent person before publication. The workable approach is a media consent section in the annual registration or re-registration pack, with separate choices rather than a single tick: photos on the school website, photos on social media, photos in printed publications, and whether names may appear with photos. Parents can agree to some and not others, and many will happily allow group photos without names while declining named individual photos.
Keep a register and make it usable
Consent is only useful if the person uploading photos knows who has declined. Schools that manage this well keep a simple, current list of learners whose photos may not be published, available to whoever manages the website and social media. Without it, consent forms are filed and forgotten while photos go up every Friday.
Publish less identifying detail
Even with consent, there is little reason to pair a full name, a grade and a clear face in a public gallery. First names only, team photos without captions, and avoiding images that identify a learner’s home or regular whereabouts reduce risk without losing the warmth that makes a school website appealing. Location data embedded in photos taken on phones should be stripped before or on upload; an image optimisation plugin configured to strip metadata from the original file can do this automatically, whereas WordPress on its own keeps it in the original upload.
Consider what genuinely needs to be public
Galleries exist mostly for current parents, not for prospective ones. Moving event galleries behind a parent login keeps them available to the community they are meant for, while the public website uses a smaller set of carefully chosen images with consent on file. This one structural decision removes most of the exposure.
Realistic expectation: consent can be withdrawn. When a parent withdraws it, photos of their child need to come down from the website within a reasonable time, which means someone needs to know where they were published.
Online Enrolment and Application Forms
Enrolment forms collect some of the most sensitive information a school holds: identity numbers, home addresses, custody arrangements, medical conditions, allergies, and sometimes financial details for fee assistance. Collecting this is necessary, and the obligations are about how it is done.
Collect only what is needed at each stage. An application form does not need a child’s medical history; an acceptance pack might. Asking for everything up front means storing sensitive information for families who never enrol.
Know where submissions go. Many school website forms simply email submissions to a general inbox, where they sit indefinitely, are forwarded around, and are exposed if the mailbox is compromised. A better setup stores submissions securely in the website or a dedicated system, sends staff a notification rather than the full contents, and limits who can see them.
Watch third-party tools. Free online form builders, survey tools and spreadsheets often store data on servers outside South Africa. POPIA has rules on transferring personal information across borders, and transferring children’s information to a third party in a country without adequate protection can require prior authorisation from the Regulator. Choosing tools with a clear data location, or keeping forms on the school’s own website, avoids the question.
Delete what you no longer need. Applications from families who did not enrol, and records past their retention period, should be deleted on a schedule. Information that no longer exists cannot leak.
Newsletters, Parent Communication and Fundraising
Communicating with parents about school matters, such as calendars, closures, reports and events, is part of running the school and is generally not direct marketing, because it neither promotes goods or services nor requests donations. Using parent contact details to request donations or promote fundraising products, sponsor offers or third-party services is a different matter, and electronic direct marketing rules apply. Keep the two separate, give parents a clear way to opt out of anything promotional, and never pass parent lists to sponsors or suppliers without consent.
Security Is Part of Compliance
POPIA requires appropriate, reasonable technical and organisational measures to protect personal information. For a school website that means the basics done consistently: WordPress, themes and plugins kept updated, strong unique passwords and two-factor authentication for every administrator, old volunteer and staff accounts removed, backups taken and tested, and HTTPS enforced on every page. A school website that has not been updated in a year is not just a technical problem; it is a compliance problem waiting to become a breach notification.
Schools should also have an identified, registered Information Officer (public schools should confirm the position with their provincial education department), a privacy policy that explains what the website collects and why, and a contact for parents who want to see or correct the information held about their child.
A Practical Checklist for Schools and Crèches
- Add a granular media consent section to the annual registration pack, covering website, social media, print and naming.
- Keep a current do-not-publish list available to whoever manages the website and social media.
- Review existing galleries and news posts, and remove images and names where consent is not on file.
- Move event galleries behind a parent login and keep the public website to selected, consented images.
- Strip location data from photos before or on upload and avoid pairing full names with identifiable photos.
- Review every form: what it collects, where submissions go, who can see them and how long they are kept.
- Check where third-party form, survey and mailing tools store data.
- Separate school communication from fundraising and sponsor promotion, with an opt-out for the latter.
- Put the website on a maintenance schedule with updates, backups and account reviews.
- Publish a clear privacy policy and confirm who the school’s Information Officer is and that they are registered with the Regulator (public schools should check the position with their provincial education department).
Summary
- POPIA prohibits processing children’s information unless a section 35 ground applies, most often the prior consent of a parent or guardian.
- Information needed to enrol and educate learners is usually covered by the school’s statutory and contractual rights and obligations; publishing photos, names and achievements needs consent.
- Granular annual consent, a usable do-not-publish list and parent-only galleries solve most photo risk.
- Enrolment forms should collect only what is needed, store submissions securely and avoid unvetted offshore tools.
- Keeping the website updated and secure is part of meeting POPIA’s security safeguards.
A school website exists to show a community at its best, and that community includes the children in the photos. Built with consent and care, it can do that without putting any of them at risk.
Frequently Asked Questions
Can a school post learner photos on its website under POPIA?
Yes, with the prior consent of a competent person, usually a parent or guardian. Consent should be specific to the website and to whether names appear with photos, and the school must remove images if consent is withdrawn.
Who can consent on behalf of a child under POPIA?
A competent person, meaning someone legally competent to consent on the child’s behalf. In practice this is a parent or legal guardian. In general, a learner’s own agreement is not a substitute while they are under 18.
Does a school need consent to process enrolment information?
Information the school needs to enrol and educate a learner is usually covered by the ‘right or obligation in law’ ground, which includes a school’s statutory and contractual duties, rather than consent. It still has to be collected for a defined purpose, stored securely and kept no longer than necessary.
Are group photos without names allowed?
Group photos are still images of identifiable children, so the safest approach is to cover them in the consent form as well. Many parents who decline named individual photos are comfortable with uncaptioned group photos, which is why granular consent works well.
Can we use free online forms for school applications?
You can, but check where the provider stores the data. Transferring children’s information to a third party in a country without adequate data protection can require prior authorisation from the Information Regulator. Keeping forms on the school’s own website avoids the issue.
Do crèches and aftercare centres have to comply too?
Yes. POPIA applies to any responsible party processing children’s information, regardless of size. Crèches, aftercare centres, sports clubs and tutoring businesses face the same rules on consent, security and publication.
A School Website Built With Care
We build and maintain websites for organisations that handle sensitive information, with secure forms, parent-only areas and consent-aware galleries designed in from the start.
Explore our website development services, or reach out through our contact page.






