In most affiliate set-ups, the affiliate, the network and the advertiser are each controllers of the personal data they use for their own purposes, and they are often joint controllers for the moment a tracking click or pixel collects data from a visitor. A tracking platform you license to run your own campaigns is normally your processor. Getting the controller vs processor question right for each affiliate network relationship decides who must get consent, who answers users' requests, which contract you need (an Article 26 arrangement or an Article 28 data processing agreement) and who is liable when something goes wrong.

This guide explains the tests, the case law and how roles typically split. It is general information, not legal advice.

Controller, processor, joint controller: the tests

  • Controller: decides the purposes ("why") and the essential means ("how") of processing. Labels in contracts don't decide this; what actually happens does.
  • Processor: processes personal data on behalf of a controller and only on its documented instructions. A processor that starts using the data for its own purposes becomes a controller for that use.
  • Joint controllers: two or more parties that jointly determine purposes and means. Their contributions need not be equal, and neither needs access to all the data.

The EDPB's Guidelines 07/2020 on controller and processor are the leading European guidance; the ICO takes a broadly similar approach under the UK GDPR.

Joint controllers and affiliates: what Fashion ID means

In Fashion ID (C-40/17, July 2019), the Court of Justice held that a website operator that embedded a social media "Like" button was a joint controller with the platform for the collection and transmission of visitors' data, because by embedding the plug-in it made that collection possible and both parties benefited commercially. It was not a controller for what the platform did with the data afterwards.

The same logic maps closely onto affiliate tracking. When you place a network's tracking link, pixel or script on your site:

  • you decide to deploy it, and you benefit through commissions;
  • the network decides how the tracking works and benefits through its margin;
  • so you are likely joint controllers for the collection and transmission of tracking data from your pages;
  • but you are not a controller for the network's later processing, such as fraud scoring or reporting to advertisers.

Later rulings point the same way: in IAB Europe (C-604/22, March 2024), the Court held that an industry body that set the rules for a consent framework could be a joint controller even without access to the data. Practical consequence: for the tracking you place, you share responsibility for getting consent where it is needed and telling users about it. See do affiliate cookies need consent?.

Affiliate network GDPR roles: who is what

Party and activityTypical roleContract needed
Affiliate running its own site, analytics and email listControllerPrivacy notice; DPAs with its own processors
Affiliate and network: collection via tracking link or pixel on the affiliate's siteJoint controllersArticle 26 arrangement, often in network terms
Network: attribution, fraud checks, commission calculationControllerController-to-controller terms with affiliates and advertisers
Advertiser: customer sign-ups and purchasesControllerIts own privacy notice and lawful basis
SaaS tracker licensed by an affiliate or media buyerProcessorArticle 28 DPA
Tracker that also pools data across clients for its own productsController for that useSeparate terms; possible joint controllership
Hosting, email delivery, CDNProcessorArticle 28 DPA

The middle rows are where disputes start. Some networks describe themselves as processors for affiliates, but if a network uses tracking data to run its own business (setting payouts, detecting fraud across its whole programme, profiling traffic sources), it is acting as a controller for those purposes, whatever the contract says.

Check your tracker's terms: a self-hosted or cloud tracker should be a pure processor. If its terms allow it to use your campaign data for "service improvement", benchmarking or its own products, ask what that means. Our guide to self-hosted vs cloud trackers covers the practical trade-offs.

Worked example (hypothetical)

A UK comparison site promotes a dating offer through a network. The network's tracking link sets a click ID when visitors leave the site, and the advertiser posts conversions back to the network, which reports them to the site through a cloud tracker the site licenses. Roles: the site and the network are joint controllers for collecting the click; the network and the advertiser are separate controllers for attribution and payouts; the cloud tracker is the site's processor. That means three documents: the network's joint-controller terms, controller-to-controller terms between network and advertiser, and a DPA with the tracker.

Joint controller arrangements for affiliates

Article 26 requires joint controllers to set out their respective responsibilities in an arrangement. It should cover:

  • which party gets consent for the tracking, and how the consent state is passed on;
  • which party provides privacy information to users, and what it says about the other;
  • how users' rights requests are handled and forwarded;
  • breach notification between the parties;
  • the scope: precisely which processing is joint.

The "essence" of the arrangement must be made available to users, typically in your privacy notice. Individuals can exercise their rights against either joint controller, whatever the arrangement says. Many large networks include joint-controller terms in their publisher agreements; read them, because they usually put the consent burden on you.

What an Article 28 DPA must contain

Where a party is your processor, you need a written contract that includes, at minimum:

  1. the subject matter, duration, nature and purpose of processing, data types and categories of people;
  2. processing only on your documented instructions, including on international transfers;
  3. confidentiality commitments from staff;
  4. appropriate security measures;
  5. rules on sub-processors: your authorisation, and the same obligations passed down;
  6. assistance with data subjects' rights requests;
  7. assistance with security, breach notification, DPIAs and prior consultation;
  8. deletion or return of data at the end of the contract;
  9. information and audit rights so you can check compliance.

Using a data processing agreement template

Most SaaS vendors publish a standard DPA, and that's fine for small customers, provided you check it contains all of the above, names the sub-processors, gives breach notification timings and includes transfer safeguards for any processing outside the UK or EEA (see the EU-US Data Privacy Framework). If you are the one supplying a service to clients, the European Commission has published standard contractual clauses for controller-processor contracts within the EU, which can serve as a starting point.

Common mistakes

  • Calling everyone a processor to avoid joint responsibility. Regulators look at the facts.
  • No contract at all with small tools such as form builders, chat widgets or link shorteners.
  • Ignoring server-side flows. Postbacks and server-to-server feeds still pass personal data between controllers; see server-side tracking and GDPR.
  • Privacy notices that don't name partners or explain the joint-controller relationship.

Frequently asked questions

Is an affiliate network my processor?

Usually not for its core activities. A network that runs attribution, fraud detection and payouts across its programme is acting for its own purposes as a controller. It may be a joint controller with you for collecting data on your pages.

Do joint controllers share liability for fines?

Each joint controller can be held responsible for its part of the processing, and individuals can claim against either. The arrangement allocates responsibilities between you, but it doesn't bind regulators or users.

Does this apply under UK GDPR as well?

Yes. The UK GDPR keeps the same definitions and Articles 26 and 28. Fashion ID was decided before Brexit and remains part of UK law as assimilated case law, though higher UK courts can now depart from it.

Next steps

List every partner and tool, assign a role to each and file the matching contract. Compare tracking platforms with clear processor terms in our affiliate tracking platforms directory, and revisit our pillar guide to GDPR and cookie compliance for affiliate websites for the full picture.