Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.1 · Control for PII controllers

A.1.3.8 PII controllers' obligations to inform third parties

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

An event agency passes participant lists to hotels, a coach company and a photo service. One participant withdraws his consent to the publication of photos and has the spelling of his name corrected. The agency changes both in its CRM. Six months later, his picture appears in the photo service’s brochure, and the hotel keeps greeting him by the wrong name. A.1.3.8 requires the organization to inform third parties that received data about changes, withdrawals and objections, and to set up fixed routes and responsibilities for doing so.

Data subject rights reach as far as the data itself. Without this control, a correction or withdrawal only takes effect where it was declared.

What does the standard require?

The control extends data subject rights to every recipient of the data.

  • Inform third parties. The organization tells every body it has shared data with about changes, withdrawals and objections concerning that data, and sets up rules, procedures or technical routes for this.
  • Within technical reach. The steps are appropriate and take the available technology into account. In some jurisdictions, informing recipients is a legal requirement.
  • Active channels. The organization determines communication routes to the third parties and keeps them working.
  • Responsibilities. The tasks can be assigned to people responsible for running and maintaining these routes.
  • Monitor receipt. The organization tracks whether the third parties confirm receiving the information.
  • A broad notion of change. According to a note in the standard, changed or withdrawn consent, requests for correction, erasure or restriction, and objections all count.

In practice

Know who received what. The basis is an overview of recipients per processing activity, fed from the record of processing activities and the records of disclosures and transfers. Without it, a change cannot be passed on in a targeted way.

Secure channels technically and contractually. For regular data exchange, interfaces that transmit deletions and status changes automatically are a good fit. For other recipients, there is a named mailbox on both sides. In the contract, the recipient commits to implementing and confirming changes.

Assign responsibilities with deputies. Each channel has a responsible person and a deputy, often from the department that manages the partner relationship. Staff changes trigger a review of these responsibilities.

Follow up on acknowledgements. Notifications go out with a deadline, acknowledgements are filed and missing replies are escalated. The results feed into the assessment of suppliers and partners.

Involve the data subject. The reply to a request states which recipients were informed. This answers the question under the second sentence of Article 19 GDPR before it is asked and shows the person that the request is being implemented beyond the organization too. For marketing objections, the reply mentions that partners involved are blocking the address as well.

Document proportionality. Where a notification is impossible or would require disproportionate effort, record the reasons. This includes which attempts were made and why they did not succeed.

Typical audit evidence

For A.1.3.8, auditors typically expect:

  • Overview of recipients per processing activity with contact route (→ Supplier Register)
  • Communication channels with responsible persons and deputies (→ Stakeholder Communication Plan)
  • Contract clauses in which recipients commit to implementing and confirming changes
  • Notification logs with date, content and acknowledgement of receipt
  • Reasons for cases in which no notification was sent

KPI

% of third-party data recipients notified of PII corrections or deletions

For each request, the recipients that received the change are counted against all recipients of the data concerned. The target is 100%, minus documented cases of disproportionate effort. A notification only counts once it has been confirmed.

Supporting KPIs:

  • Share of notifications acknowledged within the deadline
  • Average time to acknowledgement per recipient
  • Share of recipients with an active and tested channel

Under Article 19 GDPR, the controller communicates every rectification, erasure or restriction to each recipient to whom the data was disclosed, unless this proves impossible or involves disproportionate effort. On request, the data subject learns who those recipients are. Withdrawals and objections come under this duty through the erasure grounds in Article 17(1)(b) and (c). Where data has been made public, Article 17(2) requires other controllers to be informed of the erasure request, taking account of available technology and the cost of implementation. Article 4(9) defines the term recipient (→ GDPR General Data Protection Regulation).

Informing third parties links data subject rights to the records of disclosures:

Sources

Frequently asked questions

Who counts as a third party under this control?

Every body to which the organization has passed data: processors, partners in joint control and independent recipients such as shipping providers or cooperation partners. What matters is that the data is processed further there and a change has to arrive there. The records under A.1.5.5 show who belongs to this group.

What if a recipient can no longer be reached?

Article 19 GDPR releases the controller from the notification where it proves impossible or involves disproportionate effort. In such cases, record what was attempted and why it failed. The standard still expects the organization to maintain its channels to recipients actively, so that this case stays rare.

Does the data subject have to learn who was informed?

On request, yes. Under the second sentence of Article 19 GDPR, the controller informs the person about the recipients who were notified of the rectification, erasure or restriction. A maintained overview of recipients makes this answer easy.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.