Data Processing Agreements With Your Website Tools Under UK GDPR
Short answer: Under UK GDPR, when a supplier handles personal data on your behalf (your web host, form builder, newsletter platform, CRM, live chat), it acts as your processor and you need a written contract with specific terms, usually called a data processing agreement or DPA. Most established vendors publish a standard DPA that is either built into their terms or can be accepted in the account settings. Your job is to list every tool that touches visitor or customer data, find and accept or download each DPA, note where data is stored and whether it leaves the UK, and keep that in a one-page register. This article explains the general rules and is not legal advice; check the ICO's guidance for your situation.
Controller and processor in plain words
You are the controller: you decide why you collect someone's details and what happens to them. A plumbing firm that asks for a name, phone number and postcode on its quote form is a controller.
The tools that store or handle those details because you told them to are processors. The form builder that receives the submission, the email platform that sends the confirmation and the CRM where the lead lands all process data on your instructions.
Article 28 of UK GDPR says a controller may only use processors that give enough guarantees, and that the relationship must be covered by a contract containing set points: processing only on your instructions, confidentiality, security, help with data subject requests, deletion or return at the end, and rules about sub-processors. That contract is the DPA.
Some vendors are not processors for all purposes. An analytics or advertising platform may say it acts as an independent controller for some of the data, or as a joint controller. Read the vendor's privacy terms to see which role they claim, because it changes what you need to tell visitors.
Tool-by-tool table
Use this as a starting map for a typical small business site. Your stack will differ, so treat the rows as categories.
| Tool type | Personal data it sees | Usual role | Where the DPA tends to be |
|---|---|---|---|
| Web host and CDN | IP addresses, server logs, any stored form data | Processor | Legal or terms page, often incorporated automatically |
| Form builder | Everything visitors type | Processor | Account settings or legal centre |
| Newsletter platform | Emails, names, open and click data | Processor | Legal page, sometimes needs a click to accept |
| CRM | Contact details, notes, deal history | Processor | Trust or security centre |
| Analytics | Online identifiers, device data | Processor or controller depending on vendor | Admin settings, data processing terms |
| Live chat or chatbot | Chat transcripts, names, emails | Processor | Legal centre |
| Booking or payments | Names, appointment details, payment data | Processor or controller | Terms, merchant agreement |
Do not forget the quieter tools: a spam filter on your forms, a reviews widget, a cookie consent tool, a website backup service and the email account where form notifications arrive.
Where vendors publish their DPAs
Large SaaS providers almost always have a dedicated page, usually called something like "Data Processing Addendum", "DPA" or "Data Processing Terms", linked from the footer of their website under Legal, Privacy or Trust. There are three common patterns:
- Automatically incorporated: the DPA forms part of the terms you accepted when you signed up. Download a PDF copy and note the version date.
- Accept in settings: you tick a box or press a button in the admin panel, sometimes under Account, Billing or Privacy. Google Analytics, for example, has data processing terms you accept in the admin area.
- Signed copy on request: smaller vendors may email a document for you to sign. Ask support if you cannot find one; their answer is useful evidence either way.
If a small supplier, such as a freelance developer who hosts your site on their own server, has no DPA at all, ask them to sign a short one. The ICO publishes guidance on what the contract must cover.
Sub-processors
Your processor will use its own suppliers: cloud hosting, email delivery, support desks. These are sub-processors. A proper DPA either lists them or links to a page that does, and explains how you will be told about changes. Save that link in your register and, if the vendor offers it, subscribe to change notifications. You do not need to audit each sub-processor, but you should know the list exists and roughly where the data goes.
International transfer notes
Many tools store data in the United States or elsewhere outside the UK. UK GDPR allows this under conditions: for example a UK adequacy regulation for the destination, the UK Extension to the EU-US Data Privacy Framework for certified US companies, or the UK International Data Transfer Agreement or Addendum to EU standard clauses. Reputable vendors explain which mechanism they rely on inside their DPA or a transfers page. You do not have to draft anything yourself; just record which mechanism the vendor names. If a vendor says nothing about transfers and stores data abroad, raise it with them.
A one-page register
Keep a simple sheet with one row per tool. Columns that do the job:
- Tool name and what you use it for
- Personal data involved (for example "quote form fields: name, phone, postcode")
- Role (processor, controller, joint)
- DPA status: incorporated, accepted in settings on a date, signed copy
- Link or file location of the DPA and the sub-processor list
- Data location and transfer mechanism named by the vendor
- Account owner inside your business
- Date last reviewed
Review it once a year and whenever you add a tool. When a staff member signs up for a new free app and pipes form submissions into it, that tool goes on the sheet the same day. This register also feeds your privacy notice and your record of processing activities.
Practical steps for this month
- Open your website and list every script, widget and form; ask your developer for the full list if needed.
- Check your email account for notification flows, such as forms forwarding to a shared inbox.
- For each tool, find the DPA page and save a PDF with the date in the filename.
- Accept any DPAs that require a click in settings.
- Fill in the register and store it with your other compliance documents.
- Remove tools you no longer use, and delete the data they still hold.
FAQ
Do we need a DPA if the tool is free?
Yes, if it processes personal data for you. Price does not change the role. Free tiers usually fall under the same terms as paid ones, so the published DPA normally still applies.
Is a privacy policy on the vendor's website the same as a DPA?
No. A privacy policy explains how the vendor treats its own customers' data. The DPA is the contract that governs data it handles for you. Look for both.
What if a vendor refuses to provide a DPA?
Treat it as a warning sign. Choose another tool for anything involving customer details, or limit the tool to data that is not personal.
Does our web designer need a DPA with us?
If they can access personal data held on your site, such as form entries or customer accounts, they act as a processor while doing that work, so yes.
If you want your website stack mapped and the register filled in alongside a technical review, get in touch with us and we can work through it together.