Tally Reading: legal & compliance

Data Processing Agreement

Data Processing Agreement

Between the School (as Controller) and Tally Reading (as Processor)

Version: 1.0

Effective Date: This Agreement takes effect on the date the School begins using Tally Reading (the subscription start date).


Table of Contents

  1. Definitions and Interpretation
  2. Scope and Duration
  3. Nature and Purpose of Processing
  4. Categories of Data Subjects
  5. Types of Personal Data
  6. Processor Obligations
  7. Sub-processor Management
  8. International Transfers
  9. Security Measures
  10. Data Breach Notification
  11. Liability
  12. Term and Termination
  13. General Provisions
  14. Signatures
  15. Schedule 1 -- Technical and Organisational Security Measures
  16. Schedule 2 -- Approved Sub-processors

Parties

Controller:

Name of School: ————————————————

Address: ————————————————

Contact Name: ————————————————

Contact Email: ————————————————

(hereinafter referred to as the "Controller" or "School")

Processor:

Scratch IT LTD

Company Registration Number: 08151576

Contact Name: Sam Castillo

Contact Email: privacy@tallyreading.uk

Website: https://tallyreading.uk

(hereinafter referred to as the "Processor" or "Tally Reading")

Each a "Party" and together the "Parties".


1. Definitions and Interpretation

1.1 In this Agreement, unless the context otherwise requires, the following terms shall have the meanings set out below:

"Applicable Data Protection Law" means (a) the UK General Data Protection Regulation (UK GDPR), being the retained EU law version of Regulation (EU) 2016/679 as it forms part of the law of England and Wales, Scotland, and Northern Ireland by virtue of section 3 of the European Union (Withdrawal) Act 2018, as amended by the Data Protection, Privacy and Electronic Communications (Amendments etc) (EU Exit) Regulations 2019; and (b) the Data Protection Act 2018 (DPA 2018); and any successor legislation, regulations, or statutory instruments amending or replacing the same.

"Controller" has the meaning given in Article 4(7) of the UK GDPR: the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data. In this Agreement, the Controller is the School.

"Data Subject" has the meaning given in Article 4(1) of the UK GDPR: an identified or identifiable natural person to whom personal data relates. In the context of this Agreement, Data Subjects include students (children) and school staff.

"DPIA" means a Data Protection Impact Assessment as described in Article 35 of the UK GDPR.

"IDTA" means the International Data Transfer Agreement issued by the Information Commissioner's Office under section 119A of the Data Protection Act 2018.

"Information Commissioner" or "ICO" means the UK Information Commissioner, being the supervisory authority for the purposes of the UK GDPR.

"Personal Data" has the meaning given in Article 4(1) of the UK GDPR: any information relating to an identified or identifiable natural person (Data Subject).

"Personal Data Breach" has the meaning given in Article 4(12) of the UK GDPR: a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored, or otherwise processed.

"Processing" (and its cognates, including "Process" and "Processed") has the meaning given in Article 4(2) of the UK GDPR: any operation or set of operations which is performed on personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure, or destruction.

"Processor" has the meaning given in Article 4(8) of the UK GDPR: a natural or legal person, public authority, agency, or other body which processes personal data on behalf of the Controller. In this Agreement, the Processor is Tally Reading.

"Service Agreement" means the subscription agreement or terms of service between the Controller and the Processor for the provision of the Tally Reading service, under which this Agreement supplements the data protection obligations.

"Services" means the Tally Reading student reading tracking and management platform, as described in the Service Agreement and Section 3 of this Agreement.

"Sub-processor" means any third party appointed by the Processor (or by any other Sub-processor of the Processor) to process Personal Data on behalf of the Controller in connection with the Services.

"UK Adequacy Decision" means a decision made by the Secretary of State under section 17A of the Data Protection Act 2018 that a country, territory, sector, or international organisation ensures an adequate level of protection for personal data.

1.2 Terms defined in the UK GDPR or the Data Protection Act 2018 shall, where used in this Agreement, have the same meaning as in those enactments unless otherwise defined herein.

1.3 References to "Articles" are to Articles of the UK GDPR unless otherwise stated.

1.4 The headings in this Agreement are for convenience only and shall not affect its interpretation.


2. Scope and Duration

2.1 This Agreement sets out the terms on which the Processor shall process Personal Data on behalf of the Controller in connection with the provision of the Services, and supplements the Service Agreement between the Parties.

2.2 This Agreement applies to all Personal Data processed by the Processor on behalf of the Controller in connection with the Services.

2.3 The duration of this Agreement shall be coterminous with the Service Agreement. This Agreement shall commence on the Effective Date stated above and shall continue for so long as the Processor processes Personal Data on behalf of the Controller, including any period following termination of the Service Agreement during which the Processor retains Personal Data for the purposes set out in Section 12 (Term and Termination).

2.4 In the event of any conflict between the terms of this Agreement and the terms of the Service Agreement as they relate to the processing of Personal Data, the terms of this Agreement shall prevail.


3. Nature and Purpose of Processing

3.1 The Processor shall process Personal Data solely for the purpose of providing the Services to the Controller, which comprise the Tally Reading student reading tracking and management platform. The nature and purpose of the processing includes, but is not limited to:

(a) Reading progress tracking -- recording and managing individual student reading sessions, including books read, reading levels, and session details;

(b) Session logging -- storing records of reading activity including dates, durations, and teacher observations;

(c) Book recommendations -- generating personalised book suggestions based on student reading level, preferences, and reading history, which may involve the use of artificial intelligence services;

(d) Reporting and analytics -- producing reports on individual and class-level reading progress, reading streaks, and attainment for use by school staff;

(e) Class management -- organising students into classes and groups, assigning teachers, and managing the school's use of the platform;

(f) User account management -- creating and maintaining staff accounts for the purpose of accessing and administering the platform;

(g) Home reading register -- facilitating home reading tracking through class-wide status recording;

(h) Book library management -- maintaining the school's book catalogue, including import, search, and organisation of books.

3.2 The Processor shall not process Personal Data for any purpose other than those set out in this Section 3, unless required to do so by Applicable Data Protection Law, in which case the Processor shall, to the extent permitted by law, inform the Controller of that legal requirement before carrying out the processing.


4. Categories of Data Subjects

4.1 The Personal Data processed under this Agreement relates to the following categories of Data Subjects:

(a) Students (pupils) -- children attending the Controller's school, typically aged between 4 and 11 years. These Data Subjects are children, and the Processor acknowledges that particular care must be taken when processing children's personal data, in accordance with Recital 38 and Article 8 of the UK GDPR.

(b) School staff -- teachers, administrators, and other authorised personnel of the Controller who use the platform in the course of their professional duties.


5. Types of Personal Data

5.1 The categories of Personal Data processed in relation to students include:

(a) First name and surname;

(b) Reading level range (minimum and maximum, expressed as AR levels);

(c) Age range or year group (as implied by class assignment);

(d) Reading preferences and interests (including genre preferences);

(e) Reading history (books read, session dates, session details, enjoyment ratings);

(f) Teacher observations and notes relating to reading progress;

(g) Reading streak data (consecutive reading days);

(h) Class and group membership.

5.2 The categories of Personal Data processed in relation to school staff include:

(a) First name and surname;

(b) Email address;

(c) Role within the platform (e.g., teacher, administrator);

(d) Account credentials (stored in hashed form only; the Processor does not have access to plain-text passwords).

5.3 The Processor does not knowingly collect or process special category data (as defined in Article 9 of the UK GDPR) in connection with the Services. Should the Controller or any Data Subject include special category data within free-text fields (such as teacher notes), the Controller acknowledges that it is responsible for ensuring an appropriate lawful basis for such processing.


6. Processor Obligations

