Affiliate Compliance: FTC, GDPR, Consent 2026

Fewer than 30% of SaaS affiliate programs include disclosure guidance in onboarding materials, and roughly half of those that do never reference it again after the welcome email. In 2026, that gap is no longer a soft risk.

The FTC's revised endorsement guides treat the merchant as jointly liable for affiliate disclosure failures, with a $50,000 minimum civil penalty exposure per post that crosses the clear-and-conspicuous line.

On the other side of the Atlantic, EU data-protection authorities have started fining tracking-cookie misconfigurations directly — not just data-breach incidents — and affiliate tracking pixels are squarely in scope.

This guide covers what FTC disclosure actually requires in 2026, how affiliate tracking intersects with GDPR consent, the clauses your affiliate agreement needs to carry both, and a 10-item checklist you can audit against in an afternoon.

Affiliate is the acquisition channel you scale once channel-level revenue attribution has shown it actually pays your MRR — and the compliance layer here is the guardrail that keeps that channel payable at scale.

FTC disclosure requirements

The Federal Trade Commission's Endorsement Guides — codified at 16 CFR Part 255 — are the controlling US framework for affiliate marketing disclosures.

They require that any "material connection" between an endorser and a brand — including affiliate commission, free product, or paid placement — be disclosed clearly and conspicuously, in a way that a reasonable consumer would notice before they engage with the recommendation.

The FTC's plain-language reference for creators, Disclosures 101 for Social Media Influencers, is the document worth handing affiliates directly.

What the FTC requires

The standard is clear and conspicuous, which the FTC interprets in plain English: the disclosure must be hard to miss and easy to understand.

The minimum acceptable text for written content is the hashtag #ad placed at the top of the post — buried in a paragraph or at the end of a 3,000-word article doesn't qualify.

Phrases like "thanks to [brand] for sponsoring" are acceptable; coy formulations like "#sp," "#collab," or "#partner" are not, because the FTC's consumer-testing research found they don't reliably communicate a commercial relationship.

For video content, the disclosure must be visible within the first 30 seconds and on screen long enough to be read. A spoken disclosure is acceptable in addition to the on-screen one, never as a replacement for it.

For livestreams, the disclosure must be repeated periodically so that viewers joining mid-stream see it. For podcasts, an audio disclosure at the start of the segment that mentions the product is the floor.

Who is responsible

This is the part most SaaS founders miss. Under the 2023 revisions to the Endorsement Guides, the FTC made explicit that brands share liability with their affiliates for inadequate disclosures.

If your affiliate publishes a YouTube review without disclosing the commission, the FTC can — and now routinely does — name both parties in the enforcement action.

The Commission expects merchants to operate an active monitoring program, not just a disclosure clause in the affiliate agreement. "We told them to disclose" is not a defense.

The expectation is that you periodically audit a sample of affiliate content, document the audit, and act on violations (warning, removal, or termination depending on severity).

For a deeper look at what monitoring infrastructure ties into your tracking stack, see our piece on affiliate attribution fraud prevention.

Influencer and social-media specifics

Each platform has its own native disclosure mechanism, and the FTC treats using the native tool as evidence of good-faith disclosure — though never as a substitute for clear-and-conspicuous text in the content itself.

The native tools change frequently; the underlying rule does not.

GDPR and affiliate tracking

Affiliate tracking and the General Data Protection Regulation collide in one place: the cookie (or fingerprint, or stored identifier) that links a click to a later conversion.

Under GDPR Article 4, that identifier is personal data — even if no name or email is attached — because it is used to single out an individual across sessions, and an "online identifier" is named explicitly in the definition.

Personal data triggers the full GDPR machinery: lawful basis, consent, data subject rights, data processing agreements, and breach notification.

How affiliate tracking intersects with GDPR

The relevant lawful basis for affiliate tracking cookies is almost always consent.

The "legitimate interest" basis is technically available but in practice rejected by EU regulators for any tracking that survives across sessions or shares data with third parties, which describes the entirety of an affiliate stack.

The European Data Protection Board's 2020 consent guidelines set the bar: consent must be specific, informed, freely given, and as easy to withdraw as to grant.

