Data processing agreement

Last updated 21 November 2026

This agreement is between the school or trust that uses ReproFlow (the “school”, the controller) and E-Tech Ltd, company number 03017834 (“we”, the processor). It forms part of the terms of use and is accepted by the school's admin on its behalf. It meets the requirements of Article 28(3) of the UK GDPR. If it conflicts with the terms of use, this agreement takes priority on data protection matters.

1. Our role

The school is the controller of the personal data processed in ReproFlow, and we are its processor. The details of the processing are set out in Annex 1.

2. What we will do

  1. Instructions. We will process personal data only on the school's documented instructions. These are this agreement, the terms of use, and the settings and actions of the school's admins in ReproFlow. The only exception is where the law requires otherwise, in which case we will tell the school first unless the law forbids it. We will tell the school if we think an instruction breaks data protection law.
  2. Confidentiality. Everyone we authorise to process the data is bound by a duty of confidentiality.
  3. Security. We will apply appropriate technical and organisational measures under Article 32 of UK GDPR, including those in Annex 2, and review them regularly.
  4. Sub-processors. See section 3.
  5. Data subject requests. We will help the school respond to requests from staff to exercise their rights. If a request comes to us, we will pass it to the school without undue delay and won't answer it ourselves unless the school asks us to.
  6. Other assistance. Taking into account the nature of the processing and the information we hold, we will help the school meet its obligations on security, breach notification, data protection impact assessments and prior consultation with the ICO. Our DPIA support pack is available to help with this.
  7. Deletion or return. See section 6.
  8. Information and audits. We will give the school the information it reasonably needs to show compliance with Article 28. We will allow and contribute to audits by the school or an auditor it appoints, with reasonable notice, no more than once a year unless there has been a breach, and subject to confidentiality.

3. Sub-processors

The school gives general authorisation for us to use sub-processors. The current sub-processors are listed in Annex 3. We will give the school at least 30 days' notice of any new or replacement sub-processor by email to its admins. The school may object on reasonable data protection grounds. If we can't resolve the objection, the school may end the service. We will put data protection obligations equivalent to this agreement on every sub-processor in a written contract, and we remain responsible to the school for their performance.

4. International transfers

We will only transfer personal data outside the UK where the transfer is covered by UK adequacy regulations or appropriate safeguards under Article 46 of UK GDPR, such as the UK International Data Transfer Agreement or Addendum.

5. Personal data breaches

We will notify the school without undue delay, and in any case within 48 hours of becoming aware of a personal data breach affecting school data. We will tell the school, as far as we know them, what happened, the categories and approximate number of people and records affected, the likely consequences, and what we have done or propose to do. We will keep the school updated and cooperate with its investigation. The school is responsible for deciding whether to notify the ICO or the people affected.

6. When the service ends

When the school stops using ReproFlow, and at its choice, we will delete all school personal data or return it to the school (as an export of job and account records) and then delete it. We will do this within 30 days, unless the law requires us to keep it. Data in backups will be overwritten as backups expire, within [35] days.

7. The school's responsibilities

The school confirms it has a lawful basis for the processing, has given its staff the information required by Articles 13 and 14 of UK GDPR, and that its instructions comply with data protection law.

8. Liability and duration

Each party's liability under this agreement is subject to the limits in the terms of use, except where the law does not allow it to be limited. This agreement lasts for as long as we process personal data for the school.

Annex 1: Details of the processing

  • Subject matter: providing ReproFlow, a service for sending and managing school print jobs.
  • Duration: for as long as the school uses ReproFlow, then as set out in section 6.
  • Nature and purpose: storing and showing staff accounts and print jobs; signing staff in through Google; letting the Repro team print, query and hand over jobs; letting admins approve and manage staff; sending email notifications; keeping an admin activity log; deleting data on the schedule below.
  • Categories of data subjects: school staff who use ReproFlow, people invited to use it, and anyone (including pupils) whose personal data appears in files or messages that staff send.
  • Categories of personal data: names, school email addresses, Google account IDs, roles, departments, account status and approval details, last activity time, notification preferences, print job details and messages, job history, uploaded documents and their contents, and admin activity records.
  • Special category data: none is needed for the service. Uploaded documents could contain it if staff send it. The school decides whether that is allowed and tells its staff.
  • Retention: uploaded files are deleted 7 days (or the period the school sets) after a job is collected, dropped off, cancelled or rejected; unsent uploads after 24 hours; finished jobs with their messages and history after 6 months; deleted jobs after 30 days; removed staff accounts are anonymised after 30 days; declined account requests are deleted after 90 days; invitations after 90 days; and admin activity records after 24 months. The school may ask us for different periods.

Annex 2: Security measures

  • Sign-in only through the school's Google Workspace. ReproFlow holds no passwords, personal Google accounts are rejected, and new accounts need an admin's approval.
  • Role-based access (teacher, Repro staff, admin), checked on the server for every request. Each school's data is kept separate in every query.
  • Encrypted connections (HTTPS) in transit, encrypted session cookies, protection against cross-site request forgery, and rate limiting.
  • Data minimisation: files are deleted automatically, and accounts unused for 6 months are flagged to admins for review.
  • A log of admin actions such as approvals, removals and sign-in domain changes.
  • Additional sign-in domains have to be confirmed by someone with an email address on that domain.
  • Access to production systems is limited to our authorised staff, with strong, unique credentials and multi-factor authentication.
  • Software dependencies are kept up to date, and security fixes are applied promptly.

Annex 3: Sub-processors

  • Hostinger: Hosts the ReproFlow servers, database and uploaded files. Location: the United Kingdom.
  • Postmark (ActiveCampaign, LLC): Sends ReproFlow emails, such as job updates, approvals and daily summaries. Location: United States, under the UK Extension to the EU–US Data Privacy Framework.

Google sign-in is provided by the school's own Google Workspace under the school's agreement with Google, so Google is not our sub-processor.

Contact

Data protection queries and breach contacts: info@reproflow.co.uk.