Privacy policy
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
- We help schools make Chromebooks reach only the websites a teacher or IT has approved.
- The school decides why and how student data is used. We act only on the school's instructions.
- We don't read web pages, record what students browse, or keep a log of blocked attempts. The one time web addresses leave the device is when a student chooses to ask a teacher to approve one: the address they asked for, and the approved site they were on (see "Student requests" below). We don't take keystrokes, screenshots, camera, microphone or location.
- We never sell personal data, show ads, build advertising profiles, or use school data to train AI models.
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
- No accounts, no tracking cookies, no analytics, no advertising. Browsing this site doesn't require giving us any information.
- Fonts. The pages load fonts from Google Fonts, so Google receives your IP address and browser details when a page loads. See Google's privacy policy for how it handles that.
- Hosting and security. The site is delivered through Cloudflare, which processes technical request data (such as IP address) to serve pages and protect against attacks.
- Email. If you write to , we keep your message and address to reply to you. Mail is forwarded through Cloudflare Email Routing and sent through Brevo. We use it only to talk with you, and we don't add you to a mailing list without asking.
The ScreenED service: what we hold for a school
| Who | What | Why |
|---|---|---|
| Teachers and staff | Name, school email, role, classes taught | To record who approved what, and for which students |
| Teachers and staff | Every change to people, roles, approved sites and settings, with date and time. Never what a student browses | The audit trail schools use to review decisions |
| Students | School email, name if the school provides it, grade, and class enrolment | To give each student the approved sites for their own classes |
| Student requests | The web address a student asked their teacher to approve, the reason they chose, the device ID, and the time. If the student was on an approved site when they asked, that site's address is included too, so the teacher can see where they came from | So a teacher or the school can decide whether a site can be approved, and keep students off sites that can never be approved. The school holds these requests and decides how long they are kept. Student names are hidden by default and looked up only on purpose; each lookup is logged |
| Teachers' units | A unit name a teacher chooses (for example "Weather"), the classes it is for, and the list of website addresses in it | So a teacher can load a saved set of sites into a focus time. The teacher can delete a unit at any time |
| Devices | A device ID and its grade or group | To apply the right rules to the right Chromebook |
| The school | A timestamped record that the school confirmed it has the consent it needs | So the school, not ScreenED, holds the consent paperwork |
What we do not collect
- Page content, or a browsing history. ScreenED compares web addresses to the approved list on the device. It does not keep a record of the sites students visit or try to visit.
- Keystrokes, screenshots, camera, microphone or location.
- Grades, attendance, health records or other school records.
- Special category data such as health, religion, ethnicity, biometrics, sexual behaviour or criminal records.
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 checks in with ScreenED regularly (every 30 seconds to 5 minutes) to fetch the school's approved list and any focus time or test, and to report that it is working: the device code, the signed-in school account and the extension version, so IT can see every Chromebook is covered. It never sends the addresses a student visits, except the one a student asks a teacher about, or a page a teacher approves. 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.
Google Classroom and unit plans
These features are optional and only used by teachers. Students never use them.
- Importing a unit plan. When a teacher pastes or uploads a unit plan, the file is read inside the teacher's own browser to find website addresses. The file itself is never sent to ScreenED. Only the web addresses the teacher chooses to check are sent, so ScreenED can say which are already on the school's vetted list.
- Sync with Google Classroom. If a teacher presses this button, Google asks the teacher for permission to read the classes they teach and the posts in a class they pick (materials, assignments and announcements). This happens in the teacher's browser. ScreenED looks only for website links in those posts and shows them to the teacher. The text of the posts is not sent to or stored by ScreenED. Only the links the teacher approves are saved, as approvals.
- Post to Classroom. If a teacher chooses to, ScreenED posts a link to an approved site into their class, using permission the teacher grants at that moment.
ScreenED's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google data only to provide these features to the teacher who asked for them. We do not sell it, use it for advertising, or use it to train AI models, and no person at ScreenED reads it unless the school asks us to for support or the law requires it.
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:
- Cloudflare hosts the service and its databases and delivers the website and category filtering. We choose data centres in the Asia-Pacific region where possible. Where data leaves the country where the school is, the school's data processing agreement includes the safeguards that local law requires.
- Google provides school sign-in and, where a school chooses, class rosters through Google Classroom.
- Brevo sends email on our behalf.
We will list any new provider that handles school data and give schools notice before adding one.
How long we keep it
- Approvals stay while they are in use, and go when they expire or a teacher or IT removes them. The audit record is kept for a period set in the school's agreement.
- Student requests that have been answered are deleted on a schedule the school's IT chooses in Settings: by default at the end of each semester, or after a year, or after 30, 90 or 180 days.
- The record of changes (people, roles, approved sites, settings) is kept for 6, 12 or 24 months, as the school chooses, then deleted.
- If a teacher sets a daily time limit on a site, the minutes used are counted on the Chromebook only. The running total for the day is never sent to ScreenED and is discarded the next day.
- When a school ends its contract, we export its data to the school on request and delete it within 30 days.
- Messages to are kept for as long as needed to deal with them, then deleted.
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.
What ScreenED does and does not promise
ScreenED is designed to keep students to the sites a school has approved. It works as described when the ScreenED extension and the school's Google Admin settings are set up correctly and running. No filtering tool can guarantee that every workaround is closed, and we do not promise that.
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: