DPIA support pack

Last updated 21 November 2026

Your school is the controller for the personal data in ReproFlow, so any data protection impact assessment (DPIA) is yours to carry out. This pack gives the information you'll need, laid out to follow the ICO's sample DPIA template. Copy what's useful into your own template, complete the parts marked for the school, and ask your data protection officer to review it. To keep a copy, print this page or save it as a PDF.

It should be read with the privacy notice and the data processing agreement. If you need anything else, email info@reproflow.co.uk.

1. Is a DPIA needed?

ReproFlow isn't likely to be high risk: it handles staff work details and print jobs, makes no automated decisions about people and doesn't monitor staff. But uploaded files may contain personal data about pupils, who are vulnerable data subjects, so many schools choose to do a DPIA as good practice. Whether one is required is the school's decision.

2. The processing

Nature

  • Staff sign in with their school Google account and send print jobs (settings, copies, deadline, notes and files) to the school's reprographics team.
  • The Repro team views, prints and hands over jobs, and can message the member of staff about a job.
  • School admins approve new accounts, assign roles and departments, and manage settings.
  • Email notifications about jobs and approvals are sent if the school turns them on.
  • Data is collected from Google (name, email address, Google ID), from staff themselves and from admins.

Scope

  • People: school staff who use ReproFlow, people invited to use it, and anyone (often pupils) named in uploaded files or messages.
  • Data: names, school email addresses, Google IDs, roles, departments, account status, last activity, notification settings, print job details, messages, job history, uploaded documents and admin activity records.
  • Special category data: none is needed. It could appear in uploaded files if staff send it.
  • Volume: usually every member of staff who prints, and a few thousand jobs a year, depending on the size of the school.
  • Location: stored in the United Kingdom. Emails are sent through a provider in the United States (see section 4).

Context

  • Staff would expect their school to use their work details to manage printing. ReproFlow replaces emailing files or leaving them on shared drives and USB sticks.
  • Pupils are not users and never have accounts.
  • ReproFlow is run by E-Tech Ltd, which is registered with the ICO (ZB666410).

Purposes

To let staff send print jobs and follow their progress, let the Repro team manage the workload, let admins control who has access, and give the school a record of printing. The benefit is fewer lost or misprinted jobs and less personal data left in inboxes, on shared drives and on USB sticks.

3. Consultation

For the school to complete. For example, record any views from your DPO, IT staff, the reprographics team and staff representatives. We can answer technical questions on request.

4. Necessity and proportionality

  • Lawful basis: the school's choice, usually public task (Article 6(1)(e)) or legitimate interests (Article 6(1)(f)). Consent is not relied on.
  • Data minimisation: only the details needed to sign in and route jobs are collected. Files are deleted automatically once a job is finished.
  • Transparency: the ReproFlow privacy notice is shown at sign-in. Mention ReproFlow in your staff privacy notice too.
  • Rights: requests go to the school, and we help it respond under the data processing agreement.
  • Processor: an Article 28 data processing agreement is accepted by an admin on the school's behalf.
  • Sub-processors and transfers:
    • 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.
  • Retention: applied automatically. See the privacy notice for each period.

5. Risks and how they are reduced

Likelihood and severity are our suggested ratings for the risk before measures are applied, using the ICO's scales. Adjust them to suit your school.

Risk 1: Personal data about pupils in uploaded files

Staff upload worksheets, class lists or seating plans that name pupils, possibly including special category data such as SEN or medical information.

Likelihood: Possible. Severity: Significant. Residual risk after measures: Low.

What ReproFlow does:

  • Files are deleted automatically 7 days after a job is finished (the school can shorten this), and unsent uploads after 24 hours.
  • Only the uploader and the school's Repro team can open a job's files.
  • The terms of use tell staff to include only the personal data a job needs and not to send special category data unless the school allows it.

What the school should do: Tell staff what may be uploaded, for example in your data protection or acceptable use policy.

Risk 2: Someone gets access who shouldn't

A person outside the school, or a member of staff who has left, signs in and sees jobs or files.

Likelihood: Remote. Severity: Significant. Residual risk after measures: Low.

What ReproFlow does:

  • Sign-in only through the school's Google Workspace. Personal Google accounts are rejected and ReproFlow holds no passwords.
  • Every new account needs an admin's approval, and additional sign-in domains must be confirmed from that domain.
  • Accounts unused for 6 months are flagged to admins, and removed accounts are anonymised after 30 days.
  • Suspending a Google account in Workspace also stops sign-in to ReproFlow.

What the school should do: Include ReproFlow in your leavers process, and keep Google Workspace security (such as 2-step verification) in place.

Risk 3: Staff see more than their role needs

A teacher sees other staff's jobs, or another school sees this school's data.

Likelihood: Remote. Severity: Minimal. Residual risk after measures: Low.

What ReproFlow does:

  • Role-based access (teacher, Repro staff, admin) is checked on the server for every request.
  • Each school's data is kept separate in every query, and teachers only see their own jobs.
  • Admin actions such as approvals, removals and role changes are logged.

What the school should do: Give admin and Repro roles only to the people who need them, and review them each year.

Risk 4: Data kept longer than needed

Old jobs, files and accounts build up over time.

Likelihood: Remote. Severity: Minimal. Residual risk after measures: Low.

What ReproFlow does:

  • Retention is applied automatically every day: finished jobs after 6 months, deleted jobs after 30 days, declined requests after 90 days, invitations after 90 days and the admin log after 24 months.
  • When the school stops using ReproFlow, its data is deleted or returned within 30 days.

What the school should do: Check the periods fit your retention schedule, and set the file retention period in ReproFlow's settings.

Risk 5: Printed copies collected by the wrong person

A finished job containing personal data is picked up by someone else.

Likelihood: Possible. Severity: Minimal. Residual risk after measures: Low.

What ReproFlow does:

  • Jobs are handed over at a named collection point, and the system records who collected them and when.

What the school should do: Keep collection points supervised or secure, especially for jobs containing pupil information.

Risk 6: A breach at ReproFlow or a sub-processor

A security incident exposes school data.

Likelihood: Remote. Severity: Significant. Residual risk after measures: Low.

What ReproFlow does:

  • Data is encrypted in transit, with protection against cross-site request forgery and rate limiting.
  • Sub-processors are bound by written data protection terms, and transfers outside the UK have appropriate safeguards.
  • We will notify the school within 48 hours of becoming aware of a breach and help with its response.

What the school should do: Add ReproFlow to your breach log procedures and information asset register.

6. Sign-off

For the school to complete: measures approved by, residual risks approved by, DPO advice and whether it was followed, and a date to review the DPIA (for example each year, or when ReproFlow notifies you of a material change).