The Processor shall, in relation to the processing of Personal Data under this Agreement:

6.1 Controller Instructions

6.1.1 Process the Personal Data only on documented instructions from the Controller, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Applicable Data Protection Law to which the Processor is subject, in which case the Processor shall, to the extent permitted by law, inform the Controller of that legal requirement before the relevant processing of that Personal Data (Article 28(3)(a)).

6.1.2 Immediately inform the Controller if, in the Processor's opinion, an instruction from the Controller infringes Applicable Data Protection Law (Article 28(3), final sub-paragraph).

6.2 Confidentiality

6.2.1 Ensure that all persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (Article 28(3)(b)).

6.2.2 Ensure that access to Personal Data is limited to those personnel who require access in order to perform the Services, and that such personnel are appropriately trained in data protection.

6.3 Security Measures

6.3.1 Implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, and the nature, scope, context, and purposes of processing, as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, in accordance with Article 32.

6.3.2 The specific technical and organisational security measures implemented by the Processor are set out in Schedule 1 to this Agreement.

6.3.3 The Processor shall regularly test, assess, and evaluate the effectiveness of the technical and organisational measures for ensuring the security of the processing (Article 32(1)(d)).

6.4 Sub-processors

6.4.1 The Processor shall not engage another processor (Sub-processor) without prior specific or general written authorisation of the Controller, in accordance with Article 28(2).

6.4.2 Where the Controller has given general written authorisation (which shall be deemed given by signature of this Agreement in respect of the Sub-processors listed in Schedule 2), the Processor shall inform the Controller of any intended changes concerning the addition or replacement of Sub-processors, thereby giving the Controller the opportunity to object to such changes, in accordance with Section 7 of this Agreement.

6.4.3 Where the Processor engages a Sub-processor, the Processor shall impose the same data protection obligations as set out in this Agreement on that Sub-processor by way of a contract or other legal act, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the UK GDPR (Article 28(4)).

6.4.4 The Processor shall remain fully liable to the Controller for the performance of any Sub-processor's obligations under such contract.

6.5 Data Subject Rights

6.5.1 Taking into account the nature of the processing, assist the Controller by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Controller's obligation to respond to requests for exercising the Data Subject's rights laid down in Chapter III of the UK GDPR (Articles 15-22), including rights of access, rectification, erasure, restriction, data portability, and objection (Article 28(3)(e)).

6.5.2 Where the Processor receives a request from a Data Subject directly, it shall promptly notify the Controller and shall not respond to the Data Subject directly unless authorised to do so by the Controller.

6.6 Assistance with Compliance Obligations

6.6.1 Taking into account the nature of the processing and the information available to the Processor, assist the Controller in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the UK GDPR, including in particular:

(a) The obligation to implement appropriate security measures (Article 32);

(b) The obligation to notify a Personal Data Breach to the Information Commissioner (Article 33);

(c) The obligation to communicate a Personal Data Breach to the Data Subject (Article 34);

(d) The obligation to carry out a Data Protection Impact Assessment (Article 35);

(e) The obligation to consult the Information Commissioner prior to processing where a DPIA indicates that processing would result in a high risk (Article 36).

6.7 Deletion or Return of Data

6.7.1 At the choice of the Controller, the Processor shall delete or return all Personal Data to the Controller after the end of the provision of Services, and shall delete existing copies unless Applicable Data Protection Law requires storage of the Personal Data (Article 28(3)(g)).

6.7.2 The Processor shall carry out such deletion or return within thirty (30) calendar days of the termination or expiry of the Service Agreement, or within thirty (30) calendar days of receipt of the Controller's written instructions to delete or return, whichever is later.

6.7.3 Upon request by the Controller, the Processor shall provide written certification that all Personal Data has been securely destroyed in accordance with this Section 6.7.

6.7.4 The Controller acknowledges that the Processor may retain anonymised or aggregated data (from which no individual Data Subject can be identified) beyond the period specified in this section, for the purpose of service improvement and statistical analysis.

