protégéThe school board pack
Everything a school board's privacy officer, IT department and principals need to decide whether to use Protégé, and how to run it safely. Written for Ontario first (MFIPPA, the Education Act, EDSTA and its 2026 regulations, AODA), and organized so it carries over to Québec, the rest of Canada, the EU, the UK and the US.
| Document | For | What's in it |
|---|---|---|
| Data inventory | Privacy officer | Every piece of information, why it's kept, who sees it, where it lives, when it's deleted |
| Privacy impact assessment (draft) | Privacy officer | Pre-filled PIA; the board fills in its own parts |
| Notice to families (EN/FR) | Schools | Ready-to-send notice covering O. Reg. 52/26 |
| AI transparency | Privacy officer, principals | What the AI does and doesn't do, human oversight, validation, known limits |
| Security summary | IT security | Accounts, sessions, headers, supply chain, what's not done yet |
| Running Protégé for a school or board | IT | Board-managed computers, encryption, network, backups, updates |
| If something goes wrong | Privacy officer | Breach steps, using the access log, notification |
| Accessibility conformance | Accessibility lead | WCAG 2.2 AA status, how it was tested, known gaps |
In one paragraph. Protégé runs entirely on a computer the school or board controls. That includes its AI and voice typing. The people who make it receive nothing. Students use nicknames and a picture key, never real names or email. What they write stays on that computer, is seen only by them and their teacher, and is deleted by the board's retention rule. Teachers approve every lesson, can read every conversation, and can correct anything the AI judged. Students are told plainly that Gloam is an AI. It's free and open source (AGPL-3.0), so anyone can check every claim in these documents against the code.
These documents explain how the software works. They are not legal advice. The board's privacy officer and counsel decide how they apply.