A school rowing crew on the water, deliberately pixelated so no individual is identifiable

Student image policy for schools in 2026: three problems, not one.

Breaking image policy down into three smaller, manageable jobs.

Why it feels like one big problem

What looks like one big scary problem student image policy in the age of AI is really three more manageable problems.

Problem one

Where images live.

This is the infrastructure problem. Whose phone took the photo, and where does it sync? Where are the photos stored, and who can open that folder? Are they filed so you could find one particular child? When someone pulls a photo out, is there a record?

This problem is the responsibility of ICT. Thankfully, it’s more black and white, because best practice and policy guidelines typically exist (depending on your particular jurisdiction).

Here’s one test. If a family withdrew consent today, could you find every photo of their child by Friday?

The Australian eSafety Commissioner’s July 2026 advisory poses three specific questions about this problem: whether original images are “stored securely and handled in line with school or sector policies for data retention and disposal”, who “may post, approve and moderate content”, and whether “archived pages or past posts still need to remain public”.[2]

What OurNews does here

Every photo you publish through OurNews is filed to the story it belongs to, so a takedown finds it and it comes off the live system straight away. That answers the Friday test for what you publish through us.

Problem two

How images get misused.

This is a behavioural problem, which means it’s a little more grey. We think about this as risk reduction, not risk elimination. eSafety agrees: “Posting fewer images of school students and personnel – or none at all – can reduce the risk. It cannot remove the risk completely because images may still be available from other public sources.”[2]

It’s tempting to imagine this kind of threat as a shadowy figure in a basement; but we know that isn’t the reality most of the time. The eSafety advisory describes an overseas case where criminals took student photos from a school website to build an extortion attempt.[2] But the same advisory says who is usually behind the anonymous accounts it gets reports about: “Those running the accounts are often believed to be current or former students from the targeted school. People outside the school community may also misuse images.”[2]

In the Australian deepfake cases that reached the news in 2024, Bacchus Marsh Grammar and Salesian College, the person responsible was a student of the school.[6][7]

So the question isn’t only how to keep strangers out. It’s also what makes misuse harder for someone who already has a way in.

Three questions to help you wrestle with this problem:

What level of risk is acceptable to us on the different platforms that we communicate via? What have we done to reduce it? And how do we explain that to parents, staff and students?

What OurNews does here

OurNews has spent a lot of time designing solutions to this problem. Every story has two settings that help give schools control over who finds it and who reads it. Our deterrence layers are built to reduce risk for the at-scale attacks as well as the opportunistic misuser.

Problem three

Who said yes, to what, and when.

This problem is all about consent. We think about consent being given by both parents/carers AND students. Queensland’s state school consent procedure already asks the student to sign too, where they are old enough to give and understand the consent.[5]

Consent has to be specific. Your different channels/surfaces each should have specific consent based on their inherent risks and exposures. Think social media, vs website, vs a prospectus, vs an internal LMS. The eSafety advisory asks “Is consent active, informed and current? Does it cover school social media posts?”[2] Moores, a law firm that advises schools, has written that opt-out boxes “often lead to unwitting, and ultimately invalid expressions of consent”, and that a set-and-forget consent gathered at enrolment years ago isn’t current.[3] The draft Children’s Online Privacy Code, if it is legislated, would cap how long a consent stays ‘live’ at 12 months.[4]

The Australian eSafety Commissioner’s provocations.

The advisory lists nine things to consider before posting.[2] Here they are, mapped to our three problems:

Where images live

storage, governance, old material

How images get misused

purpose, identification, audience, alternatives, settings

Who said yes

consent

Student image policy: the three jobs.

Where our images live

Where photos are taken, stored and filed. Who can retrieve them. How fast we can find every photo of one child.

How we reduce misuse

Which images go public and which don’t. Who can see what we share. What we’ve done to deter misuse. How we explain it to families.

Who said yes

What consent covers, channel by channel. How students have a say. How often it’s renewed. How a family changes their mind.

Sources

  1. eSafety Commissioner, “School photo posts vulnerable to emerging AI threat”, media release, 28 July 2026.
  2. eSafety Commissioner, Online Safety Advisory, “Sharing school imagery in the age of AI: risks, deepfakes, and how to protect students and staff”, 28 July 2026.
  3. Moores, “Schools: do you actually have consent to publish student photographs?”, 8 November 2024.
  4. Office of the Australian Information Commissioner, official exposure draft of the Children’s Online Privacy Code, 2026.
  5. Queensland Department of Education, “Obtaining and managing student and individual consent” procedure.
  6. CNN, “Australian boy arrested over deepfakes of schoolgirls”, 13 June 2024.
  7. SBS News, “Parent reacts after 50 girls targeted in AI explicit photo scandal at Melbourne school”, June 2024.
  8. OurNews, “What the eSafety Commissioner said about school photos and AI in 2026”.

Introducing OurNews

Share your school’s stories while managing privacy and eSafety risk with OurNews

OurNews is a school storytelling platform: a space your school controls, where you publish your stories to the people who care about them. Everything you publish stays yours.

Teachers contribute in a couple of taps. The platform handles the layout and design. Families get a newsletter that works on a phone.

We don’t plug into your student information system, on purpose: no student database to leak, and Grandma still gets to stay up to date with her grandkids.