6.8 Audit and Compliance

6.8.1 Make available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the UK GDPR (Article 28(3)(h)).

6.8.2 Allow for and contribute to audits, including inspections, conducted by the Controller or another auditor mandated by the Controller (Article 28(3)(h)). Such audits shall be subject to the following conditions:

(a) The Controller shall give the Processor reasonable prior written notice of any audit (not less than thirty (30) calendar days, except in the case of an audit required by the Information Commissioner or following a Personal Data Breach, in which case reasonable notice shall be given);

(b) Audits shall be conducted during normal business hours and shall not unreasonably interfere with the Processor's business operations;

(c) The Controller shall bear its own costs in connection with any audit;

(d) The Controller's auditor shall be bound by appropriate confidentiality obligations;

(e) The Processor may satisfy audit requests by providing relevant third-party certifications, audit reports, or compliance documentation where available (such as SOC 2 reports from Sub-processors).


7. Sub-processor Management

7.1 The Controller hereby provides general written authorisation for the Processor to engage the Sub-processors listed in Schedule 2 to this Agreement as at the date of execution.

7.2 The Processor shall give the Controller prior written notice of the appointment of any new Sub-processor or the replacement of an existing Sub-processor, including full details of the processing to be undertaken by the Sub-processor. Such notice shall be given at least thirty (30) calendar days before the new Sub-processor commences processing of Personal Data.

7.3 The Controller may object to the appointment of a new Sub-processor by providing written notice to the Processor within the thirty (30) calendar day notice period set out in Section 7.2. Such objection must be on reasonable grounds relating to the protection of Personal Data.

7.4 If the Controller objects to the appointment of a new Sub-processor, the Parties shall discuss the Controller's concerns in good faith with a view to achieving a commercially reasonable resolution. If no resolution can be reached within a further thirty (30) calendar days, either Party may terminate the Service Agreement (and this Agreement) upon written notice, without penalty.

7.5 The Processor shall ensure that each Sub-processor is bound by data protection obligations no less onerous than those set out in this Agreement, and the Processor shall remain fully liable to the Controller for the acts and omissions of its Sub-processors.

7.6 An up-to-date list of Sub-processors shall be maintained by the Processor and made available to the Controller on request. The current list is set out in Schedule 2.


8. International Transfers

8.1 The Processor shall not transfer Personal Data to a country outside the United Kingdom unless:

(a) The transfer is to a country, territory, sector, or international organisation that is the subject of a UK Adequacy Decision; or

(b) Appropriate safeguards are in place in accordance with Article 46 of the UK GDPR, including but not limited to the International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses; or

(c) A derogation under Article 49 of the UK GDPR applies; or

(d) The Controller has given prior written consent to the transfer.

8.2 Where a transfer is made in reliance on appropriate safeguards under Article 46, the Processor shall ensure that the relevant transfer mechanism is in place before the transfer occurs and shall provide a copy to the Controller upon request.

8.3 The Parties acknowledge that the following international transfers take place in connection with the Services:

(a) Cloudflare, Inc. (United States) -- The Processor's infrastructure provider. The Tally Reading platform is hosted on Cloudflare's edge network and data storage services (including Cloudflare Workers, D1 database, KV storage, and R2 object storage). Cloudflare processes Personal Data as a Sub-processor. Data may be processed in the United States and other jurisdictions in which Cloudflare operates. Cloudflare maintains appropriate safeguards including the UK International Data Transfer Agreement (IDTA) and implements technical measures as described in its Data Processing Addendum.

(b) AI Service Providers (United States) -- Where the book recommendations feature is enabled, limited Personal Data (reading level range, genre preferences, and reading history summary, but not student names or other directly identifying information) may be transmitted to AI service providers (such as Anthropic, OpenAI, or Google) for the purpose of generating personalised book recommendations. These providers process data as Sub-processors and are listed in Schedule 2.

