Skip to content
Educator

For data protection officers

Data protection & your DPIA

This page is for school data protection officers and anyone completing a Data Protection Impact Assessment (DPIA) before rolling out Educator. It gives you the processor-side facts you need, grouped under the usual ICO DPIA headings.

Questions, or need our DPIA / RoPA / a countersigned DPA? support@educator-labs.com

Who is responsible for what

When your school adopts Educator, the school is the data controller for its students' and staff's personal data, and Educator is your processor under the Data Processing Agreement. That means your school completes its own DPIA. This page gives you what you need to fill it in. (Individuals who sign up directly, without a school, are a separate arrangement where Educator is the controller; that isn't part of your school deployment.)

Nature, scope & purpose of the processing

  • What it is: browser-based daily revision practice. Students answer short sessions of cards; a spaced-repetition algorithm chooses what they see next; teachers see class progress. Seventeen subjects across GCSE and KS3.
  • Data subjects: students (aged 11–16) and teaching staff.
  • Purpose: deliver the revision practice the school subscribed to, and let teachers monitor their classes. No advertising, no profiling for marketing, no sale of data.
  • Lawful basis: Article 6(1)(b) (performance of the contract) for account and practice data; Article 6(1)(f) (legitimate interest in operating the service securely) for short-lived server logs. The school provides privacy information to students and parents.

Personal data processed (data minimisation)

Identity

Name and email address. No date of birth for your pupils: it is asked only of learners who sign up on their own, without a school

School context

Year group, exam board, exam tier, class membership

Practice activity

For each question: the card, correct/incorrect, the answer the student gave (typed, picked or matched), time-to-answer and a timestamp. Homework hand-ins with their scores, and in a teacher-hosted live class, correct/incorrect and time per question

Progress & cosmetics

XP, streak count, daily goal, equipped badge/character

Not collected

No postcode, uploaded photos, demographic data, location/geolocation, device fingerprint, or special-category data. (A student who signs in with Google or Microsoft brings that account's profile picture, which Clerk holds and shows only in their own account menu.)

Storage, sub-processors & international transfers

Data is stored in AWS us-east-1 (Virginia, USA). The transfer is covered by the UK International Data Transfer Agreement (IDTA). Educator uses 6 sub-processors, all US-based and all under the UK IDTA:

Clerk

Authentication and account management

Neon

Database hosting (AWS us-east-1, Virginia)

Vercel

Application hosting and delivery

Sentry

Error monitoring

Stripe

Payment processing (school billing contacts only)

Resend

Transactional and digest email

The authoritative, version-controlled sub-processor list lives on the Data Processing Agreement page.

Retention

  • Account and practice data: kept while the account is active.
  • After a school pilot or subscription ends: data is retained for 60 days to allow retrieval, then deleted in full.
  • A teacher's own deletion from their profile is immediate and irreversible. A student's account is your school's record: students cannot delete it themselves, and we delete it on your instruction within 5 working days.
  • Server logs: 30 days.

Security measures

  • Encryption at rest and TLS for all data in transit.
  • Authentication delegated to Clerk; student passwords are never visible to Educator staff.
  • Least-privilege production credentials with periodic rotation.
  • Changes are tested on an isolated preview environment before reaching production; production and test data are kept separate.
  • Ongoing internal security review and testing; an independent external penetration test is planned, with results available to school DPOs on request once completed.

Children's data: ICO Age Appropriate Design Code

  • Hard age-gate on self-serve sign-up: a learner signing up on their own, without a school, gives a date of birth, and under-13s are routed to a parental-consent flow. Pupils who join through your class code are your school's pupils (you are the controller) and are not asked for one.
  • Profiling is used only to choose the next revision card (spaced repetition), never for advertising or behavioural profiles.
  • Progress-only feedback and high-privacy defaults; class and school leaderboards are never public and students' real names never appear on a public board.
  • No countdown timers, streak-loss guilt prompts, or other dark patterns.

Data subject rights

Every signed-in user can download their own data from their profile at any time. Teachers can also delete their own account there; deletion cascades through the database and the auth provider, and a teacher who still teaches classes hands them to a colleague first (with no colleague at the school, the classes are archived and stay with the school). Students cannot delete their own account: as controller, the school asks us to. Rectification requests are handled by email. The school passes on any rights requests it receives, and Educator assists within 5 working days.

Key risks & mitigations

Engagement loop applies pressure on a child

Progress-only feedback, banked streak freezes, no countdown timers or FOMO prompts, no 'you've been overtaken' messaging. Competitive signals are teacher-side only.

One student's data visible to another class or school

All class/school queries are scoped server-side; students' real names never appear on public leaderboards.

Personal-data breach at Educator or a sub-processor

Encryption at rest and in transit; least-privilege credentials; the school is notified without undue delay and within 24 hours where feasible.

Cross-border transfer to a non-adequate jurisdiction

All processors are US-based and covered by the UK International Data Transfer Agreement (IDTA).

Documents

Talk to us

If your DPO has questions not covered here, or needs anything in a particular format for your records, email support@educator-labs.com. We aim to respond within one working day.

To attach to your DPIA: use your browser's File → Print → Save as PDF to create a printable copy.