School Data Processing Agreement

The Article 28 UK GDPR terms under which Markwell processes pupil and staff data on behalf of schools.

Last updated 29 October 2026

1. Parties and roles

This agreement is between the school, academy trust, college or teacher using Markwell (the "Controller") and [Company legal name] (trading as Markwell) (the "Processor"). It forms part of the Terms of Service and applies whenever the Processor processes personal data on the Controller's behalf.

2. Subject matter and duration

The Processor provides an online assessment service. Processing lasts for the term of the subscription and the deletion period set out in clause 10.

3. Nature and purpose of processing

  • Hosting accounts for staff and pupils and managing classes.
  • Delivering timed assessments and recording answers and integrity signals.
  • Storing scanned scripts, transcribing them and suggesting marks.
  • Producing results, feedback and analytics for the Controller.
  • Syncing rosters and results with systems the Controller connects (for example an MIS or learning platform).

4. Data subjects and categories of data

  • Pupils: name, school email or identifier, year group, class, answers, scanned scripts, marks, feedback, attempt timing and integrity signals.
  • Staff: name, school email, role, activity logs.
  • No special category data is required. The Controller should not upload it (for example SEN or health notes) unless agreed in writing.

5. Processor obligations

The Processor will:

  • process personal data only on the Controller's documented instructions, including these terms and the Controller's use of the service settings;
  • make sure everyone with access is bound by confidentiality;
  • apply the technical and organisational measures in Annex A;
  • assist the Controller with data subject requests, data protection impact assessments and consultations with the ICO;
  • notify the Controller without undue delay, and in any case within 48 hours, of becoming aware of a personal data breach, so that the Controller can meet its own 72-hour reporting duty;
  • make available the information needed to show compliance and allow audits as set out in clause 9;
  • tell the Controller immediately if it believes an instruction breaks data protection law.

6. Artificial intelligence safeguards

  • Only question text, mark schemes and answer text are sent to AI providers — never pupil names, emails or image files.
  • AI providers may not retain the data beyond the request or use it to train models.
  • AI suggestions are always available for teacher review; the Controller's teachers remain accountable for released marks, in line with Ofqual principles and DfE guidance on generative AI in education.

7. Sub-processors

The Controller gives general authorisation for the sub-processors in Annex B. The Processor will give at least 30 days' notice of any new sub-processor; the Controller may object on reasonable data protection grounds and, if no solution is found, end the affected service with a pro-rata refund. The Processor remains liable for its sub-processors.

8. International transfers

Personal data will be stored in the UK or EEA. Any transfer to another country will rely on UK adequacy regulations, the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.

9. Audits

The Processor will answer reasonable security questionnaires and share summaries of independent assessments. On-site audits may take place once a year with 30 days' notice, at the Controller's cost, unless following a breach.

10. Return and deletion

The Controller can export its data at any time. When the contract ends, the Processor will keep the data available for export for 30 days and then delete it from live systems within a further 60 days, and from backups within 35 days of that, unless the law requires it to be kept.

11. Liability and precedence

Liability under this agreement follows the Terms of Service. If this agreement conflicts with the Terms of Service on data protection, this agreement wins.

Annex A — Security measures

  • Encryption in transit (TLS 1.2+) and at rest.
  • Tenant separation enforced by database row-level security on every school table.
  • Role-based access; administrative access limited to named staff and logged.
  • Server-side checks for every sign-in, permission and entitlement.
  • Signed, header-only secrets for integrations, checked in constant time.
  • Daily backups with tested restores; monitoring and alerting.
  • Staff confidentiality agreements and data protection training.

Annex B — Sub-processors

  • Supabase Inc. — Database, authentication and file storage. Location and safeguard: EU (Ireland) region; UK IDTA / SCCs where applicable.
  • Cloudflare Inc. — Application hosting and content delivery. Location and safeguard: Global edge network; UK IDTA / SCCs.
  • OpenAI (API) — Text-only AI marking suggestions and question transcription. Location and safeguard: No pupil names or files sent; no training on customer data.
  • Stripe Payments Europe Ltd — Card payments and invoicing (staff payers only). Location and safeguard: EU / UK.
  • Lovable email service — Account and service emails. Location and safeguard: EU / US; UK IDTA / SCCs.