This summary is provided for school IT, principals, privacy officers, and parents considering LEP. The full report covers every Australian Privacy Principle, subprocessors, retention, incident response, and our honest assessment of what's not yet done. The canonical version is the Markdown document below.
Download full report (Markdown · ~12 KB)syd1)| Category | Purpose |
|---|---|
| Email, display name, role | Authentication + identifying student to teacher |
| Writing-process events (timing, paste metadata, caret position) | Process summary in teacher report |
| First 2000 chars of pasted text | So teacher conversations about pastes can be specific |
| Final draft text | Cross-device continuity + teacher review |
| Vendor | Role | Region |
|---|---|---|
| Supabase | Database + auth | Sydney (AWS ap-southeast-2) |
| Vercel | App hosting | syd1 region pinned |
| Google OAuth (optional) | Alternative sign-in | Global |
Access, correction, deletion, and complaint rights are honoured within 30 days of a verified request to privacy@learningevidenceplatform.com. See the full report for the detail of how each Australian Privacy Principle is met.
LEP follows the NDB scheme. If an eligible breach occurs, affected users will be notified directly, the OAIC will be informed via the prescribed form, and the adopting school will be told as soon as practicable, regardless of NDB classification, so the school can fulfil its own obligations.