There's a parallel regime — the ePrivacy Directive, soon to be replaced by the ePrivacy Regulation — that applies specifically to cookies and similar technologies.

ePrivacy requires consent before any non-strictly-necessary cookie is set, regardless of whether the underlying data is "personal" under GDPR. Affiliate tracking cookies are never strictly necessary, so the consent requirement applies whether you analyze it under GDPR or ePrivacy.

Consent mechanics

The technical implementation has two parts.

First, your tracking script must not fire until consent is granted — not "fire and respect opt-out later," which is the most common pattern outside the EU and which EU regulators consistently treat as a violation.

Second, the consent decision must be documented and timestamped via a Consent Management Platform (CMP) that can produce an audit trail on request.

In practice this means your tracking pixel — including any pixel TrackRev installs on your behalf — sits behind a consent gate.

When an EU visitor clicks an affiliate link and arrives on your site, the CMP banner loads first, the tracking script loads only if consent is granted, and the visitor's choice is logged.

If consent is denied, the click never enters the attribution database. For the technical pattern that keeps the link layer working under these constraints, see European SaaS attribution with GDPR-first-party tracking.

Data processing agreements

Every tool that touches affiliate-tracking data — your tracking platform, your CMP, your email provider that sends payout notifications, your CRM if it ingests partner records — is a data processor under GDPR and requires a Data Processing Agreement (DPA) with you, the controller.

The DPA is not boilerplate. It must specify the categories of data processed, the duration, the security measures, the sub-processors used, and the data transfer mechanism if processing occurs outside the EEA.

If you process EU resident data through US-based affiliate tooling, you also need a valid international transfer mechanism: the EU-US Data Privacy Framework (for certified US processors), Standard Contractual Clauses with a transfer impact assessment, or one of the GDPR Article 49 derogations (rarely available in practice).

TrackRev's affiliate analytics and conversion tracking products both support EU data residency, which removes the transfer question entirely for EU-resident traffic.

EU data residency

Even with a valid transfer mechanism, the simplest compliance posture is to keep EU resident data in the EU. That means your tracking platform should let you select an EU region for storage of click logs, visitor identifiers, and conversion records.

If your tooling can't offer that — and a lot of US-incorporated affiliate platforms still can't in 2026 — you're either relying on the EU-US Data Privacy Framework (which has been struck down twice and is expected to be challenged again) or absorbing meaningful regulatory risk.

Affiliate agreement clauses

The affiliate agreement is the contract layer that operationalizes both FTC disclosure and GDPR consent. It's also the document that lets you terminate a partner cleanly when something goes wrong.

The clauses below are the minimum a 2026 program needs to carry. This is not a template — your attorney should draft the actual language — but every clause listed should appear in some form.

Disclosure requirements

Specify the exact disclosure language the affiliate must use, the placement (above the fold, first 30 seconds, etc.), and the consequence for non-compliance.

Suggested clause structure: "Affiliate shall include the disclosure '#ad' or 'This post contains affiliate links to [Brand]' at the top of any written content and within the first 30 seconds of any video content promoting the Services.

Failure to comply may result in immediate commission reversal and termination of this agreement."

Pair this with a contractual obligation to comply with FTC Endorsement Guides, the UK CAP Code (if marketing to UK consumers), the EU Audiovisual Media Services Directive, and any other jurisdiction-specific disclosure rules that apply to the affiliate's audience.

Prohibited promotional methods

Spell out — explicitly — the methods that constitute commission-reversal grounds.

The baseline list every B2B SaaS program should carry: brand-bidding on your trademarked terms in paid search, trademark bidding in display, cookie stuffing (forcing tracking cookies without a real click), incentivized clicks (paying users to click), email spam (unsolicited bulk mail under CAN-SPAM or GDPR-equivalent rules), black-hat SEO against your brand keywords, and iframe injection on third-party sites.

A common omission worth fixing: prohibit running paid traffic to your landing pages without permission.

Affiliates running their own Google Ads campaigns to your site bid up your CPCs and create attribution conflicts with your in-house team — TrackRev's Stripe affiliate tracking can flag the conflict, but the contract has to prohibit the behavior for the flag to matter.