8.4 The Processor shall carry out a transfer impact assessment where required by Applicable Data Protection Law and shall implement supplementary measures where necessary to ensure that the level of protection afforded to Personal Data is not undermined by the transfer.


9. Security Measures

9.1 The Processor shall implement and maintain the technical and organisational security measures set out in Schedule 1 to this Agreement, in accordance with Article 32 of the UK GDPR.

9.2 The Processor shall take into account the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored, or otherwise processed.

9.3 In assessing the appropriate level of security, the Processor shall take particular account of the fact that the Personal Data processed includes children's data, and shall implement measures appropriate to the heightened level of protection required for such data.

9.4 The security measures set out in Schedule 1 represent the minimum standard of security to be maintained by the Processor. The Processor may update and enhance these measures from time to time, provided that the overall level of security is not diminished. The Processor shall notify the Controller of any material changes to the security measures.


10. Data Breach Notification

10.1 The Processor shall notify the Controller without undue delay and in any event within twenty-four (24) hours of becoming aware of a Personal Data Breach affecting the Controller's Personal Data.

10.2 Such notification shall include, to the extent reasonably available at the time of notification:

(a) A description of the nature of the Personal Data Breach, including where possible the categories and approximate number of Data Subjects concerned, and the categories and approximate number of Personal Data records concerned (Article 33(3)(a));

(b) The name and contact details of the Processor's data protection contact from whom further information may be obtained (Article 33(3)(b));

(c) A description of the likely consequences of the Personal Data Breach (Article 33(3)(c));

(d) A description of the measures taken or proposed to be taken by the Processor to address the Personal Data Breach, including, where appropriate, measures to mitigate its possible adverse effects (Article 33(3)(d)).

10.3 Where it is not possible to provide all of the information referred to in Section 10.2 at the time of the initial notification, the Processor shall provide the information in phases, without further undue delay.

10.4 The Processor shall cooperate with the Controller and take all reasonable steps as are directed by the Controller to assist in the investigation, mitigation, and remediation of any Personal Data Breach.

10.5 The Processor shall document all Personal Data Breaches, including the facts relating to the breach, its effects, and the remedial action taken, and shall make such documentation available to the Controller and, where applicable, the Information Commissioner.

10.6 The Processor shall not inform any third party of any Personal Data Breach without first obtaining the Controller's prior written consent, unless notification is required by Applicable Data Protection Law, in which case the Processor shall, to the extent permitted by law, inform the Controller of that legal requirement.


11. Liability

11.1 Each Party's liability under or in connection with this Agreement, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, shall be subject to the limitations and exclusions of liability set out in the Service Agreement.

11.2 Nothing in this Agreement shall exclude or limit the liability of either Party for:

(a) Death or personal injury caused by its negligence;

(b) Fraud or fraudulent misrepresentation;

(c) Any other liability that cannot be excluded or limited by Applicable Data Protection Law.

11.3 The Processor shall be liable for the damage caused by processing only where it has not complied with obligations of the UK GDPR specifically directed to processors, or where it has acted outside of or contrary to the Controller's lawful instructions, in accordance with Article 82 of the UK GDPR.

11.4 Where the Processor is liable to a Data Subject for damage resulting from a breach of the UK GDPR in accordance with Article 82, the Processor shall be entitled to recover from the Controller that part of the compensation corresponding to the Controller's share of responsibility for the damage, and vice versa.

11.5 Without prejudice to Sections 11.2 and 11.3, the Processor's total aggregate liability under this Agreement shall be limited to the total fees paid or payable by the Controller under the Service Agreement in the twelve (12) months immediately preceding the event giving rise to the claim.


12. Term and Termination

12.1 This Agreement shall come into force on the Effective Date and shall continue in full force and effect for so long as the Service Agreement remains in effect, and for such additional period as may be necessary for the Processor to fulfil its obligations under Section 6.7 (Deletion or Return of Data).

