Monty's data processing agreement, version 1

Version 1 (dpa-2026-11), written 6 November 2026 and published 10 November 2026. The agreement a school accepts when its first Monty admin sets it up (Article 28 UK GDPR). It hasn't been read by a lawyer yet. Our reading, not legal advice.

Parties

  • The controller: the school named at setup, with its register number ("the School"). The member of staff who accepts this agreement at setup confirms they work at the School and can accept it for the School, or will have it signed by someone who can.
  • The processor: Omar Latreche, trading as Learn-Python, 78 Halesworth Road, RM3 8QB, who runs Monty (hellomonty.app) ("Monty"). Contact: hello@hellomonty.app.

1. What this agreement covers

Subject matterMonty's classes: pupils join a teacher's class, carry their progress between devices with a login card (or the School's Microsoft or Google account), and their teachers see that progress; safeguarding concerns raised by Monty's checks go to the School's designated safeguarding lead (DSL).
DurationFrom acceptance until the School stops using Monty's classes, then until deletion under clause 9.
Nature and purposeStoring, organising, showing to the School's staff, sending to the School's DSL, exporting and deleting class data, only to teach the School's pupils and keep them safe. Never to improve Monty, train or test its AI, or for Monty's own statistics. Counting use per class and per school for fair-use limits and the price is part of the service.
Personal data: pupilsA generated username and the nickname the pupil chose; which class they're in, and when they joined and were accepted; their progress (lessons and activities passed, checks, hints used, mistakes the tests recognised, when they were last active, the current lesson); minutes active each day; how many times a day they pasted a large block of code or reached a worked example (counts, never content); how many AI calls a day, how many were chat and how many late at night; an HMAC of their login code; a keyed fingerprint of a linked school account (never its name or email); when they last saw "what your teacher sees". A flagged message, its level, category and time, and Monty's one-sentence summary. No pupil's name, email address, date of birth or photo: teachers' names for pupils stay in the teacher's own browser.
Personal data: staffEach member of staff's work email, roles, who invited them and when, an encrypted secret for their authenticator app, and a keyed fingerprint of a linked Microsoft or Google account; the DSL's and deputy's email addresses and (optionally) names; who viewed or changed each class, and when (ids only).
Special category dataNone is asked for. A flagged message can reveal health or other special category data; it is kept only as clause 9 says and seen only by the DSL (and by Monty's operator on purpose, which is logged).
Data subjectsThe School's pupils in classes (aged 11 to 18), and the School's staff who use Monty or receive its emails.

2. Instructions

Monty processes the personal data only on the School's documented instructions: this agreement, and what the School's staff do in Monty (making and deleting classes, accepting and removing pupils, inviting and removing staff, changing the DSL, the settings for each class). Monty tells the School at once if it thinks an instruction breaks data protection law. Transfers outside the UK happen only as clause 6 says.

3. Confidentiality

Everyone Monty lets process the data is bound to keep it confidential. Today that is the operator alone.

4. Security (Article 32)

Monty keeps the measures in the record of processing, among them: encryption in transit and at rest; no pupil names on Monty's server; login codes stored only as keyed hashes; each member of staff signs in with an email link or the School's Microsoft or Google account, then a code from their own authenticator app (the DfE's cyber security standard), with the secret encrypted; signed, HttpOnly sessions that a new card, a new authenticator, "sign out everywhere" or removal ends; lockouts after wrong codes; every view of a class logged; a flagged message kept out of the DSL's email unless the School chooses otherwise; and links in emails that can only point at Monty. Monty reviews these measures at least once a year and when the service changes.

5. Sub-processors

The School gives general authorisation to the sub-processors in the sub-processor list. Monty tells the School at least 30 days before adding or replacing one: by email to the School's Monty admins and DSL, and on the list itself, which keeps a dated record of every change. The School may object within those 30 days; if the objection can't be resolved, the School may stop using Monty's classes and have its data deleted, with a refund under clause 12. Monty puts the same data protection obligations on each sub-processor by contract and remains liable for them.

6. Transfers outside the UK

Data goes outside the UK only to the sub-processors listed, under the safeguard each one's terms provide, as the sub-processor list records: today, the EU standard contractual clauses with the ICO's UK addendum, for Anthropic, Vercel and Databricks (Neon) in the United States. Amazon Web Services sends emails from London. Class data is kept in the United States today. Monty has built keeping class data in a database of its own in London, with classes' pages running in London; that is one switch for every school's class data, not a choice school by school, and the sub-processor list says where class data is kept at any time. A School that needs its class data kept in the UK should say so before it sets up its classes.

7. Helping the School

Monty helps the School, as far as it reasonably can:

  • with pupils' and staff's rights: Monty passes any request it receives to the School within 5 working days and doesn't answer it itself; teachers can export a class and delete a pupil or a class themselves at any time;
  • with security, breaches, DPIAs and consulting the ICO (Articles 32 to 36): Monty publishes a DPIA template filled in with what it knows, and answers the School's questions.

8. Breaches

Monty tells the School of a personal data breach without undue delay, aiming at 24 hours after becoming aware of it, by email to the School's Monty admins and DSL, with what is known (what happened, the data and pupils affected, likely consequences, what Monty has done) and the rest as it becomes known. Breaches are listed on the trust page.

9. Retention and the end

The periods below are the same for every school, and are stated on Monty's privacy page and in its emails:

  • a class is read-only from the day after its school year ends and deleted at the end of the first month of the School's next year, unless a teacher deletes it sooner, which takes effect at once; a class carried on into the next year keeps its pupils. For a school year that starts in September, that is read-only from 1 September and deleted on 30 September. Each School says which month its year starts in when it is set up;
  • pupils who asked to join but weren't accepted are deleted after 14 days;
  • a safeguarding alert is deleted 30 days after the DSL confirms receipt (or 30 days after it was raised, if it is never confirmed);
  • the access log is kept 24 months; emails 30 days; links in emails a day after they're used or expire; invitations never accepted, 30 days;
  • a member of staff's email, authenticator secret and linked account go when they leave or are removed;
  • a school set up but never finished (not approved, its DSL and admin email never confirmed) is deleted after 30 days.

When the School stops using Monty's classes, it can export its classes and then delete everything in one step; otherwise Monty deletes it under the rules above. Monty keeps no copy, apart from what the law requires. Pupils keep their own progress on their own devices: that is theirs, not the School's or Monty's.

10. Information and audits

Monty makes available what the School needs to show this agreement is kept, and allows and contributes to audits by the School or an auditor it chooses, with reasonable notice, at most once a year unless there's been a breach.

11. Changes to this agreement

A new version is published with its date and what changed, and emailed to the School's Monty admins at least 30 days before it applies. The School may stop using Monty's classes instead, with a refund under clause 12. The version the School accepted, and when, is shown on its School page.

12. If Monty stops

Monty gives at least a term's notice (and never less than 90 days) before it stops offering classes. Until the last day, teachers can export every class; anything a School has paid for the unused part of the year is refunded.

13. Law

This agreement is governed by the law of England and Wales.

14. Schools outside the United Kingdom

This agreement is written to the UK GDPR. A School in another country may accept it as it stands. Monty makes no statement about any other country's law: where the School's own law asks more of a processor than this agreement gives, the School should write to Monty before it sets up its classes, and Monty will say whether it can meet it. "DSL" means the member of staff the School names as responsible for safeguarding or child protection, whatever that role is called where the School is.

Schedule 1: the School's choices

Each School chooses for itself, in Monty: the month its school year starts in (at setup, and changeable while it has no classes); the AI's level for each class and daily time limits (set by teachers); whether the School's own Microsoft or Google second factor is trusted; and whether the DSL's weekly patterns email is sent (on by default).

These are settings for every school at once, so they are the same for all schools and stated on the privacy page: what an alert email holds (a link to the message, never the message itself); the retention periods in clause 9; and where class data is kept (clause 6).