ScreenED
Privacy

Privacy policy

Last updated 30 September 2026

ScreenED is in pilot development. This policy describes how the service is designed to handle data. Each school that uses ScreenED signs a data processing agreement with us, and that agreement governs the details for that school.

The short version

Who is responsible for what

For the ScreenED service, the school is the data controller: it decides why student and staff data is used and it is the point of contact for families. ScreenED is the data processor: we handle the data only to run ScreenED for that school and only on the school's written instructions. If you are a parent or student and want to see, correct or delete something, please ask your school. We will help the school respond quickly.

For this website and for messages sent to us, ScreenED is responsible for the personal data described in the next section.

This website

The ScreenED service: what we hold for a school

WhoWhatWhy
Teachers and staffName, school email, role, classes taughtTo record who approved what, and for which students
Teachers and staffEvery approval, change and removal, with date and timeThe audit trail schools use to review decisions
StudentsSchool email, name if the school provides it, grade, and class enrolmentTo give each student the approved sites for their own classes
Student requestsThe web address a student asked their teacher to approve, the reason they chose, the device ID, and the timeSo a teacher can decide. Student names are hidden by default and looked up only on purpose; each lookup is logged
DevicesA device ID and its grade or groupTo apply the right rules to the right Chromebook
The schoolA timestamped record that the school confirmed it has the consent it needsSo the school, not ScreenED, holds the consent paperwork

What we do not collect

The school's own Chromebooks keep their normal Chrome browsing history under the school's control. That history is the school's record, not ours.

The ScreenED Chrome extension

The extension is installed by the school on its own student and teacher accounts. On a student's device, it checks each web address against the school's approved list and shows the "not approved" page when needed. It sends information to ScreenED only when a person acts: a teacher approving a site, or a student tapping the button to ask a teacher to approve one. It also needs to know which classes a signed-in student belongs to, so it can apply the right approvals. It does not read the content of pages.

Where the data is kept, and who helps us

Each school's data is kept in its own separate database, never mixed with another school's. We use these providers to run the service:

We will list any new provider that handles school data and give schools notice before adding one.

How long we keep it

Security and incidents

Data travels over encrypted connections. Access to a school's data is limited to its own named administrators; ScreenED staff access it only to give support at the school's request, and that access is logged. If we learn of a security incident that affects a school's data, we tell the school without delay and within 24 hours, so it can meet its own legal deadlines.

Children

ScreenED is used by schools, not by children directly. Students never create a ScreenED account. The school is responsible for informing families and for the consent or other legal basis it relies on. We support that by keeping only what the service needs.

Your rights

Depending on where you live, you may have the right to see, correct, delete, move or object to the use of your personal data, and to complain to your data protection authority. For anything held about a student, please contact the school first. For anything we hold as the responsible party, such as a message you sent us, email us and we will respond.

Changes to this policy

If we change this policy in a way that matters, we will update the date at the top and tell the schools we work with.

Contact

Privacy questions: hello@screenedforschools.com