12.2 This Agreement shall automatically terminate upon the termination or expiry of the Service Agreement, subject to Section 12.1.

12.3 Either Party may terminate this Agreement immediately by written notice to the other Party if:

(a) The other Party commits a material breach of this Agreement and (where such breach is capable of remedy) fails to remedy it within thirty (30) calendar days of receiving written notice to do so;

(b) The other Party is unable to comply with its obligations under this Agreement due to a change in Applicable Data Protection Law;

(c) In the circumstances described in Section 7.4 (unresolved Sub-processor objection).

12.4 The obligations of the Processor under Sections 6.2 (Confidentiality), 6.7 (Deletion or Return of Data), 6.8 (Audit and Compliance), 10 (Data Breach Notification), and 11 (Liability) shall survive the termination or expiry of this Agreement.


13. General Provisions

13.1 Entire Agreement. This Agreement, together with the Service Agreement and its schedules, constitutes the entire agreement between the Parties relating to the processing of Personal Data and supersedes all previous agreements, arrangements, and understandings between the Parties in respect of the same, whether written or oral.

13.2 Amendments. This Agreement may only be amended by a written instrument signed by both Parties.

13.3 Severability. If any provision of this Agreement is found by any court or administrative body of competent jurisdiction to be invalid or unenforceable, such invalidity or unenforceability shall not affect the other provisions of this Agreement, which shall remain in full force and effect.

13.4 No Waiver. No failure or delay by either Party in exercising any right or remedy under this Agreement shall operate as a waiver of that right or remedy, nor shall any single or partial exercise of any right or remedy preclude any further exercise of that or any other right or remedy.

13.5 Third Party Rights. A person who is not a Party to this Agreement shall not have any rights under the Contracts (Rights of Third Parties) Act 1999 to enforce any term of this Agreement.

13.6 Governing Law and Jurisdiction. This Agreement shall be governed by and construed in accordance with the laws of England and Wales, and the Parties submit to the exclusive jurisdiction of the courts of England and Wales.

13.7 Notices. All notices under this Agreement shall be in writing and shall be sent by email to the contact addresses specified at the head of this Agreement, or to such other address as the relevant Party may notify in writing from time to time.

13.8 Counterparts. This Agreement may be executed in counterparts, each of which shall be deemed to be an original, and all of which together shall constitute one and the same agreement.


14. Signatures

This Agreement has been entered into on the date stated above.

Signed for and on behalf of the Controller:

Name:————————————————
Position:————————————————
School:————————————————
Signature:————————————————
Date:————————————————

Signed for and on behalf of the Processor:

Name:Sam Castillo
Position:Director
Organisation:Scratch IT LTD
Signature:————————————————
Date:————————————————

Schedule 1 -- Technical and Organisational Security Measures

This Schedule describes the technical and organisational security measures implemented by the Processor in accordance with Article 32 of the UK GDPR. For the avoidance of doubt, the measures listed below represent the minimum standard to be maintained, and the Processor may implement additional measures from time to time.

1. Authentication and Access Control

MeasureDescription
Password hashingPBKDF2 with 100,000 iterations using cryptographically secure random salts. Plain-text passwords are never stored or logged.
Encryption of secretsAPI keys and other secrets are encrypted at rest using AES-GCM.
Role-based access controlFour-tier role hierarchy (Owner, Admin, Teacher, Readonly) with permission enforcement at the application layer. Each role is restricted to a defined set of operations.
Token-based authenticationJWT access tokens (15-minute expiry) with refresh tokens (7-day expiry). Tokens are automatically rotated prior to expiry.
Rate limitingAuthentication endpoints are subject to rate limiting to prevent brute-force attacks, with attempt counts stored per-user.

2. Data Isolation and Multi-Tenancy

