Data Protection Agreement

Version 2026-11, effective 14 November 2026. Forms part of the Organisation Terms.

This agreement sets out who is responsible for personal data when an organisation uses the Route 2 Trade platform. It applies when the organisation accepts it during account setup, or signs it.

1. About this agreement

1.1 The parties are Route 2 Trade Ltd, company number 17179950 ("Route 2 Trade"), and the organisation named in its written confirmation or account ("the Organisation").

1.2 Definitions. "Controller", "processor", "data subject", "personal data", "personal data breach" and "processing" have the meanings in the UK GDPR. "Data Protection Law" means the UK GDPR, the Data Protection Act 2018, and any law that amends or replaces them. "Participant" means a person the Organisation adds to the platform.

1.3 Order of priority. If this agreement conflicts with the Organisation Terms on data protection, this agreement applies. A Tier 1 contractor or master account accepts this agreement for itself. Each organisation beneath it with its own login accepts it separately.

2. Who is responsible for what

Each party is an independent controller for its own activities, and they aren't joint controllers. Where Route 2 Trade only follows the Organisation's instructions, it's a processor.

ActivityRoute 2 TradeThe Organisation
Deciding to enrol a Participant and running its programmeController
Background or other details the Organisation enters about a ParticipantProcessorController
Hosting the Organisation's dashboard and producing its reportsProcessorController
Participant accounts, the course, workbook and certificatesController
Background details a Participant gives directlyControllerController, once shared with it
Job matching and candidate introsController
Questions sent to Route 2 Trade, and safeguarding referralsControllerController, once it receives a referral
The Organisation's own use of data from the platformController
Business contacts, invoices and sign-in recordsControllerController for its own records

3. What both parties agree

3.1 Each party will comply with Data Protection Law, have a lawful basis for its own processing, keep personal data secure, and use it only for the purposes in Schedule 1.

3.2 The Organisation will:

3.3 Route 2 Trade will:

3.4 Sensitive data. Disability is special category data, and prison leaver status can reveal criminal offence data. Each party will treat all background details as sensitive, and rely on a valid condition under Data Protection Law. Reports outside the Organisation will use totals where possible, and small groups will be combined so that people can't be identified.

3.5 Under-18s. Before adding anyone under 18, the Organisation will name a safeguarding lead, and confirm that it has any consent or authority it needs. Each party will follow the Safeguarding Policy and the ICO's Children's Code where it applies.

3.6 Sharing between the parties. Route 2 Trade shares each Participant's progress, completion and outcomes with their Organisation. The Organisation won't use this for anything beyond supporting the Participant, running its programme and reporting. It won't pass on a Participant's identifiable data to a funder or other third party without a lawful basis.

4. Where Route 2 Trade is a processor

This section applies only to the processing marked "Processor" in section 2. Schedule 1 describes that processing. Route 2 Trade will:

4.1 Instructions. Process the data only on the Organisation's documented instructions, which include this agreement and use of the platform, unless the law requires otherwise. It will tell the Organisation first where it legally can. It will also tell the Organisation if it believes an instruction breaks Data Protection Law.

4.2 Confidentiality. Make sure that anyone authorised to process the data is bound by a duty of confidentiality.

4.3 Security. Keep appropriate technical and organisational measures in place, including those in Schedule 3.

4.4 Suppliers. The Organisation gives general authorisation for the suppliers in Schedule 2. Route 2 Trade will give at least 30 days' notice of any new or replacement supplier, so that the Organisation can object on reasonable grounds. If the objection can't be resolved, either party may end the affected service. Each supplier will be bound by equivalent data protection terms, and Route 2 Trade stays responsible for its suppliers' performance.

4.5 Rights requests. Pass on any request from a data subject about this data without undue delay, and give reasonable help so that the Organisation can respond.

4.6 Other help. Give reasonable help with security, breach reporting, DPIAs and consultation with the ICO, taking into account the nature of the processing and the information available.

4.7 End of service. At the Organisation's choice, delete or return the data when the service ends, unless the law requires it to be kept. Backups are overwritten on the supplier's normal cycle.

4.8 Audits. Make available the information needed to show compliance with this section, and allow reasonable audits, on at least 30 days' written notice, no more than once a year unless a breach or regulator requires it.

5. Requests, breaches and other terms

5.1 Requests from individuals. The party that receives a request deals with it if it's the controller of that data. If the other party is the controller, it passes on the request within 5 working days. Each party gives the other reasonable help.

5.2 Personal data breaches. A party that becomes aware of a breach affecting data shared under this agreement will tell the other without undue delay, and within 48 hours where it can. It will share what it knows about what happened, who is affected and what's being done. The controller of the affected data decides whether to tell the ICO and the people affected, and each party gives reasonable help. Neither party will name the other publicly about a breach without first consulting it, unless the law requires it.

5.3 Safeguarding. Nothing in this agreement stops either party sharing information needed to protect someone from harm.

5.4 International transfers. Neither party will transfer this data outside the UK unless the transfer complies with Data Protection Law, for example under UK adequacy regulations or an approved safeguard.

5.5 Retention. Each party keeps data only for as long as needed for its purposes, and the law. Route 2 Trade's periods are in its Data Protection Policy. When this agreement ends, each party deals with the data it controls under its own retention periods, and section 4.7 applies to data held as a processor.

5.6 Liability. Each party is responsible for its own compliance. Liability under this agreement is subject to the limits in the Organisation Terms, except for anything that can't legally be limited.

5.7 Term and changes. This agreement lasts for as long as Route 2 Trade holds personal data under the licence. Route 2 Trade may update it where the law or the service changes, giving at least 30 days' notice of any significant change.

5.8 Governing law. This agreement is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.

Schedule 1: The processing

PurposeDelivering a trades careers course, recording progress and outcomes, candidate matching, and social value and funder reporting
PeopleParticipants, including young people, prison leavers, care leavers, NEET and homeless people, and staff and contacts of each party
Personal dataName, email, username, date of birth, postcode, work status, course progress, quiz results, certificates, workbook and CV details, job profile, and job outcomes
Sensitive dataDisability or health condition, and prison leaver status, which can reveal criminal offence data. Other background details are treated as sensitive
DurationThe licence term, plus the retention periods in Route 2 Trade's Data Protection Policy

Schedule 2: Suppliers

SupplierServiceData involved
SupabaseDatabase and storageAll platform data
NetlifyWebsite and server functionsData passing through the platform
ResendEmail deliveryNames, email addresses and email content
PDFShiftCertificate PDFsParticipant name and completion date
Google WorkspaceBusiness emailEmails and related details
postcodes.ioDistance searchesPostcodes only

Schedule 3: Security measures

Schedule 4: Organisation details

The Organisation's name, contacts, and the date and version it accepted are recorded during account setup.