Website & Development
Data Processing Agreement with Your Web Agency: Why You Need One
Copy for AI
Some links in this article are affiliate links. If you choose a tool through one of them, we may earn a commission. It costs you nothing extra and does not change our assessment.
Yes, you need a data processing agreement with your web agency.
That’s the case as soon as the agency can access the personal data of your visitors, leads or customers.
The verdict: almost every B2B website triggers it. Contact forms, a CRM connection, hosting, analytics or simple CMS access all count, and the GDPR then wants the arrangements in writing.
The agreement is often shortened to DPA, so “DPA GDPR” and “data processing agreement” mean the same thing.
Below: who is who, why the agreement must exist, what goes in it and how to arrange it without a mountain of paperwork.
What is a data processing agreement and who is who?
A data processing agreement is a contract that sets out how an outside party processes personal data for you.
The requirement comes straight from the GDPR, the General Data Protection Regulation.
The controller and the processor
The division of roles is the heart of it:
- Data controller: your company, because you decide why and how lead and customer data is processed.
- Processor: your web agency or host, which works on your instructions without a purpose of its own.
- Sub-processor: a party your processor brings in, such as an external host or email tool.
Think of an agency that manages your form submissions, or a host that keeps your database on its servers.
How the roles fit together
Here’s the chain in one picture:
The European Data Protection Board spells these roles out in its Guidelines 07/2020 on controller and processor, final version of 7 July 2021.
Why the roles matter
The law puts ultimate responsibility on you as the client.
You choose the processor, you give the instructions, and you must be able to show that you arranged it properly. The data processing agreement is that evidence.
Why do you need a data processing agreement with your web agency?
Because the GDPR literally requires it once an outside party processes personal data for you.
Article 28 of the GDPR says this processing must be governed by a contract or another binding legal act, “in writing, including in electronic form”.
No threshold: company size and data volume make no difference.
Where a web agency touches personal data
In practice, a web agency almost always comes into contact with personal data. For example:
- it builds and maintains your contact forms, with names, emails and phone numbers
- it has admin access to your CMS, with submissions and user accounts
- it connects your site to your CRM, email tool or analytics
- it hosts your site, or arranges hosting with a third party
In each case, someone can access data about real people. That’s what triggers the obligation.
The tools in the chain
Your CRM and email platform are processors too, and often sub-processors of your agency.
A CRM such as HubSpot stores every lead your forms send it:
HubSpot’s free CRM page, October 2026. Any CRM that receives your form leads belongs on your list of processors.
Our comparison of the best B2B CRM systems shows how many of these tools a typical stack holds.
What the agreement protects
It isn’t just a formality. The agreement sets out three things:
- the agency uses the data only for your purpose
- it doesn’t resell the data
- it secures the data adequately
Without that document you have no enforceable arrangement. You carry the full risk alone.
Part of trust on your site
This ties into trust on your B2B website.
Prospects leave their data on the assumption that you handle it carefully. Sealing the chain with your suppliers is invisible, but it’s part of that promise.
Your GDPR-compliant contact form is the visible half; the DPA is the hidden half.
Is your hosting provider also a processor?
Yes, as a rule: its servers hold your databases, form submissions and backups.
It can technically access personal data, so you need a data processing agreement with your host as well.
Large hosts usually have one ready
Big hosting providers offer a ready-made DPA. You accept it digitally, or it’s woven into their terms and conditions.
Still, check it rather than assume it. Our guide to choosing web hosting lists the other questions worth asking at the same time.
Where your data physically sits
If the servers are inside the European Economic Area (EEA), that’s the simplest case.
If data is processed outside the EEA, for example by an American cloud provider, extra rules apply to that transfer. Appropriate safeguards must be in place.
The European Commission’s standard contractual clauses are the usual safeguard. The modernised set dates from 4 June 2021.
Good sign: an agency with its affairs in order explains in a few sentences where your data is.
What belongs in a data processing agreement?
A concrete description of what the processor may do with your data, and under which conditions.
In Article 28(3), the GDPR lists a fixed set of topics. Here they are in plain language.
The scope of the processing
These items describe what the processing is:
- Subject, duration, nature and purpose: what the data is for, how long, ongoing or one-off.
- Type of data and data subjects: names, emails, IP addresses; leads, customers, visitors.
- Your instructions only: the processor uses the data for what you instruct, not its own goals.
The safeguards
These items describe how the data is protected:
- Confidentiality: staff with access are bound to confidentiality.
- Security: technical and organisational measures such as encryption, access management and backups.
- Sub-processors: other parties only with your prior written authorisation.
That authorisation can be specific or general. With a general one, the agency must tell you about changes, so you get the chance to object.
The obligations around the processing
These items cover help, the exit and oversight:
- Help with obligations: handling access and deletion requests, and reporting data breaches in good time.
- End of the collaboration: your data is returned or deleted, at your choice.
- Oversight: the processor cooperates with audits and shows it complies.
Here’s the full checklist as a quick table:
| Article 28 topic | What to check | Weak spot to look for |
|---|---|---|
| Purpose and duration | matches what the agency really does | generic template text |
| Types of data | forms, CRM, analytics named | analytics left out |
| Sub-processors | an up-to-date list | list from years ago |
| Security | concrete measures | ”appropriate measures” only |
| End of contract | return or delete, your choice | not mentioned |
You don’t write it from scratch
Most data processing agreements follow a standard template. Your web agency or host usually provides its own version.
Your job is to check that the points above are in it. Then check that the arrangements match reality, such as which sub-processors your data actually reaches.
An email platform is a classic one to verify:
Brevo’s homepage, October 2026. If your newsletter sign-ups land in a tool like this, it belongs on the sub-processor list.
Rule of thumb: every tool that receives a form field is a line in the sub-processor list.
What happens if you don’t have a data processing agreement?
Then you carry the risk, because the controller stays liable for what happens to the data.
That’s true even when the fault lies with your supplier.
Liability sits with you
Under Article 82, a processor is only liable in narrower cases.
That’s when it breaches its own processor duties or ignores your lawful instructions.
Watch out: the missing agreement is a GDPR breach in itself, whether or not anything goes wrong.
Fines
The data protection authority can fine violations. A missing or faulty DPA falls under the lower fine category.
Article 83(4) caps it at 10 million euros or 2 percent of worldwide annual turnover, whichever is higher.
An SME will rarely see the maximum. But it’s a real risk, not a theory.
It’s also reputational damage you don’t want while you’re building trust with prospects.
No grip on your data
More practically still: without an agreement you have nothing in black and white.
Nothing says your supplier secures the data, doesn’t resell it or returns it when you leave. When something goes wrong, you’re left empty-handed.
That gap shows up most when you move your website to a new agency and nobody agreed what happens to the old copies.
How do you arrange this in practice?
In four steps, if you approach it systematically.
Here’s the route from inventory to proof:
Step 1: Make a list of your processors
Who comes into contact with the personal data around your website? Typically:
- your web agency
- your host
- your analytics tool
- your email or CRM system
Not sure which tools load on your pages? Our free cookie scanner shows which third parties your site calls.
For analytics specifically, Google Analytics and the GDPR covers what to settle.
Step 2: Ask each party for the agreement
Many suppliers have one ready.
If you don’t get one, or nobody knows what you mean, treat that as a warning sign.
Step 3: Check the essentials
Use the Article 28 checklist above.
Pay extra attention to the sub-processors and to where your data is located.
Step 4: Keep everything in one place
Store all agreements centrally.
Then you can show them if the regulator or a customer asks. Your GDPR-compliant website checklist and your website privacy policy should name the same processors.
Let the agency take the lead
A good web agency offers the data processing agreement on its own initiative, often right at the start of the website project.
When an agency does this unasked and explains where your data is stored, that tells you it has its affairs in order.
Choosing a new supplier? Put it on your list of questions to ask a web design agency.
Same for maintenance: the DPA belongs next to your website maintenance contract, because the maintenance party keeps access for years.
In our complete guide to having a B2B website built, this is a standard part of a professional process.
Frequently asked questions
Is a DPA the same as a data processing agreement?
Yes. DPA is simply the common abbreviation. Under the GDPR, the contract between a controller and a processor is required by Article 28.
Does a small company need a data processing agreement?
Yes. The GDPR sets no size threshold. As soon as a supplier processes personal data on your behalf, the written agreement is required.
Can the agreement be signed online?
Yes. Article 28 explicitly allows the contract to be in writing “including in electronic form”, so accepting a host’s DPA digitally counts.
Who has to provide the data processing agreement?
Either side can draft it, but processors usually offer their own template. You, as the controller, check that it covers the Article 28 points.
The short summary
Once your web agency or host can access your leads’ personal data, the GDPR requires a written data processing agreement.
You’re the controller and stay responsible, so the agreement protects you first. It covers purpose, security, sub-processors and the end of the collaboration.
Good news: a solid supplier arranges this without being asked.
Want hosting and updates handled too? See our website maintenance services.
Want to be sure it’s properly arranged for your website? Contact us and we’ll check your processor list with you.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.