Privacy & data
Designed around school control.
How PrismScope approaches student data, and why that architecture matters to your school. This page is written for whoever in your school is responsible for privacy and data.
School-controlled storage
Your school's data stays under your school's control.
PrismScope's architecture starts from a simple principle: a school's own student data stays under that school's control. It isn't treated as a resource for PrismScope to use beyond delivering the platform back to that school. This is a starting condition of how PrismScope is built, not a policy added on afterwards.
Built with privacy in mind
Privacy runs through the design, not just the data handling.
PrismScope is deliberately built to avoid presenting students as being watched or monitored. Activity is shown as patterns and context for a conversation, not a live feed of individual actions. The same care applies to sensitive information, such as a student's support needs, which is presented in plain language rather than reduced to a score or a flag.
Clear access and permissions
Everyone sees information scoped to their role.
Whether someone is a teacher, a Learning Support Officer, a Principal, or a member of school IT, what they see in PrismScope is scoped to their role. Search results, dashboards and student records are automatically limited to what that role is permitted to see.
Designed for education environments
Built for schools, not adapted from a generic product.
Schools handle information that deserves particular care. PrismScope's design decisions, from how evidence is captured to how it's displayed, are made with that context in mind: a school community that includes students, teachers, learning support staff and families.
Questions from your IT or privacy team?
Let's talk it through directly.
If your school's next step depends on a specific answer about privacy or data architecture, we'd rather talk it through with you than leave you guessing from a web page.