A franchisor runs a shared booking platform for 80 gyms. Headquarters analyses the bookings for marketing and site planning, while the gyms use them for class planning and member care. A member asks for access to his data. The gym refers him to headquarters, headquarters sends him back to the gym, and after six weeks the complaint lands with the supervisory authority. A.1.2.8 requires the organization to settle, in a binding way with every partner in joint control, who answers for which part of the processing, data protection and security included.
Joint control arises faster than many expect: group platforms, cooperation projects, joint events or third-party services embedded in one’s own website. Without a clear split, duties are left undone because each side assumes the other has them.
What does the standard require?
The control applies to every organization that determines the purposes and means of processing together with others.
- Set roles. Roles and responsibilities are agreed with each joint controller, explicitly including privacy and security requirements.
- Be transparent. The split is understandable for outsiders.
- Document it bindingly. The arrangement is set out in a contract or a similarly binding document. In some jurisdictions, such an arrangement is known as a data sharing agreement.
- Typical content. The standard offers an open list. It includes the purpose of the cooperation, the organizations involved, the data categories concerned, an overview of the processing operations and the roles of each side. It goes on to responsibility for technical and organizational measures, the procedure for data breaches, retention and deletion, and liability for breaches of the agreement. For data subjects, the arrangement settles how their rights are met, how they learn the essence of the arrangement, how they obtain further information and whom they can contact.
In practice
Recognize joint control. For cooperations, platforms and embedded third-party services, check who decides whether and why data is processed. As soon as several parties pursue purposes of their own and help shape the means, joint control is usually present. A data processing agreement does not fit then.
Draft the arrangement in full. Work through the standard’s list as a checklist and record an answer for each point. Rules on deletion periods and liability are missing particularly often, because both sides assume they are in the cooperation agreement.
Align the reporting route for data breaches. Decide who informs the supervisory authority, who notifies data subjects and how quickly the partners inform each other. A single contact on each side, named in the incident plans of both organizations, has proven itself.
Inform data subjects clearly. The essence of the arrangement belongs in the privacy notice: who is involved, who is responsible for what and which contact point takes requests. Name that contact point explicitly so readers do not have to work out the split themselves.
Review regularly. If purposes, data categories or partners change, the arrangement is updated. A yearly comparison with the record of processing activities finds cooperations that have quietly grown.
Typical audit evidence
For A.1.2.8, auditors typically expect:
- Overview of joint controllerships, for example as a flag in the record of processing activities
- Signed arrangements covering the items in the standard’s list
- Allocation of tasks per processing step (→ RACI Matrix)
- Privacy notices with the essence of the arrangement and the contact point
- Agreed reporting route for data breaches in the incident plans of both sides (→ Incident Response Runbooks)
KPI
% of joint controller arrangements with formalized responsibility agreements
Formalized means: signed, with every point of the checklist answered and its key points made known to data subjects. The target is 100%. The denominator is often the real problem, because joint controllerships are rarely all identified.
Supporting KPIs:
- Share of arrangements whose key points appear in the privacy notice
- Share of arrangements with a rehearsed reporting route for data breaches
- Time since the last review per arrangement
Link to the GDPR
A.1.2.8 corresponds to Article 26 GDPR. Under paragraph 1, joint controllers set out in a transparent arrangement who fulfils which obligations, in particular regarding data subject rights and the information duties under Articles 13 and 14. A contact point may be designated. Paragraph 2 requires the arrangement to reflect the actual roles and its essence to be made available to data subjects. Under paragraph 3, data subjects can exercise their rights against each controller, and under Article 82(4) each one is liable for the entire damage. Article 4(7) defines the controller as the body that decides alone or jointly with others (→ GDPR General Data Protection Regulation).
Related controls
Joint control touches contracts, information and incidents:
- A.1.2.7 Contracts with PII processors: applies when the partner only processes on instructions.
- A.1.3.2 Determining and fulfilling obligations to PII principals: describes the contact point that is needed here as well.
- A.1.3.4 Providing information to PII principals: brings the essence of the arrangement to data subjects.
- A.1.2.9 Records related to processing PII: flags joint processing in the record.
- A.5.24 Incident Management Planning and Preparation: adds the agreed reporting route to the incident plans.
- A.5.14 Information Transfer: secures the data exchange between the partners.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.2.8, and Annex B, B.1.2.8: Joint PII controller
- Regulation (EU) 2016/679 (GDPR), Articles 4, 26, 33 and 82
- Court of Justice of the EU, judgment of 29 July 2019, C-40/17 (Fashion ID)
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles