# Data processing agreement (template)

**Draft template for discussion. This is not legal advice.** Each organisation should have it reviewed by its own data protection officer and legal adviser before signing. Text in [square brackets] is to be completed or chosen.

## 1. Parties

1. **[Name of contracting authority]**, of [address] (the **Controller**).
2. **Young Procurement**, of [address], the provider of Below Threshold (the **Processor**).

## 2. What this agreement covers

The Controller uses Below Threshold, an online service for running below-threshold procurements, receiving supplier submissions and keeping a record of decisions. The Processor processes personal data on the Controller's behalf to provide the service. This agreement sets out the terms required by Article 28 of the UK GDPR.

## 3. Details of the processing

- **Subject matter:** providing the Below Threshold service to the Controller.
- **Duration:** for as long as the Controller uses the service, then until the data is returned or deleted under section 11.
- **Nature and purpose:** hosting, storing, displaying, transmitting by email, backing up, encrypting and deleting procurement records; sending one-time codes, invitations, clarifications and outcome letters; keeping an audit trail.
- **Types of personal data:** names, work email addresses and roles of the Controller's staff; email addresses, names and organisation names of suppliers' contacts; the content of supplier questions and submissions, which may include personal data about suppliers' staff (for example CVs or experience); sign-in and audit records (including times and actions).
- **Categories of data subjects:** the Controller's staff and evaluators; suppliers' staff and contacts.
- **Special category or criminal offence data:** not expected. The Controller will tell suppliers not to include it unless the procurement requires it, and will tell the Processor first if it does.

## 4. The Processor's obligations

The Processor will:

1. process the personal data only on the Controller's documented instructions, including this agreement and the Controller's use of the service, unless the law requires otherwise (in which case it will tell the Controller first, unless the law forbids that);
2. make sure everyone authorised to process the data is bound by confidentiality;
3. take the security measures described in section 6;
4. use sub-processors only as set out in section 7;
5. help the Controller, as far as reasonably possible, to respond to requests from individuals exercising their rights;
6. help the Controller with its security, breach notification, data protection impact assessment and prior consultation obligations;
7. delete or return the data at the end of the service, as set out in section 11;
8. make available the information needed to show compliance with Article 28, and allow for and contribute to audits, including inspections, by the Controller or an auditor it appoints, on reasonable notice;
9. tell the Controller straight away if it thinks an instruction breaks data protection law.

## 5. The Controller's obligations

The Controller is responsible for having a lawful basis for the processing, for the content it and its suppliers put into the service, for the instructions it gives, for deciding its own retention period in the service, and for its procurement decisions and published notices.

## 6. Security

The Processor will keep in place at least the measures described on the Below Threshold security page at the date of signing, including:

- encryption in transit (HTTPS only) and at rest, with each supplier submission encrypted under its own key;
- sealing of submissions until the deadline has passed and the procurement lead releases them;
- two-step sign-in for all staff accounts, account lockout and automatic sign-out after 30 minutes of inactivity;
- virus scanning of every uploaded file, with infected files quarantined;
- an append-only, hash-chained audit trail, including every file download and export;
- daily encrypted backups, kept for [35] days, with a tested restore procedure.

The Processor will not reduce the overall level of protection without telling the Controller first.

## 7. Sub-processors

The Controller gives general authorisation for the Processor to use the sub-processors listed on the Below Threshold privacy page at the date of signing. The Processor will give at least [30] days' notice of any new or replacement sub-processor, so the Controller can object. The Processor will put equivalent data protection terms in place with each sub-processor and remains responsible for them.

## 8. International transfers

The Processor will not transfer personal data outside the UK except to the countries, and under the safeguards, listed on the privacy page (for example, a UK adequacy regulation, the UK Extension to the EU-US Data Privacy Framework, or the International Data Transfer Agreement). [Confirm the safeguard for each sub-processor before signing.]

## 9. Personal data breaches

The Processor will tell the Controller without undue delay, and in any case within [24] hours, after becoming aware of a personal data breach affecting the Controller's data. It will give the information the Controller needs to decide whether to report the breach to the Information Commissioner within 72 hours, and to tell the people affected.

## 10. Liability

[To be agreed. Usually: each party's liability under this agreement is as set out in the main terms of use or service agreement between them.]

## 11. End of the service

When the Controller stops using the service, the Processor will, at the Controller's choice, export the Controller's procurement records and then delete them, or delete them, within [90] days, unless the law requires them to be kept. Copies in backups are deleted when those backups expire.

## 12. Law

This agreement is governed by the law of England and Wales.

## Signed

For the Controller: [name, role, date]

For the Processor: [name, role, date]
