Data Processing Agreement
Between a participating school and Net Werth Ltd, trading as Monteeno. Article 28 UK GDPR.
Where pupil data is stored
Read clause 9 before anything else. The database holding pupil records is in London (AWS eu-west-2). Some subprocessors remain outside the UK, and the platform we contract with has not supplied an Article 28 agreement — clause 9 and Annex C set out exactly which.
If your school’s legal or data-protection team would rather work from their own paper, send it over and we will sign that instead. We will not argue about whose template gets used.
1Parties and scope
This agreement is between the School named on the accepted Founding Schools application (the Controller) and Net Werth Ltd, trading as Monteeno (the Processor).
It governs Monteeno’s processing of personal data on the School’s behalf while the School uses Monteeno under a school licence. It takes effect when the School’s licence is activated and continues until the licence ends and clause 8 has been completed.
Where this agreement and the School Licence Terms conflict on the handling of personal data, this agreement prevails.
2Roles
The School is the controller of personal data relating to its pupils and staff. The School decides which pupils are given accounts and for what educational purpose.
Monteeno is the processor of that data, and processes it only to provide the service to the School.
Monteeno is a separate controller in respect of its own business records: the School’s application to the programme, the contact details of the School’s nominated staff, and correspondence between the parties. That processing is described in the Privacy Policy and is outside this agreement.
3Subject matter, duration, nature and purpose
Set out in Annex A, together with the types of personal data and the categories of data subject, as required by Article 28(3) UK GDPR.
4Processing only on the School's instructions
Monteeno processes the personal data only on the School’s documented instructions, including in relation to transfers to a third country, unless required to do otherwise by law. Where the law requires it, Monteeno will tell the School before processing unless the law forbids that notification.
The School’s documented instructions are: this agreement, the School Licence Terms, the actions taken by the School’s staff through the Monteeno interface, and any further written instruction the School gives.
Monteeno will tell the School if, in its opinion, an instruction infringes UK data protection law.
Monteeno does not and will not use pupil personal data to train machine learning models, to advertise to pupils, to build advertising profiles, or for any purpose of its own beyond providing and securing the service.
5Confidentiality
Monteeno ensures that the people authorised to process the personal data are bound by an obligation of confidentiality, and limits access to those who need it to deliver or support the service.
6Security
Monteeno implements the technical and organisational measures set out in Annex B, which are appropriate to the risk in accordance with Article 32 UK GDPR.
Annex B states what is in place and also what is not, including the certifications Monteeno does not hold. It is deliberately not written as a list of reassurances.
7Subprocessors
The School gives general authorisation for Monteeno to engage the subprocessors listed in Annex C.
Monteeno will give the School at least 30 days’ notice by email to the nominated contact before adding or replacing a subprocessor. The School may object on reasonable data-protection grounds within that period; if the objection cannot be resolved, the School may terminate the licence without penalty and clause 8 applies.
Monteeno imposes data protection obligations on each subprocessor equivalent to those in this agreement, and remains fully liable to the School for their performance.
8Return and deletion
At the School’s choice, Monteeno will delete or return the personal data at the end of the licence, and delete existing copies, unless required by law to retain them.
Monteeno will act on a deletion request within 30 days and confirm in writing when it is complete. Data in routine backups is overwritten in the ordinary backup cycle rather than extracted individually.
If the School gives no instruction, Monteeno will delete the School’s pupil accounts and learning records 12 months after the licence ends.
The 12-month rule is enforced automatically: a job runs every night and deletes pupil accounts and learning records once a School’s licence has been over for 12 months. A School that renews is not affected, because the rule looks for a current licence before deleting anything. Sign-in attempt records are deleted after 90 days and expired sessions after 30.
9International transfers
The database holding all pupil personal data is hosted in the United Kingdom (AWS eu-west-2, London). It was moved there from AWS us-east-1 on 24 September 2026. Pupil records processed under this agreement are not transferred outside the UK at the database layer.
Some subprocessors remain outside the UK, and the platform Monteeno contracts with has not confirmed its own transfer mechanism. Annex C marks each one. In particular the hosting platform is a United States company that has not supplied an Article 28 agreement or stated a transfer mechanism, despite being asked in writing. A School should take that into account rather than treat the move to London as settling every question.
A transfer risk assessment has been completed and is available to your data protection officer on request. Where a subprocessor is a US company, it is covered by the UK Extension to the EU-US Data Privacy Framework unless Annex C says otherwise, verified by us on the DPF register rather than taken from the provider.
The current position is set out in full on the data-protection page.
10Assistance with data subject rights
Taking into account the nature of the processing, Monteeno will assist the School by appropriate technical and organisational measures, so far as possible, in responding to requests to exercise data subject rights.
In practice: the School’s staff can view, correct and remove pupil records directly through the Monteeno interface. Where a request cannot be met that way, Monteeno will provide an export or perform a deletion on the School’s instruction within 30 days and at no charge.
If a data subject contacts Monteeno directly about data processed for the School, Monteeno will not respond substantively but will refer them to the School and tell the School promptly.
11Assistance with security, breaches and DPIAs
Monteeno will assist the School in complying with its obligations under Articles 32 to 36 UK GDPR, taking into account the nature of processing and the information available to it.
Monteeno will notify the School without undue delay and in any event within 48 hours of becoming aware of a personal data breach affecting the School’s data, and will provide the information the School needs to meet its own notification duties.
12Information and audit
Monteeno will make available to the School the information necessary to demonstrate compliance with this agreement, and allow for and contribute to audits, including inspections, conducted by the School or an auditor it mandates.
In the first instance Monteeno will respond to written questions and security questionnaires. An on-site or technical audit may be requested on reasonable notice, no more than once a year unless required by a regulator or following a breach.
13Liability and governing law
This agreement is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
Liability between the parties is deliberately left to be agreed rather than asserted here. Nothing in this agreement limits either party’s obligations or liability to data subjects or to the Information Commissioner under UK data protection law, which cannot be contracted out of in any event.
Annex A — Details of processing
Subject matter
Provision of the Monteeno financial education platform to pupils and staff of the School.
Duration
The period of the School’s licence, plus the deletion period in clause 8.
Nature and purpose
Creating and authenticating accounts; delivering lessons; recording completion; marking quizzes and applying the pass mark; issuing certificates; presenting progress to the School’s staff; providing support.
Categories of data subject
- Pupils at the School for whom the School creates accounts
- Staff at the School who administer or use the licence
Types of personal data — pupils
- Name, as entered by the School
- A username generated from that name
- A class or year-group label, where the School supplies one
- A password, stored only as a bcrypt hash
- Learning record: lessons and modules completed, quiz attempts with scores and results, game attempts, points, activity streaks
- Authentication records: active sessions and sign-in attempts
Types of personal data — school staff
- Name, work email address, role at the School, and a hashed password
Annex B — Technical and organisational measures
In place:
- Passwords stored as bcrypt hashes; never stored or transmitted in readable form
- Session tokens held in signed, HttpOnly, Secure, SameSite=Strict cookies, so they cannot be read by page scripts
- HTTPS enforced site-wide with HSTS (one year, including subdomains)
- Content Security Policy and MIME-sniffing protection on all responses
- Encrypted connections between application and database
- Role checks on every school endpoint, scoping every query to the caller’s own school so one school’s staff cannot read or alter another’s pupil records
- Pupils hold no email address, removing email-based account takeover and password-reset attack routes entirely
- Resetting a pupil’s password terminates all of that pupil’s sessions
- No advertising, tracking pixels or third-party analytics on pupil-facing pages
Not in place, disclosed rather than omitted:
- Cyber Essentials certification
- ISO 27001 certification
- Independent penetration testing
- Multi-factor authentication on staff accounts
Annex C — Authorised subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| Neon | Application database holding all account and learning records | AWS eu-west-2, London, United Kingdom. Moved from us-east-1 on 24 September 2026 and verified against the running database |
| Amazon Web Services | Underlying infrastructure for the database, and content delivery | London (eu-west-2) for the database. AWS is a United States company and content delivery uses global edge locations, so it remains covered by the UK Extension to the EU-US Data Privacy Framework (Amazon Web Services, Inc., a covered entity of the Amazon.com, Inc. certification; Active on the DPF register) |
| Floot | Platform the application runs on, including sign-in infrastructure and file storage | United States company. No transfer mechanism stated in its published terms; requested in writing |
| Resend | Email to school staff. No email is sent to pupils | United States company; sending region not yet confirmed |
| Bunny.net | Lesson video delivery; receives the viewer’s IP address to serve the video | Not yet confirmed in writing |
| Google Fonts | Serves the site’s typefaces. The pupil’s browser fetches the font files directly, so Google receives an IP address and browser details. No account or learning data is sent and no cookie is set | Google LLC, United States. Certified under the UK Extension to the EU-US Data Privacy Framework |
Stripe processes payments for parent purchases only. It is not used for school licences and receives no pupil data, so it is not a subprocessor under this agreement.
