Blog Small Business Guide

Sharing Personal Data with Another Business: When Do You Need an Agreement?

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.

6-minute read Topic: Data Sharing For UK small businesses

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.

First work out each organisation’s role

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 .

RelationshipWhat it usually meansWhat 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.

What should a data sharing agreement cover?

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 purpose: why the data is being shared and what each organisation may use it for.
  • The data and people involved: which categories of personal data are shared and whose information is included.
  • Each organisation’s role: whether the parties are separate controllers, joint controllers, or one is acting as a processor for the other.
  • Lawfulness and transparency: who will identify and document the relevant lawful basis, and how people will be told about the sharing.
  • Security and transfer: how the data will be sent, stored, accessed and protected, including what to do if it is sent to the wrong person or a breach occurs.
  • Retention and deletion: how long each organisation needs the information and what happens when it is no longer needed.
  • Individual rights and queries: how requests, complaints and questions will be handled, and whether a contact point would make things easier for people.
  • Review and ending the arrangement: when the parties will revisit the agreement and what happens if the purpose or relationship changes.

The ICO’s guidance on data sharing agreements explains why documenting an arrangement can support accountability and what organisations may need to consider.

Example: a small bakery using a payroll provider

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.

An agreement does not make the sharing lawful

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:

  • Purpose and necessity: is sharing needed for a clear purpose, and could you achieve it with less information?
  • Lawful basis: have you identified and documented a basis that applies to your processing? Our guide to the six lawful bases explains the options.
  • Fairness and transparency: do people reasonably expect this use, and does your privacy information explain it clearly? See what organisations must tell people .
  • Data minimisation and security: are you sharing only what is needed and using a secure method to send it?
  • Higher-risk processing: could the sharing create a high risk to individuals? If so, assess whether you need a Data Protection Impact Assessment before you begin.

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.

A practical checklist before you share

Before information leaves your organisation, check:

  • What is the specific purpose of the sharing?
  • Which data is genuinely needed for that purpose?
  • What role does each organisation have for this processing?
  • Have you documented the lawful basis and any other relevant conditions?
  • Does your privacy information accurately explain the sharing?
  • Do you need an Article 28 processor contract or an Article 26 arrangement?
  • If the parties are separate controllers, have you documented responsibilities in a data sharing agreement?
  • Is the transfer secure, and have you agreed how to handle incidents and requests?
  • Have you set a retention period and a review date?
  • Is a DPIA needed because the sharing could create a high risk?

Common assumptions to avoid

“We have a contract, so the data sharing is lawful.”

The agreement records responsibilities. You still need to assess lawfulness, fairness, transparency, necessity and security.

“The supplier calls itself a processor, so it must be one.”

The roles depend on what each organisation actually decides and does, not just the wording in a contract.

“A data sharing agreement is always legally required.”

The ICO describes it as good practice for controller-to-controller sharing. A processor relationship has a separate written-contract requirement.

“Once we agree the wording, we can leave it in a drawer.”

Review the arrangement if the purpose, data, organisations or risks change, and check that what happens in practice still matches what you documented.

Use the ICO checklist as a starting point

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

Data sharing checklist

A practical set of prompts to help organisations assess a proposed data-sharing arrangement.

View the ICO checklist

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.

Grounded in

What this article is grounded in

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.

Next step

Keep building your understanding

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.

Future Implementation Support Waitlist