Trust
A record this personalhas to be this careful.
A longitudinal record of children deserves scrutiny, and we would rather answer the hard questions here than have them asked in your governors' meeting without us in the room. This page is written for your Head, your DPO, and your most sceptical parent.
Consent with provenance
Consent is recorded per student and per purpose: who granted it, in what capacity, on what date, and when it expires. It is not a checkbox at signup; it is a first-class record that travels with the student, and the system enforces it. Where consent is withdrawn, dependent data is handled according to your school's policy, on schedule.
Identity that never guesses
Evidence is matched to students against your canonical roster. Full-confidence matches link automatically with the method and confidence recorded; everything else waits in a human review queue. A wrong merge in a school is a safeguarding matter, not a bug, so the system is built to be uncertain out loud rather than confidently wrong.
Retention by design
Every source document carries a retention tier and an expiry date, set by your school's policy. Specialist reports, pastoral records and routine exports are not all the same, and they are not kept as if they were. What should be forgotten is forgotten on schedule; what must be kept is kept with its context.
Traceable, never creative
Every sentence of every brief stores the identifiers of the observations it cites. If evidence is corrected or superseded, dependent briefs are marked stale and regenerated. A claim with no evidence has nowhere to live in this system, which is the property that makes the record safe to act on.
Family rights, honoured practically
The record is structured, which means subject access requests stop being an archaeology project. A student's record can be compiled, reviewed and exported cleanly, and families can be shown exactly what the school holds and why. Transparency is easier when the evidence was organised from the start.
Your school controls the data
Your school is the Data Controller; Evalent is the Data Processor under a signed agreement. Hosting on AWS EU (Ireland), encryption at rest and in transit, role-based access at every altitude, and student data never used to train language models. The record is exportable: it is your asset, not our hostage.
For your data protection officer
The questions your DPO will ask, answered in advance.
Lawful basis, processing purposes, retention schedules, sub-processors, and the consent model, in one page built to be attached to your internal review.