Map the decision, not the label

A controller determines the purposes and means of processing; a processor acts on a controller’s behalf. Separate controllers can share information for their own purposes. Joint control can arise where organisations jointly determine purposes and means. The fact that a document calls a recipient a processor does not settle the reality.

Our practical starting point is a simple diagram showing who collects the information, who decides why it is used and who can authorise further uses. Include any joint campaign, shared platform or group arrangement. Different activities in the same commercial relationship may have different roles. Avoid trying to describe every flow with one label because that is the supplier’s standard contract format.

Define a lawful purpose for the actual disclosure

An agreement does not itself provide a lawful basis. Each organisation must assess its relevant processing, including whether special-category or criminal-offence information requires additional conditions. A useful commercial objective does not justify sharing every field available in the database.

Write the proposed disclosure in specific terms: which information, about whom, to which organisation, for what activity and with what expected result? Then challenge the necessity. Could the purpose be met with fewer records, less detail, aggregate information or a different process? A referral may need a name and contact route, not the customer’s full purchasing history or private notes. Document the reasoning before the transfer takes place.

Distinguish recommended agreements from mandatory arrangements

The ICO regards a data-sharing agreement between separate controllers as good practice that supports accountability; it is not universally mandatory simply because two controllers share data. Joint controllers, however, must put an appropriate transparent arrangement in place under Article 26, allocating responsibilities. Controller-to-processor contracts have separate requirements.

This distinction matters when using templates. A document full of processor instructions may be inappropriate where the recipient independently decides how to use the information. Conversely, a vague collaboration memorandum may not address mandatory joint-controller responsibilities. Choose the instrument that fits the relationship and ensure it reflects how the parties actually work. Seek advice where the role assessment is genuinely contested or complex.

Make the arrangement usable by operational teams

For implementation, set out approved purposes, information categories, authorised recipients, security, retention, further sharing and escalation contacts. Identify who handles accuracy issues, rights requests and incidents. Record how a new partner is added and how access is removed when the arrangement ends.

A practical agreement should answer a real question quickly. If one party discovers that an address is wrong, who updates the shared record? If a person objects to marketing, which systems stop? If an employee sends the wrong file, whom do they call? Test those scenarios with the staff responsible. A carefully drafted document has limited value if the people operating the process cannot find or apply it.

Explain the sharing to the people affected

Privacy information should accurately describe the relevant sharing, purposes and other required information. A broad reference to “trusted partners” may conceal rather than explain a significant new use. Where information is obtained indirectly, assess the applicable transparency requirements and timing rather than assuming the original collector covered everything.

Our recommendation is to compare the proposed arrangement with the explanation the person actually saw. Would the disclosure be a surprise? Does it introduce marketing by another organisation or a materially different purpose? If consent is relied on, check its scope and evidence. Do not treat a general acceptance of website terms as a substitute for whatever valid permission or lawful basis the particular activity requires.

Build rights handling across the boundary

People should not have to understand the commercial structure to exercise their rights. Joint-controller arrangements must transparently allocate responsibilities, but those allocations do not remove the individual’s ability to exercise rights against the relevant controllers. Separate controllers also need workable processes for requests affecting shared information.

Create a shared escalation route and agree how corrections, erasure or restrictions are communicated where required. Keep enough information about recipients to make this possible. A business that cannot identify where a record went may struggle to correct it later. Test a fictional request across the arrangement and confirm that each party knows what it must assess rather than forwarding the person in circles.

Check technical delivery and onward use

Confirm the destination, recipient authority and secure transfer method before disclosure. Review access permissions and whether the receiving organisation can export or share the information further. Overseas recipients or access can introduce international-transfer requirements alongside the sharing assessment.

In practice, use a defined data specification rather than an ad hoc spreadsheet assembled differently each month. Remove unnecessary columns, check sample records and keep an appropriate transfer log. Where regular sharing is automated, assign an owner to failures and changes. An integration that silently begins sending a new sensitive field should trigger review, not be treated as a harmless product enhancement.

Review and end the arrangement deliberately

Revisit the arrangement when purposes, organisations, technology or risks change. Decide what happens to information and access on termination, while recognising each controller’s legitimate obligations. Do not promise deletion by another independent controller without establishing what it can properly do.

The strongest arrangement joins legal reasoning to operational evidence: why sharing is justified, what each party receives, what people are told and how mistakes are corrected. It is not enough to obtain a signature and file it away. A short, tested and maintained arrangement can be more useful than a long template that nobody follows.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.