A practical guide to working out whether another business is a processor, a separate controller or a joint controller, and what agreement or arrangement may be needed before you share personal data.
It is common for a small business to share personal data with another organisation: a supplier may handle customer records, a professional adviser may receive information about a client, or a business may work with a partner on a shared service.
The paperwork depends on what each organisation actually does with the information. Calling a document a “data sharing agreement” or a “processor contract” does not decide the legal roles. Start by working out who determines the purposes and means of the processing, and whether the other organisation is acting only on your instructions.
The short answer
If another organisation processes personal data on your behalf and on your documented instructions, you need a written contract or other legally binding arrangement that meets Article 28 of the UK GDPR. If both organisations are controllers, a data sharing agreement is generally good practice: it records how the sharing will work, but does not make the sharing lawful by itself.
The key question is whether the other organisation is a processor, a separate controller, or a joint controller. These roles describe what the organisations actually do with the data. They should not be chosen simply because a supplier’s contract uses a particular label.
If you need a refresher, read our guide to data controllers and data processors .
| Relationship | What it usually means | What to put in place |
|---|---|---|
| Controller to processor | One organisation decides why the data is used; the other handles it on that organisation’s behalf and follows its documented instructions. | A written contract or other binding legal act meeting the requirements of Article 28. |
| Controller to separate controller | Each organisation decides its own purposes and means for the processing it carries out. | A data sharing agreement is good practice. Each organisation remains responsible for its own compliance. |
| Joint controllers | The organisations jointly determine the purposes and means of the processing. | A transparent arrangement under Article 26 that sets out their respective responsibilities, including how people can exercise their rights. |
The same relationship may not apply to every use of the data. For example, a service provider might process information on your instructions for one purpose, but act as a controller for a separate purpose it determines itself. Consider the actual processing activity rather than trying to assign one label to an entire organisation.
Keep the distinction clear: a controller–processor contract and a data sharing agreement are not interchangeable. A processor contract has specific mandatory terms. A data sharing agreement between controllers helps document the arrangement, but the UK GDPR does not make that specific agreement mandatory in every controller-to-controller sharing situation.
For controller-to-controller sharing, an agreement should reflect the real arrangement and make responsibilities understandable to both organisations. It does not need to be an unnecessarily complicated legal document. For a small, low-risk arrangement, a clear written agreement may be enough; more complex or sensitive sharing calls for more detail.
Useful points to document include:
The ICO’s guidance on data sharing agreements explains why documenting an arrangement can support accountability and what organisations may need to consider.
A small-business example
A local bakery uses an external payroll provider to calculate wages and produce payslips. The bakery decides why it needs payroll processing and which employee information is required. The provider handles that information on the bakery’s behalf and follows its instructions.
For that processing, the bakery is likely to be the controller and the payroll provider its processor. The bakery should have a written Article 28 contract covering the required terms, such as documented instructions, confidentiality, security, assistance with data protection obligations, and what happens to the data when the service ends.
If the provider also uses information for a separate purpose it decides itself, the bakery should assess that use separately. The contract’s label does not settle the provider’s role for every activity.
Before sharing personal data, each organisation still needs to consider whether the sharing is lawful, fair and transparent. A signed agreement cannot replace that assessment or create a lawful basis where one does not exist.
Check that you have considered:
If the sharing involves special category data, criminal offence data, children’s information or particularly sensitive circumstances, consider the additional rules and risks before proceeding.
The agreement records responsibilities. You still need to assess lawfulness, fairness, transparency, necessity and security.
The roles depend on what each organisation actually decides and does, not just the wording in a contract.
The ICO describes it as good practice for controller-to-controller sharing. A processor relationship has a separate written-contract requirement.
Review the arrangement if the purpose, data, organisations or risks change, and check that what happens in practice still matches what you documented.
If you are planning a new or recurring data-sharing arrangement, the ICO’s checklist can help you work through the questions to ask before deciding whether and how to share.
Official ICO resource
A practical set of prompts to help organisations assess a proposed data-sharing arrangement.
The right paperwork follows from the relationship: use an Article 28 contract when a provider processes data on your behalf, an Article 26 arrangement when you jointly determine processing, and a clear data sharing agreement as good practice when separate controllers share information. In every case, document the purpose and make sure the sharing is lawful, fair, necessary and secure.
This article draws on the ICO’s guidance on data sharing, including its advice on data sharing agreements, lawful basis and the distinction between controller-to-controller sharing and processing carried out on a controller’s behalf. The right documentation depends on the organisations’ roles, and an agreement does not remove the need to assess whether the sharing is lawful, fair and transparent.
Use the glossary to check key data protection terms, or work through the free readiness check for a practical overview of areas your organisation may need to review.
We use cookies and similar technologies to make our website work and to provide optional features such as live chat.
Some cookies are strictly necessary for the website to function. Optional cookies support tools such as live chat and will only be used if you choose to allow them.
We also use privacy-friendly, cookieless website analytics to understand aggregated website usage. This does not use cookies or track you across websites.
You can choose to accept all cookies, reject non-essential cookies, or manage your preferences.