Commission hold and reversal conditions

Define a commission hold period that exceeds your refund window by at least seven days. For most SaaS programs this is 30–45 days.

State the conditions under which commission can be reversed after payment: customer refund, chargeback, fraud determination, terms-of-service violation by the customer attributable to the affiliate's marketing, or breach of the affiliate agreement (including disclosure failure).

The mechanics of holds and reversals are non-trivial when Stripe is your billing system — partial refunds and downgrades create proration questions that most affiliate agreements ignore.

See the companion piece handling affiliate commissions on Stripe refunds, upgrades, and downgrades for the event-by-event commission logic.

IP and brand use

Grant a limited, revocable, non-exclusive license to use your name, logo, and approved marketing assets solely for the purpose of promoting the program. Specify a brand asset library (Notion page, Frontify, brand portal) as the authoritative source.

Prohibit modification of logos, use of confusable lookalike domains, and any registration of trademarks containing your brand name.

Term, termination, and post-termination

Standard structure: month-to-month with either party able to terminate on 30 days notice, plus immediate termination for cause (material breach, fraud, regulatory violation).

Post-termination obligations should include: removal of all affiliate links within 14 days, deletion of brand assets, return or destruction of confidential information, and continuation of confidentiality and IP clauses indefinitely.

On the commission side, decide upfront whether terminated affiliates retain recurring commissions on existing customers. The most common pattern in B2B SaaS is to keep the commission stream for terminations without cause but cut it immediately for terminations with cause.

Whichever you pick, make it explicit — silence on this point is one of the most common sources of post-termination disputes.

Compliance checklist

Run through this checklist quarterly. If you can't tick a box, you have homework before your next regulator inquiry.

• Written affiliate agreement covering disclosure, prohibited methods, IP, term, and termination — signed by every active partner.
• Disclosure guidance shipped in onboarding — not just a clause in the agreement, but a one-page "how to disclose" document with platform-specific examples.
• Active monitoring sample — at least 10% of active affiliates audited per quarter, with the audit logged.
• CMP installed and verified — tracking script gated behind consent in all EU traffic, with audit trail available.
• Cookie policy and privacy policy updated — explicit reference to affiliate tracking cookies, retention period, and third-party sub-processors.
• DPAs signed with every data processor in the affiliate stack (tracking platform, CMP, payout provider, CRM).
• EU data residency confirmed — either an EU storage region selected in your tracking platform, or a documented international transfer mechanism in place.
• Disclosure language baked into payout reminders — every commission notification email repeats the disclosure expectation.
• Termination workflow documented — who decides, how the affiliate is notified, what happens to held commissions, who removes IP.
• Regulator-response runbook — single page describing who responds to an FTC warning letter or a DPA inquiry, where the audit trail lives, who the outside counsel is.

A note on legal advice

This article is operational guidance for SaaS founders and affiliate program managers. It is not legal advice, and it is not a substitute for an attorney.

The FTC Endorsement Guides, GDPR, ePrivacy, and the various national implementations interact in jurisdiction-specific ways that depend on your buyer mix, your processor stack, and the structure of your affiliate program.

Before you launch a program, before you change a material clause in an existing agreement, and before you respond to a regulator inquiry, talk to a lawyer who works in marketing and data-protection compliance.

TrackRev provides tooling — tracking and analytics, payouts, and conversion logging — that supports a compliant program. It is not a replacement for the policy, contract, and legal-review work.

The most defensible programs treat compliance as a product feature, not a checkbox: build the disclosure prompt into onboarding, the consent gate into the pixel install, and the audit log into the affiliate dashboard.

The marginal cost of doing it that way is small. The cost of doing it badly is now measured in five- and six-figure penalties.

If you want to see how the tracking layer of this fits together, the related guide on server-side click tracking vs client-side pixels covers the technical pattern that pairs well with consent gating.

For program structure, the companion piece on scaling an affiliate program from 0 to $50K MRR covers the operational milestones where compliance reviews should sit.

And the SaaS affiliate program benchmarks for 2026 show where compliant programs land on the operating metrics.