Data processing agreement
Licence agreement · Managed hosting terms · Data processing agreement · Privacy notice
Draft for legal review. This agreement has been drafted and reviewed internally but has not yet been approved by a qualified solicitor. It must not be relied on until that sign-off is done and the details in square brackets are completed. Version 0.3, [date].
About this agreement
This data processing agreement sets out the terms required by Article 28 of the UK GDPR for personal data that [Company name] Limited ("we", the processor) processes on behalf of a nursery organisation ("you", the controller). It forms part of:
- our Managed hosting terms, for the whole time we host Wrennery for you; and
- our Licence agreement, whenever you give us access to Customer Data on your own server, for example for installation, support, a data move or training.
Words defined in those terms have the same meaning here. "UK GDPR", "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meanings in the UK GDPR and the Data Protection Act 2018 ("Data Protection Law"), as amended, including by the Data (Use and Access) Act 2025.
1. Roles
1.1 You are the controller of Customer Data and we are your processor. You are responsible for having a lawful basis for the processing, for the instructions you give, for the information you give to data subjects, and for meeting the conditions in Data Protection Law for special category data and criminal offence data.
1.2 The details of the processing (its subject matter, duration, nature and purpose, the types of personal data and the categories of data subjects) are in Annex 1.
1.3 We are controller, not processor, of the limited information described in our privacy notice (such as your account contacts, invoices and licence check-ins).
2. Our obligations
We will:
- 2.1 process Customer Data only on your documented instructions, which are these terms, the Order and the use of the Software's features by your users, including for transfers outside the UK, unless the law requires otherwise (in which case we will tell you first, unless the law forbids that);
- 2.2 tell you promptly if we think an instruction breaches Data Protection Law;
- 2.3 ensure that everyone we authorise to process Customer Data is bound by confidentiality, has had data protection training, and, where they may access children's records, has been through checks appropriate to that access [including a basic DBS check];
- 2.4 keep in place the technical and organisational measures in Annex 2, which we may improve but will not reduce;
- 2.5 not use Customer Data for any other purpose, including product development, analytics, marketing or training any artificial intelligence model, and never sell it;
- 2.6 assist you, taking into account the nature of the processing, to respond to requests from data subjects exercising their rights, mainly through the Software's own tools (subject access exports, rectification, retention and erasure), and pass on to you any request we receive directly without responding to it ourselves;
- 2.7 assist you with your obligations on security, personal data breaches, data protection impact assessments and prior consultation with the Information Commissioner, including by giving you the information about the Software you need for a DPIA;
- 2.8 notify you of a personal data breach affecting Customer Data without undue delay, and in any event within [36] hours of becoming aware of it, with the information Article 33(3) of the UK GDPR requires as far as it is then known, and keep you updated; we will not notify the Information Commissioner, data subjects or anyone else about it on your behalf without your agreement unless the law requires it;
- 2.9 tell you promptly (unless the law forbids it) if a public authority, including the police, asks us for Customer Data, and refer them to you; we will disclose Customer Data only where we are legally obliged to;
- 2.10 make available all information necessary to demonstrate compliance with this agreement and allow for and contribute to audits, as set out in clause 5.
3. Sub-processors
3.1 You authorise us to use the sub-processors listed in Annex 3.
3.2 We will give you at least 30 days' notice, by email and on this page, before adding or replacing a sub-processor. You may object on reasonable data protection grounds within that period. If we cannot address the objection, you may end the hosting without penalty and receive a refund of fees paid for the unused period.
3.3 We will impose on each sub-processor, by written contract, data protection obligations that give at least the protection of this agreement, and we remain liable to you for its performance.
4. Where Customer Data is processed
4.1 Customer Data is stored and processed in the United Kingdom [subject to confirmation of the hosting region].
4.2 We will not transfer Customer Data outside the UK except to a country covered by UK adequacy regulations, or with appropriate safeguards under Article 46 of the UK GDPR (such as the International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses), and only to the sub-processors in Annex 3.
4.3 Notifications sent to parents' and staff members' phones pass through push services operated by Apple, Google and Mozilla. Their content is encrypted from the server to the device, so those services cannot read it; they process only the information needed to deliver the notification to the device.
5. Audits
5.1 We will answer your reasonable written questions about our processing within 30 days, and provide our current security summary and any independent reports or certifications we hold.
5.2 If that information is not sufficient to show compliance, or the Information Commissioner requires it, you (or an independent auditor bound by confidentiality, who is not our competitor) may audit our processing of Customer Data once in any 12 months, on at least 30 days' notice, during working hours, without access to other customers' data. Each of us bears its own costs, unless the audit shows a material breach by us.
6. End of processing
6.1 When the hosting ends, or the support task for which we were given access is finished, we will, at your choice, return Customer Data to you (as a backup file that restores on any Wrennery installation, and in the Software's export formats) and delete it, as described in clause 8 of the Managed hosting terms. Copies in backups are deleted as those backups expire, within 12 months at most, and are kept secure and out of use until then.
6.2 We may keep Customer Data beyond that only where the law requires us to, and then only for that purpose.
7. Liability and precedence
7.1 Each party's liability under this agreement is subject to the limits in the terms it forms part of, except where Data Protection Law does not allow a limit.
7.2 If this agreement conflicts with any other terms between us about personal data, this agreement applies.
Annex 1: Details of the processing
| Subject matter | Hosting and support of Wrennery, the nursery management software you use to run your settings. |
| Duration | For as long as we host the Software for you, or have access to Customer Data for a support task, and then until deletion under clause 6. |
| Nature | Storing, hosting, backing up, restoring, securing and transmitting data entered by your users; sending email and notifications on your instructions; sending families, invoices, credit notes and payments to accounting software you connect; providing support where you ask for it. |
| Purpose | To provide the Software as a hosted service and support it, so that you can run your settings. |
| Data subjects | Children attending or applying to your settings; parents, carers and others with parental responsibility; emergency contacts and people authorised to collect children; your staff, workers, volunteers, students and job applicants; visitors; professionals involved with a child (for example social workers, health visitors and SENCOs). |
| Personal data | Identity and contact details; dates of birth; attendance, registers, sleep, meals, nappies and the daily diary; photographs and videos; learning observations and assessments, including the progress check at age two; admissions, bookings, fees, invoices, payments and funding (including funding eligibility codes and related family information); staff employment, rota, training, qualifications, timesheets, pay and pension information; messages and forms; audit logs of user activity. |
| Special category data | Health information (medical conditions, allergies, dietary needs, medication, accidents and illness), special educational needs and disabilities, and, where you record them, ethnicity, religion and home language. |
| Criminal offence data | Information relating to staff criminal records checks (such as DBS certificate numbers and dates), and safeguarding records, which may contain information about alleged offences. |
Annex 2: Technical and organisational measures
- A separate database for each customer organisation; no customer's records share tables with another's.
- Encryption in transit (HTTPS with HSTS) and encryption at rest of the database disks and backups; additional field-level encryption of safeguarding entries, medical details, funding codes and certificate numbers.
- Passwords and PINs stored only as one-way hashes; limits on sign-in attempts; optional two-step sign-in, which we recommend for all administrators.
- Role and site-based access in the Software; safeguarding records restricted to designated safeguarding leads; the system administrator role cannot open children's, family or staff records.
- A tamper-evident audit log of sign-ins, changes, exports and deletions.
- Photos, videos and documents stored as private files, served only to signed-in users entitled to see them; location and other metadata removed from uploaded photos and videos.
- Platform staff access to servers limited to named people, using individual accounts and key-based authentication, with access to a customer's records only on that customer's request.
- Nightly encrypted backups held separately from the live database, with periodic restore tests.
- Operating system and dependency security updates applied promptly; firewalls permitting only the necessary traffic.
- A documented process for handling and notifying personal data breaches, and for responsible disclosure of vulnerabilities.
- Staff confidentiality obligations, data protection training and pre-employment checks.
[Open point: confirm each measure in this annex is in place on the production platform before it is published as a commitment.]
Annex 3: Sub-processors
| Sub-processor | What it does | Where | Data |
|---|---|---|---|
| [Server provider] | Servers and storage for the hosted service | [UK region] | All Customer Data |
| [Laravel Forge (Laravel Holdings Inc.)] | Server provisioning and deployment; can reach the servers it manages | [USA, under the UK extension to the EU-US Data Privacy Framework or the IDTA] | No Customer Data is sent to it, but it has administrative access to the servers |
| [Email delivery provider] | Sending email from the Software | [Region] | Recipient addresses and email content |
| [Off-site backup storage provider] | Holding encrypted backups | [UK region] | Encrypted backups of all Customer Data |
| Apple, Google and Mozilla push services | Delivering notifications to phones | Worldwide | Device tokens and encrypted notification content |
Accounting software you connect to the Software (Xero, QuickBooks or Sage Accounting) is not our sub-processor. Your users choose to connect it, it is your own account under your own agreement with that provider, and the Software sends it, on your instruction, each family's name, account reference, billing address and invoice email, and your invoices, credit notes and payments. Disconnecting it stops anything more being sent; what was sent stays in your accounting software.