Private test build — draft notice
This document has not been published as final public terms or privacy notice. It may show unfinished controller or contact fields. Lumi is available only to approved testers until its EU legal identity and counsel review are complete.
School DPIA Template
Product: Lumi Tutor Controller: [CONTROLLER_NAME] Processor: [COMPANY_LEGAL_NAME] Prepared by: [DPIA_OWNER] Reviewed by: [DPO_NAME] Date: [LAST_UPDATED_DATE]
Not legal advice. This template helps a school or school operator assess Lumi Tutor. A school controller must adapt it to its own national law, role, pupils, and deployment.
1. Decision
2. Processing description
Lumi Tutor provides formative tutoring, practice, feedback, and parent/teacher visibility. It must not make official school decisions.
Data subjects
- Students/children.
- Parents or guardians.
- Teachers.
- School administrators.
Data categories
- Parent/teacher account identifiers.
- Child first name or nickname.
- Child age, language, country, learning preferences, and school/year context.
- Tutor messages and generated responses.
- Summary-only learning memory by default.
- Safety events.
- Learning progress and practice metadata.
- Technical logs, IP address, user agent, authentication events.
Data not collected by design
- Child last name unless a school contract explicitly requires roster import.
- Child home address.
- Child phone number.
- Exact geolocation.
- Advertising identifiers.
- Religious affiliation, belief status, or denomination as a child profile attribute.
- Biometric identification data.
- Official grades, disciplinary records, admissions files, or special-education diagnoses.
3. Purposes
4. Roles and lawful basis
The school must document its lawful basis under its national law. Depending on the country and school type, this may involve public task, legal obligation, contract, legitimate interests, or consent. Lumi must not choose the lawful basis on behalf of the school.
5. Necessity and proportionality
6. Risks
7. Required evidence before pilot
- Signed pilot agreement.
- Signed DPA.
- Completed school-specific DPIA.
- Approved subprocessor list.
- Completed transfer assessment.
- Local minor consent/authority review.
- AI Act risk-register classification.
- Accessibility audit plan.
- Parent/guardian communication template.
- Teacher acceptable-use guide.
- Incident escalation contact list.
- Data deletion/export test.
8. Prior consultation
If residual high risk remains after mitigation, the school/controller must decide whether supervisory-authority consultation is required under GDPR Article 36 or national law.
9. Approval