A privacy policy for an affiliate website has to tell visitors, in plain language, who you are, what personal data you and your partners collect, why, on what lawful basis, who receives it, how long you keep it and what rights people have. Those headings come directly from Articles 13 and 14 of the GDPR and UK GDPR. For an affiliate site, the parts most often missing are the affiliate networks and merchants that receive click data, the trackers on your pages, specific retention periods and, for UK visitors since 19 June 2026, how to complain to you directly.

This guide walks through each section with example wording you can adapt. It isn't a fill-in-the-blanks template: a privacy notice is only compliant if it describes what your site actually does.

General information, not legal advice. Have a professional review your final notice, especially if you run an adult site or handle payments.

What Article 13 GDPR requires you to say

When you collect data directly from visitors (forms, cookies, analytics), Article 13 lists what you must tell them at the time of collection. Article 14 adds requirements when you get data from elsewhere, such as conversion data returned by a network, including the categories of data and the source.

Required informationAffiliate-site example
Your identity and contact detailsCompany name, registered address, privacy email
Data protection officer, if you have oneContact details, or omit if not required
Representative in the EU or UK, if neededName and contact of your representative
Purposes and lawful basis for eachAnalytics (consent or UK statistical exemption plus legitimate interests), newsletter (consent)
Legitimate interests relied onFor example, keeping the site secure
Recipients or categories of recipientsAffiliate networks, analytics provider, email platform, hosting
International transfers and safeguardsUS tools under the Data Privacy Framework or standard contractual clauses
Retention periods or criteriaServer logs 30 days; newsletter data until unsubscribe plus a short period
Individual rightsAccess, rectification, erasure, restriction, objection, portability
Right to withdraw consentHow to change cookie choices or unsubscribe
Right to complainTo the ICO or the relevant EU authority (and, in the UK, to you first)
Whether data is required and consequencesEmail needed to receive the newsletter
Automated decision-makingUsually none; say so

Privacy notice requirements: tone and format

The GDPR requires information to be concise, transparent, intelligible and easily accessible, in clear and plain language. In practice:

  • Link to it from every page (usually the footer) and from your cookie banner and sign-up forms.
  • Use headings that match visitors' questions: "What we collect", "Who we share it with".
  • Layer it: a short summary at the top, detail below.
  • Translate it for each market you target. A German-language site needs a German notice.
  • Date it, and keep previous versions.

Section by section: a privacy policy template structure

1. Who we are

Name the legal entity, not just the brand. Example: "This website is operated by Example Media Ltd, registered in England and Wales (company number 00000000), 1 Example Street, London. Contact us about privacy at privacy@example.com."

2. What we collect and why

Organise by activity, not by data type. For each, give the data, purpose and lawful basis.

  • Browsing the site: IP address, device and browser data in server logs, for security and operating the site (legitimate interests).
  • Analytics: pages viewed, referrer, approximate location, to understand how the site is used (consent; or for UK visitors, the PECR statistical exemption with legitimate interests as the GDPR basis).
  • Clicking affiliate links: a click reference and sub-ID passed to the network or merchant, so that we can be paid commission (legitimate interests for the link itself; consent for any tracking cookies or pixels on our pages).
  • Newsletter: email address and sign-up record (consent).
  • Contact and comments: what you send us (legitimate interests in responding).

3. Affiliate links and partners

This section is specific to affiliate sites and is often the weakest. Explain in plain words that some links earn you commission, that when someone clicks, the network or merchant receives information such as a click identifier, the time and their device details, and that what happens after the click is governed by those parties' own privacy notices. Name your main networks or link to a list you keep up to date.

Be accurate about roles. Most affiliate networks act as independent controllers of the click and conversion data they collect, not as your processors. Our guide to controller vs processor roles for affiliates explains how to tell. Remember that your affiliate disclosure is a separate consumer-law requirement; see how to write an affiliate disclosure.

4. Cookies and similar technologies

Summarise here and link to a separate cookie policy listing each cookie, pixel or storage item, who sets it, its purpose and duration. Explain how to change choices, ideally with a link that reopens your consent tool.

5. Who we share data with

List categories at minimum, and name key providers: hosting and CDN, analytics, email platform, consent tool, affiliate networks and ad partners. State whether each acts on your behalf or for its own purposes.

6. International transfers

If data goes outside the UK or EEA, say where and on what basis: an adequacy decision, the EU-US Data Privacy Framework (or the UK extension), or standard contractual clauses.

7. How long we keep data

Give actual periods or clear criteria. "As long as necessary" on its own isn't enough. Example: "Server logs: 30 days. Analytics: 14 months. Newsletter: until you unsubscribe, then a suppression record so we don't email you again."

8. Your rights

List the rights and how to use them, with a single contact route. Mention that you'll respond within one month, and that the right to object to direct marketing is absolute.

9. Complaints

EU visitors have the right to complain to a supervisory authority, particularly in their own Member State. For UK visitors, since 19 June 2026 the Data (Use and Access) Act requires controllers to have a process for handling data protection complaints, acknowledge them within 30 days and respond without undue delay. Explain how to complain to you, and that people can also complain to the ICO. Our guide to the UK data protection complaints procedure covers the process side.

10. Changes to this notice

Date the notice and say how you'll tell people about significant changes.

Extra points for adult and dating sites

  • Sensitive data: browsing and preferences on adult sites can reveal information about sex life or sexual orientation, which is special category data. Say how you minimise this, and never imply you don't collect anything sensitive if you track page views.
  • Age verification: if you or a provider verify ages, explain what data the provider collects, whether you receive anything beyond a pass or fail result, and how long it is kept.
  • Payments: if you sell memberships, name the payment processor and explain what you receive (usually no full card numbers).
  • Discretion: explain how billing descriptors and emails appear, if relevant.
NameProviderPurposeTypeDuration
consent_stateThis site (consent tool)Remembers your cookie choicesStrictly necessary6 months
_pk_idThis site (self-hosted analytics)Counts visits to improve the siteStatistics13 months
Affiliate pixelExample networkRecords clicks for commissionAdvertising / affiliateSession

The rows are illustrative. Generate the real list from a scan of your own site, and re-scan when you add tags.

Common mistakes

  • Copying a generic template that mentions services you don't use, and omits ones you do.
  • Claiming "we do not share your data" while running affiliate and ad tags.
  • Relying on legitimate interests for cookies that need consent.
  • No retention periods.
  • Out of date: notices that still mention Universal Analytics or the Privacy Shield.

Frequently asked questions

Do affiliate websites legally need a privacy policy?

Yes, if they collect any personal data from visitors in the UK or EU, which almost every site does through server logs, analytics or affiliate tracking. Many affiliate programs and ad networks also require one in their terms.

Can I use a privacy policy generator?

A generator can give you a structure, but you must check every statement against what your site really does. Regulators assess the accuracy of the notice, not whether it looks complete.

Should the cookie policy be separate?

It doesn't have to be, but a separate, regularly updated cookie list keeps the main notice readable. Link the two clearly.

Next steps

Map what your site collects before writing a word, then build the notice section by section. Check your website terms and conditions at the same time, and read our pillar guide to GDPR for affiliate websites for the wider checklist. More guides are in our GDPR and cookies section.