A plain-English guide to Student Information System (SIS) data, app permissions, and what Wonde can and can’t do with either.
Someone at your school has probably asked it or thought about it, but not asked. ‘If Wonde sits between our SIS and every app we use, what actually stops our data from ending up somewhere we never agreed to?’
It’s a fair question. It’s also one of the most poorly answered, usually with a wall of certification logos and no explanation of how the thing works. So here’s the plain version, written for the person who has to sign off the risk register rather than the person who reads the API docs.
Why does this question come up?
Data-sharing agreements have gotten harder in the last few years, and rightly so. In Australia, the Privacy Act 1988 and the Australian Privacy Principles put the obligation on your school, rather than on your suppliers.
Across Australia and New Zealand, Safer Technologies 4 Schools (ST4S) has given jurisdictions a shared way to assess what a product does with student information before it goes anywhere near a classroom.
Meanwhile, the number of apps in an average school has quietly climbed. Everyone wants a roster. Some want photos. A few want parent contact details, and it isn’t always obvious why.
So when a single service connects to your SIS and feeds all of them, the natural instinct is to ask who’s holding the keys. Keep asking. Any supplier who treats that as an inconvenience is telling you something.
What actually happens to your data
Three steps, and none of them are hidden.
Your SIS holds the record. It always has. Wonde doesn’t replace it, migrate it, or become the master copy. Your SIS stays the source of truth.
Wonde reads from your SIS, on your instruction. We’re a data processor. Your school is the data controller. In practice, that means we can only do what you’ve told us to do, and you can tell us to stop.
Approved apps read from Wonde. This is the part that matters most. An app connected through Wonde receives nothing until someone at your school approves it, and the approval is specific. Not “access to student data”, but which fields, for which students, for that app.
An app asking for something you’re not comfortable handing over is a decision you get to make before any data moves, rather than a discovery you make afterward.
What you can see and change, at any time
Knowing the theory is one thing. Being able to check it at 4 pm on a Tuesday when a parent has asked a pointed question is another. Four tools in Wonde Premium exist for exactly that.
- Dynamic access controls | Filter what an app receives by class, campus, or year group. A wellbeing app used only in the senior school doesn’t need the whole roll.
- Data Explorer | See the actual data being provisioned to each app, as it stands right now. No ticket, no waiting, no taking our word for it.
- Data protection request tool | Start from a single student and see every app their data has reached. What used to be a week of emails becomes a screen.
- Activity and device log | Who did what in your portal, and when. Useful for audits, and more useful the day something looks odd.
None of this requires a phone call to us. That’s deliberate. The control you have to request isn’t really control.
Who checks our homework?
You shouldn’t take a vendor’s word for its own security, including ours. So here’s what’s independently verified and where to look.
We’re ISO 27001-certified, covering our staff, offices, technology, and processes rather than a single product in isolation. We maintain a SOC 2 Type 2 report, an independent audit of whether our controls actually worked over time, not just whether they existed on paper.
We support the Safer Technologies 4 Schools framework, the assessment approach shared across Australian and New Zealand education jurisdictions.
On privacy, we align with the Australian Privacy Act 1988, GDPR, the UK Data Protection Act 2018, and POPIA in South Africa.
We also publish our sub-processor list, so you can see every third party involved in delivering the service. If your DPO needs to complete a Data Protection Impact Assessment, there’s a support document ready to download rather than a form to fill in and wait on.
Full detail, and the documents themselves, are at wonde.com/about/security.
What this looks like when a school actually uses it
King’s Baptist Grammar School in Adelaide spent 2025 doing the thing most IT leaders hope to avoid: changing their SIS and their Learning Management System (LMS) at the same time.
Joanna, who led it, has been open about the role we played. We kept the new student information system talking to the legacy LMS while the rest of the migration caught up, and worked with her team to extend the fields they could map between systems. Teachers largely didn’t notice, which was the point.
“We wouldn’t have been able to go live with our broad-scale digital transformation project if it wasn’t for Wonde supporting different integrations along the way.”
Joanna, Projects and Systems Manager, King’s Baptist Grammar School
On the trust question specifically, she puts it better than we would:
“It’s just really nice to know that we have a very trustworthy partner there to support us in all of our systems work.”
Watch Joanna’s story | under 2 minutes
The short answer
You control your school’s data. We move it, on your instruction, to the places you’ve chosen, and we give you the tools to check that’s what’s happening.
That’s the whole model. It’s why 30,000+ schools globally work with us, and why we’d rather explain it than ask you to assume it.
If you want to see the controls on your own data rather than in a screenshot, book a Wonde Premium walkthrough. Twenty minutes, your portal, and time for your specific questions.
And if there’s something in here you’d want to press us on, do. Our privacy and security team answers those directly at wonde.com/about/security.