Last updated: 14 November 2026
1. Introduction
This DPA automatically applies when the School’s subscription to the MathedUp service takes effect in accordance with the MathedUp Service Terms.
2. Definitions
“UK GDPR”, “personal data”, “processing”, “controller”, “processor”, “personal data breach,” “special category data” and “data subject” have the meanings given in the UK GDPR and the Data Protection Act 2018 and any future statutory amendments. “School Data” means personal data relating to the School’s pupils and teachers that MathedUp processes under this agreement.
3. Roles
3.1 The School is the controller of Pupil and Teacher Data directly supplied by the School for use of the Service. MathedUp is the processor of that data.
3.2 The School is responsible for ensuring that it has a lawful basis for providing Pupil and Teacher Data to MathedUp and instructing MathedUp to process that data on its behalf. Each party complies with its own obligations under data protection law. Where a pupil under 13 uses the Service through the School without a parent, the School confirms that it has a lawful basis for this and that it has told parents.
3.3 This Data Processing Agreement applies only to personal data processed by MathedUp on the School’s behalf in connection with the Service. It does not apply to personal data that MathedUp processes as a controller for its own purposes.
3.4 A pupil who joins a class by class code using their own MathedUp account is outside this Data Processing Agreement. MathedUp is the controller of that pupil’s data, and the teacher sees the pupil’s progress because the pupil chose to share it.
4. Subject matter, duration, nature and purpose
4.1 Subject matter: provision and performance of the Service and processing initiated by the School’s use of the Service.
4.2 Duration: the term of the School’s subscription, plus the retention period in clause 11.
4.3 Nature and purpose: creating and maintaining pupil accounts; recording pupils’ self-assessed topic confidence and quiz results; presenting those to the pupil and to their teachers; enabling the pupil to use learning content.
4.4 Type of personal data:
Pupil Data:
- pupil full name, as supplied by the School
- school email address
- year group
- a pupil-chosen or system-generated display name (“gamer tag”)
- class membership, class and set names
- self-assessed topic ratings, quiz attempts and scores, written answers and working, marks from class tasks (including marks a teacher types in), badges, last-active timestamp
Teacher Data:
- full name
- school email address
- role
- class
4.5 Categories of data subject: pupils and teachers of the School.
4.6 Special category data: none. MathedUp does not collect or request special category data and the School must not upload it.
5. Processing on documented instructions
5.1 MathedUp processes Pupil and Teacher Data only on the School’s documented instructions, which comprise this agreement, the pupil and class details the School provides (by upload, by import from its Google or Microsoft account, or entered by its staff), and the ordinary operation of the platform’s features as documented, unless required otherwise by law, in which case MathedUp will inform the School before processing unless the law prohibits that.
5.2 MathedUp will not: sell School Data; share it with third parties for advertising; use it to target advertising at pupils; or use it to train any machine learning model.
6. Confidentiality
6.1 Persons authorised to process School Data are bound by an obligation of confidentiality and at all times act in compliance with data protection legislation and this DPA. Access is limited to those who need it to provide or support the Service.
7. Security
7.1 MathedUp maintains appropriate technical and organisational measures, including:
a. Data minimisation by design, full names only for pupils the School adds and seen only by that pupil’s own teachers and the School’s MathedUp lead, other pupils see a gamer tag only; no home address, date of birth, photograph or special category data
b. Row-level security with appropriate measures including on every table, so a record is readable only by the pupil it belongs to and the teachers of a class that pupil has joined
c. Encryption in transit (TLS) for all connections, and encryption at rest by the database provider
d. Credential handling delegated to the authentication provider; MathedUp never stores or sees a password in plain text; school single-sign-on (Google or Microsoft) is supported so that no additional pupil credential need exist
e. Least-privilege access, administrative interfaces are restricted to the account owner
f. Automated testing of the access rules on every change, including explicit tests that a teacher cannot read another class’s data and that pupil email addresses are not publicly readable
8. Sub-processors
8.1 The School gives general authorisation for MathedUp to engage the sub-processors listed below. MathedUp will give the School at least 30 days’ notice before adding or replacing a sub-processor (except where an urgent replacement is needed on security grounds, in which case MathedUp will tell the School as soon as it can), and the School may object on reasonable data protection grounds. Each sub-processor is bound by written terms offering protection equivalent to this agreement, and MathedUp remains fully liable for their performance.
| Sub-processor | Service | Personal data involved | Location |
|---|---|---|---|
| Supabase | Database hosting | Account details, class membership, progress and quiz results | UK |
| Resend | Email service | Email address, first name, and the content of the email | US |
| Anthropic | AI | A pupil’s written answer, the question and the mark scheme. No name, email or account identifier is sent. | US |
| Sign-in | Name and email address | US and elsewhere | |
| Microsoft | Sign-in | Name and email address | US and elsewhere |
9. International transfers
9.1 School Data is stored in the United Kingdom. Some School Data is also processed briefly outside the UK by the sub-processors listed above. Where a sub-processor is located outside the UK, MathedUp ensures a lawful transfer mechanism (UK adequacy regulations, the IDTA, or the UK Addendum to the EU SCCs).
10. Assistance to the School
10.1 MathedUp will cooperate with and assist the School for the fulfilment of its obligations, taking into account the nature of the processing:
a. Data subject rights. The Service allows a pupil to export or delete their own Pupil Data. Where the School asks MathedUp to exercise a data subject right on a pupil’s behalf, MathedUp will acknowledge the request and start work on it within 5 working days, and will complete it in time for the School to meet its one-month deadline
b. Personal data breach. MathedUp notifies the School without undue delay and in any event within 48 hours of becoming aware of a breach affecting School Data, with the information the School needs for its own Art. 33 notification.
c. DPIAs and prior consultation. MathedUp provides information reasonably required for the School’s data protection impact assessment.
11. Deletion and return
11.1 On termination, or on the School’s written instruction, MathedUp deletes School Data processed on the School’s behalf within 30 days, except where UK law requires retention. Removing a School’s pupil and class details ends the link between a pupil and the School’s classes. It does not delete the pupil’s own MathedUp account, progress or self-assessment, except as set out in the next sentence. Where the link ends for a pupil under 13 and no parent is attached to the account, MathedUp will lock the account straight away and invite a parent to take it over, and will delete the account after 30 days if no parent does.
12. Audit
12.1 MathedUp makes available to the School the information necessary to demonstrate compliance with this agreement, and allows for and contributes to audits, including inspections, by the School or an auditor it mandates, on reasonable notice and no more than once a year unless a data breach has occurred.
13. Liability, Governing Law and general
13.1 Each party’s total aggregate liability arising out of or in connection with this Data Processing Agreement shall be subject to the limits set out in the MathedUp Service Terms.
13.2 Nothing in this Data Processing Agreement shall limit or exclude either party’s liability to the extent that such liability cannot lawfully be limited or excluded.
13.3 This Data Processing Agreement and any dispute or claim arising out of or in connection with it shall be governed by the laws of England and Wales. The courts of England and Wales shall have exclusive jurisdiction to settle any such dispute or claim.
13.4 If any provision of this Data Processing Agreement is found to be invalid or unenforceable, the remaining provisions shall continue in full force and effect.
13.5 A failure or delay by either party to exercise any right or remedy under this Data Processing Agreement shall not constitute a waiver of that right or remedy.
13.6 Any amendment to this Data Processing Agreement must be agreed in writing by both parties.
13.7 A person who is not a party to this Data Processing Agreement shall have no right to enforce any of its terms.
13.8 The parties will each provide a contact for data protection matters. The School may contact MathedUp at hello@mathedup.co.uk regarding any questions, requests or concerns relating to the processing of School Data.

