Skip to content
Atesto
Create account
All articles

Audits and evidence

EDPB requires independent consent audits for joint controllers

The European Data Protection Board published a decision summary confirming that joint controllers must independently verify consent and cannot rely on partners.

On October 16, 2026, the European Data Protection Board (opens in a new tab) published a decision summary detailing an administrative fine against advertising technology company Xandr Inc. The Norwegian Data Protection Authority imposed a penalty of EUR 8,600,000 on the company. The decision shows how organizations must collect and audit evidence of consent across their data supply chains. Companies acting as joint controllers can no longer rely on contractual representations or standard security questionnaires from their commercial partners. They must maintain independent and auditable proof that the data they process has a valid legal basis.

The enforcement action originated from a complaint regarding bidding practices on a location-based dating application. The Norwegian authority found that Xandr processed personal data, including advertising identifiers and IP addresses. The data also revealed information concerning sexual orientation, which falls under special category personal data in the General Data Protection Regulation. Processing this type of data requires explicit consent. Xandr did not collect this consent directly. The company relied on the consent obtained by the application publisher. The authority determined that the publisher's consent was invalid. This reliance on a third party without independent verification formed the basis of the infringement.

For executives managing compliance and technology, the decision shifts how data provenance is audited. Historically, many organizations accepted signed agreements or annual vendor questionnaires as sufficient evidence of compliance. A company receiving data from a partner would ask the partner to confirm that all necessary consents were in place. The partner would check a box or sign a data processing addendum. This decision summary clarifies that such administrative checks fall short of regulatory expectations. When a company acts as a joint controller, it shares the responsibility for the data processing lifecycle. The authority held that "accountability cannot be outsourced" in these relationships.

This regulatory stance directly impacts how companies approach formal audits. During a security audit, auditors evaluate the controls an organization has in place to manage third-party risks. Traditionally, a completed customer security questionnaire served as adequate evidence that a vendor or partner met the necessary privacy and security standards. The auditor would review the questionnaire and mark the control as effective. The Norwegian decision challenges this methodology for privacy controls. A questionnaire is merely a claim made by a partner. It is not independent evidence of the underlying fact.

When a company processes personal data, especially in environments with high transaction volumes, the evidence of consent must move at the same speed as the data itself. Relying on a static document to govern millions of daily transactions creates a significant compliance gap. The technical infrastructure must capture and log the consent signal alongside the data payload. This creates a verifiable chain of custody. If a regulator or an auditor requests proof of lawful processing for a specific transaction, the organization must be able to produce the exact consent record tied to that event.

The classification as a joint controller fundamentally changes the compliance burden. In a standard controller and processor relationship, the processor acts strictly on the instructions of the controller. The controller bears the primary responsibility for obtaining consent. However, when multiple platforms participate in an environment where they collectively determine how and why data is processed, they become joint controllers. The European Data Protection Board summary emphasizes that each participant in this joint relationship carries an independent burden of proof. One controller cannot shield itself behind the compliance failures of another.

The severity of the fine also highlights the critical need for precise data inventories. The Norwegian authority noted that the processed data revealed sexual orientation. This elevates the data to a special category under the law. Auditing processes must therefore not only track the presence of personal data but also classify its sensitivity accurately. An organization cannot implement appropriate consent verification mechanisms if it does not know exactly what type of data flows through its systems. The audit trail must demonstrate that the level of consent matches the sensitivity of the data.

Who it applies to

The requirement applies to any organization acting as a joint controller under the General Data Protection Regulation. This includes supply-side and demand-side platforms in the advertising technology sector. It also extends to any business model where multiple entities determine the purposes and means of processing personal data together. The territorial scope covers companies processing the personal data of individuals located in Norway.

What it requires

Organizations must independently verify that the consent covering their data processing is valid. They must confirm that the consent specifically covers their own processing activities. The text requires joint controllers to look beyond contractual guarantees and actively audit the consent mechanisms of their partners. If the data includes special categories of personal data, such as information concerning sexual orientation, the organization must secure and verify explicit consent. The company must hold concrete evidence showing how and when the user granted this permission.

The dates

The Norwegian Data Protection Authority issued the final decision on October 2, 2026. The European Data Protection Board published the decision summary on October 16, 2026. The enforcement action applies immediately to the entities involved. The underlying principles regarding joint controllership and independent verification reflect the current interpretation of the General Data Protection Regulation.

What to check now

  • Identify all data streams where your company acts as a joint controller with a commercial partner.
  • Review the current methods used to verify consent for these specific data streams.
  • Locate the technical evidence that proves the validity of the consent for your own processing activities.
  • Evaluate whether your organization relies solely on partner questionnaires or contractual clauses for compliance proof.
  • Determine if any processed data falls under special categories requiring explicit consent.
  • Map the exact journey of the consent signal from the user interface to your internal databases.

The publication of this fine signals a clear regulatory focus on data provenance and shared accountability. The decision shows that consent verification is a continuous technical requirement rather than a static legal formality. Organizations must ensure their audit practices provide verifiable proof of compliance at every step of the data supply chain.

Sources

  1. European Data Protection Board (opens in a new tab) · www.edpb.europa.eu

This article is general information, not legal advice. For your company's situation, talk to a qualified lawyer.

This article was written with AI and checked, sentence by sentence, against the sources linked above.