One page for a board, a principal or a privacy officer. Everything on it can be verified by a member of your own IT staff in ten minutes.
A free web app in which a student names something they are working on, cuts it into steps, and uses structured thinking methods (5 Whys, Pre-mortem, Working Backwards and others) to break it down. It runs in the browser and installs as an app on Chromebooks, iPads and laptops without administrator involvement.
Nothing. There are no accounts, so no names, emails or logins. There is no server, so nowhere for work to go. There are no analytics, no tracking and no third-party scripts, fonts or images. Student work stays in the browser on the device and in a file the student saves and moves themselves.
The app is delivered with a Content-Security-Policy that forbids outbound network connections outright: the browser itself refuses to let the page fetch, post or send a beacon anywhere, including back to its own server. An automated test asserts that the app makes no request to another origin, and another asserts that the policy is present every time it is built. The app is a set of static files; there is no backend to be breached.
No data processing agreement, because there is no processing. No privacy impact assessment, because there is no personal information. No hosting conversation, because nothing is hosted. No accounts to provision, and none to remove at the end of the year.
Greggle never receives, stores or processes anything a student writes, and the software is built so that it cannot.
Greggle is made by Stuart Muir, an independent developer in Wellington, New Zealand. Questions to feedback@greggle.app. The licence terms, including a written undertaking about outbound connections, are at greggle.app/licence/.