1. Purpose and scope
When Carefully Coded Ltd ("we", "us") processes personal data on behalf of a client, any third party we use to help process that data is a sub-processor. Examples include hosting and cloud infrastructure providers, backup services, and specialist contractors.
This policy explains how we appoint and manage sub-processors so that client data stays protected and we meet Article 28 of the UK General Data Protection Regulation (UK GDPR).
It applies to every client engagement where we act as a processor, and to everyone who works for us, including staff and contractors.
Where a client contract sets stricter terms or shorter timescales than this policy, the contract takes precedence.
2. Responsibilities
The data protection lead, Tom Emmerson, Director, is responsible for:
- approving every new sub-processor;
- keeping the sub-processor register up to date;
- holding the written contract with each sub-processor;
- notifying clients of changes;
- carrying out annual reviews.
Staff and contractors must not use any new service, tool or third party to store, access or process client data until the data protection lead has approved it under this policy.
3. Client authorisation
We only engage a sub-processor with the client's prior written authorisation. This is either:
- specific authorisation for a named sub-processor; or
- general authorisation in the contract, in which case we follow the notice process in section 6.
Our proposal or contract for each client lists the sub-processors we intend to use for that engagement, including our hosting provider, a UK region of a major cloud provider, agreed with each client in the contract.
4. Due diligence before appointment
Before appointing a sub-processor, the data protection lead will check and record:
| Area | What we check |
|---|---|
| Need | That the service is necessary and uses only the minimum data required |
| Location | That client data, including backups, will be stored and processed in the UK only, in line with our Data location and remote access policy |
| Security | Independent certifications or reports, such as ISO/IEC 27001 or SOC 2, or equivalent evidence of security controls |
| Access | Who at the sub-processor can access client data, and how that access is controlled and logged |
| Breach handling | That they will notify us of a breach promptly enough for us to meet our obligations to the client |
| Their own sub-processors | That they flow down equivalent terms and tell us about changes |
| Contract terms | That they will agree to Article 28 terms (see section 5) |
| Deletion | That they can return or securely delete data at the end of the service |
| AI | That they will not use client data to train artificial intelligence models (see our AI use policy) |
If a provider does not meet these requirements, we will not use it for client data. We keep the due diligence record for the life of the appointment and for 6 years afterwards.
5. Written contracts
We will have a written contract with every sub-processor before it processes client data. The contract will impose data protection obligations at least as protective as those in our contract with the client, including that the sub-processor will:
- process personal data only on our documented instructions;
- ensure that people with access are bound by confidentiality;
- implement appropriate technical and organisational security measures;
- only use further sub-processors with our authorisation and on the same terms;
- help us respond to data subject requests and meet our security, breach and impact assessment obligations;
- delete or return all personal data at the end of the service;
- provide the information needed to show compliance, and allow audits.
For large providers, this is usually their standard data processing agreement. We review it against these terms before accepting it.
We remain fully liable to the client for the actions of our sub-processors.
6. Changes to sub-processors
We will give each affected client at least 30 days' written notice before adding or replacing a sub-processor. The notice will state:
- the name of the sub-processor;
- the service it will provide and the data it will process;
- where it will store and process the data;
- the date of the change.
The client may object within the notice period. If they do, we will not make the change for that client while we discuss it. If we cannot resolve the objection, the client's contract terms on termination or alternatives apply.
If a sub-processor must be removed urgently, for example because of a security concern, we may remove it without notice and will tell the client as soon as possible.
7. The sub-processor register
The data protection lead keeps a register of all sub-processors. For each one it records:
- name and contact details;
- the service provided;
- the clients and categories of data concerned;
- storage and processing locations;
- the contract or data processing agreement and its date;
- the date of due diligence and the last review.
We provide each client with the current list of sub-processors used for their engagement at the start of the contract and after any change. The full register is available to clients on request, and we will provide it within 5 working days.
8. Ongoing monitoring
The data protection lead reviews every sub-processor at least once a year, and sooner if we learn of a breach, a change in ownership or location, or a change in its terms. The review checks that the due diligence findings are still accurate. We record the outcome in the register.
If a sub-processor suffers a breach affecting client data, we follow our Incident response procedure and notify the client.
9. Review
We review this policy at least once a year. Related policies: Data protection policy and Information security policy.