MeasureDescription
Organisation-scoped queriesAll database queries are scoped to the authenticated organisation, enforced by middleware. No cross-tenant data access is possible through the application layer.
Tenant middlewareA dedicated middleware layer injects and enforces organisation context on every authenticated request.
Soft deleteDeactivated organisations and user accounts are soft-deleted (marked inactive) rather than hard-deleted, preventing accidental data loss while allowing recovery.

3. Transport Security

MeasureDescription
TLS encryptionAll data in transit is encrypted using TLS 1.2 or higher, enforced by the infrastructure provider (Cloudflare).
HSTSHTTP Strict Transport Security headers are applied to all responses, preventing protocol downgrade attacks.
Security headersAdditional security headers are applied, including Content Security Policy (CSP), X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.

4. Infrastructure Security

MeasureDescription
Edge hostingThe platform is hosted on Cloudflare's global edge network, benefiting from Cloudflare's enterprise-grade DDoS protection, Web Application Firewall, and network security.
Serverless architectureThe application runs on Cloudflare Workers (serverless), eliminating the need to manage or patch servers and reducing the attack surface.
Database encryptionData at rest in Cloudflare D1 is encrypted using Cloudflare's encryption at rest capabilities.

5. Application Security

MeasureDescription
Input validationAll user inputs are validated and sanitised before processing.
Error handlingA global error handler sanitises all 5xx error responses to prevent leakage of internal system details.
Audit loggingAdministrative actions are logged for audit trail purposes, including the user, action, and timestamp.
CORS policyCross-Origin Resource Sharing is restricted to explicitly whitelisted domains.

6. Data Minimisation

MeasureDescription
AI recommendationsWhen generating book recommendations, only non-identifying data is sent to AI providers (reading level, genre preferences, and reading history summary). Student names and other directly identifying information are not transmitted.
No special category dataThe platform is not designed to collect or process special category data. Free-text fields are provided for teacher observations but are not intended for recording sensitive personal characteristics.

7. Organisational Measures

MeasureDescription
Confidentiality obligationsAll personnel with access to Personal Data are subject to confidentiality obligations.
Access on need-to-know basisAccess to production systems and data is limited to authorised personnel who require it for the performance of their duties.
Incident responseThe Processor maintains an incident response procedure for identifying, containing, and reporting Personal Data Breaches.
Regular reviewSecurity measures are reviewed and updated on a regular basis to reflect changes in technology, threats, and Applicable Data Protection Law.

Schedule 2 -- Approved Sub-processors

The following Sub-processors are approved by the Controller as at the date of this Agreement:

Sub-processorRegistered CountryProcessing ActivityData ProcessedTransfer Mechanism
Cloudflare, Inc.United StatesInfrastructure hosting, content delivery, database storage (D1), key-value storage (KV), object storage (R2), edge compute (Workers)All Personal Data processed through the platformUK IDTA / Cloudflare DPA
Anthropic, PBCUnited StatesAI book recommendation generation (where enabled by Controller)Reading level, genre preferences, reading history summary (no names or directly identifying data)UK IDTA / Anthropic DPA
OpenAI, Inc.United StatesAI book recommendation generation (where enabled by Controller)Reading level, genre preferences, reading history summary (no names or directly identifying data)UK IDTA / OpenAI DPA
Google LLCUnited StatesAI book recommendation generation (where enabled by Controller)Reading level, genre preferences, reading history summary (no names or directly identifying data)UK IDTA / Google DPA
Open Library (Internet Archive)United StatesBook metadata and cover image retrievalBook titles, authors, ISBNs (no student Personal Data)Publicly available API; no student Personal Data transferred

Notes:

  1. AI service providers are only engaged when the book recommendations feature is actively used by the Controller. The Controller may choose which AI provider (if any) is enabled through the platform configuration.

  2. Open Library is used solely for retrieving publicly available book metadata (titles, authors, cover images, ISBNs). No student Personal Data is transmitted to this service.

  3. The Processor will notify the Controller of any changes to this list in accordance with Section 7 of this Agreement.


END OF AGREEMENT