Safeguarding and data
As little data as possible, and a person behind every decision.
This page explains, in plain English, how Aspinall Learning is built. It is not the privacy notice or the agreement a school would receive before a pilot — those are written with each school.
Five ways in, and what each one holds
Guest
Anyone can use the whole pupil experience without an account. Progress is kept in that browser only and is never sent anywhere.
Demo school
A made-up school with made-up pupils, for looking around as a SENCo, a pupil or a parent. The database keeps it apart from every real school.
Pupils
A class code, a name and a PIN. No email address.
Parents and carers
The family code their child was given. It links them to their own child and nobody else, and the family view is read-only.
Staff
An email address and a password. Staff see only the pupils they are responsible for.
Where information lives
- There is no application server holding pupil data. Pages are plain files; a signed-in device talks directly to the database, and the database decides, row by row, what that person may read or change.
- The installed app keeps a copy of pages and topics on the device so that it opens quickly and works offline. It keeps no pupil records there.
- Tutor mode is built from authored content only. No AI model is involved in teaching.
People decide
- The platform notices; people decide. A pupil who has gone quiet is flagged to staff with the reason shown. What happens next is a member of staff’s decision.
- Suggested wording for a follow-up is a draft for a member of staff to edit and approve. Approving records a decision. It does not send a message to anyone.
- Anything that looks like a safeguarding matter is never worded automatically. It is passed straight to a person.
Before a school uses it with real pupils
Until each of these is in place for a school, the demo school and guest mode are the right way to look around.
- A named safeguarding lead at the school, and an agreed route for concerns that arise through the platform.
- A data protection impact assessment and a data-sharing agreement, written with the school.
- A privacy notice for young people as well as for adults.
- Retention, deletion, backup and incident handling that have been rehearsed, not just written down.