Customer Impact

Website & Development

Is Your Contact Form GDPR Compliant? Consent and Retention Periods

Copy for AI

A GDPR compliant contact form collects only needed data, lawfully and for a set period.

Put fully: you ask only what you need. You have a valid legal basis. You’re transparent about what you do with the data. And you don’t keep it longer than necessary.

That sounds simple. In practice many B2B forms collect too many fields, lack a clear privacy reference, and nobody ever cleans up the leads.

The verdict: privacy and conversion don’t clash. Fewer fields, a separate marketing checkbox and a retention period you actually enforce make a form both compliant and easier to fill in.

Below: consent, data minimisation and retention periods in practical terms, without wrecking your conversion.

What does GDPR compliant mean for your contact form?

Every piece of personal data from your form has a purpose, a legal basis and a retention period, and the visitor knows it.

Who the GDPR protects

The GDPR (AVG in Dutch) is the European privacy law. It protects the personal data of people who are in the EU, whatever their nationality.

That’s set out in Article 3 and Recital 14 of the GDPR. A name, email address or phone number in your form simply falls under it.

The principles behind it

At its core it comes down to a few principles from Article 5 of the GDPR:

  • Data minimisation: data must be “limited to what is necessary”
  • Fairness and transparency: the visitor knows what happens
  • Lawfulness: you have a valid legal basis
  • Security: you protect the data properly

So one checkbox doesn’t make a form compliant.

It’s compliant because of the combination: what you ask, how you explain it, where the data goes and how long you keep it.

Here’s that combination as one check per field:

GDPR CONTACT FORM Three questions for every field 1. Do you need it to answer? data minimisation, Article 5(1)(c) No: drop it or make it optional 2. Which legal basis? request: Art. 6(1)(b) or (f); marketing: consent Marketing apart unticked, separate box 3. How long do you keep it? storage limitation, Article 5(1)(e) Set and enforce a period per purpose Document every answer, for example in your record of processing activities.

For the wider picture beyond the form, see our guide to a GDPR compliant website.

For simply answering a request, you generally rely on legitimate interest or on pre-contract steps, not on separate consent.

Someone who fills in a form to reach you expects a reply. That’s the whole point.

Article 6(1) of the GDPR sets out six possible legal bases, and consent is only one of them.

Two matter most for a contact form:

  • Point (b): steps taken at the visitor’s request before a contract
  • Point (f): your legitimate interests

Which one fits depends on your purpose.

Answering is not marketing

The distinction that often goes wrong in B2B: answering a question isn’t the same as adding someone to your newsletter or calling them for sales.

If you also want to use the data for marketing, you usually need separate, explicit consent. You collect it through a checkbox that isn’t pre-ticked.

Recital 32 of the GDPR is blunt: “Silence, pre-ticked boxes or inactivity should not therefore constitute consent.”

Article 7(2) adds that a consent request must be “clearly distinguishable from the other matters”.

Watch out: never merge the two. One generic “I agree” box fails both.

The European data protection authorities set out the full conditions in the EDPB Guidelines 05/2020 on consent, adopted on 4 May 2020.

A clean set-up

A common, clean approach:

  1. Process the request on the basis of your legitimate interest.
  2. Add a separate, optional checkbox for those who also want commercial follow-up.
  3. Leave that box unticked by default.

That keeps your legal basis defensible. It also respects the visitor’s choice.

For example, say a visitor asks for a quote and leaves the newsletter box empty. You answer the quote, but they don’t land on your mailing list.

Document your choice

Whether you rely on consent or on legitimate interest, you must be able to justify and document that choice.

With legitimate interest you explicitly weigh your interest against the visitor’s privacy. The UK regulator’s three-part test is a handy structure for that:

  • Purpose: do you have a legitimate interest?
  • Necessity: is using the data necessary for it?
  • Balancing: do the person’s rights override your interest?

The ICO adds that you must satisfy all three parts “before you start using the information”.

What data are you allowed to ask for?

Only the fields you need to handle the request. Not one more.

Where most B2B forms go wrong

That’s the data minimisation principle, and it’s exactly where most B2B forms slip.

Job title, company size, budget, phone number, postal address: every extra mandatory field you don’t directly need is harder to justify. It also costs you conversion.

The test per field

A good test per field: can you answer the request without it? If so, make it optional. Or drop it.

For a first contact, a name, an email address and the message often suffice:

FieldNeeded to answer?Advice
NameYesRequired
Email addressYesRequired
MessageYesRequired
Phone numberOnly if they prefer a callOptional
Job title, company size, budgetNoOptional with a reason, or drop

Enrichment needs a reason

If you do collect enriching data, for lead qualification for instance, make clear why. And don’t make it mandatory.

Short forms are more privacy friendly. They usually convert better too.

You can read more about this in our guide on form conversion optimisation and our tips for lead form optimization.

How long may you keep the data?

No longer than the purpose needs.

No fixed period in the law

The storage limitation principle in Article 5(1)(e) says data may be kept “for no longer than is necessary”.

The GDPR deliberately sets no fixed retention period. You determine a reasonable period per data category, document it and stick to it.

The alternative, leaving everything in your inbox or CRM indefinitely, is exactly what the law wants to prevent.

Two tracks in practice

A request that leads nowhere? Don’t keep it for years.

If it becomes a customer or an active opportunity, you have a legitimate reason to keep it longer. Statutory retention obligations sometimes come into play as well, for invoicing for example.

So work with simple logic:

  • Standard period: for unanswered or rejected leads
  • Separate period: for data that moves into a customer relationship

Write it down and enforce it

Write down which period applies to which purpose and who is responsible for the clean-up. Your record of processing activities is the natural place.

Rule of thumb: a period you don’t enforce doesn’t count in practice.

What else needs to be next to your form?

A visible, honest explanation of what happens to the data, with a link to your privacy statement right next to the submit button.

Transparency before the click

Transparency is a core GDPR obligation. Before submitting, the visitor must be able to see who processes the data, for what purpose and on which legal basis.

One line with a click-through to your full privacy statement usually suffices. That statement must be accurate and up to date; our guide to a website privacy policy covers what goes in it.

Technical and organisational points

On top of that, a few technical and organisational points come into play:

  • Security: HTTPS, and data that arrives safely, not in an unsecured inbox or a random plugin
  • Processors: form tools, CRMs and email services need a data processing agreement
  • No unnecessary trackers: no marketing cookies or scripts before consent on your contact page
  • Data subject rights: you can actually carry out an access or deletion request

Processors and hosting

Your form tool is a processor. So are your CRM and email service.

That requires a data processing agreement, and you check where they store the data. Our piece on EU hosting and GDPR data residency explains why location matters.

Cookies on the contact page

Trackers are a separate obligation alongside the form itself. Our overview of cookie banner rules in Belgium sets out what’s allowed before consent.

Not sure what your contact page loads? Run it through our free cookie scanner and see which cookies fire before anyone clicks:

How you work all of this neatly into the page without raising the barrier ties in with your broader contact page optimisation.

How do you combine GDPR compliance with conversion?

Treat privacy as a trust signal, not an obstacle.

Trust is the conversion lever

In B2B, the request through your form is often the start of a sales process. That’s exactly where trust counts.

A form that asks only what’s needed, explains clearly what happens and shows a tidy privacy reference feels more professional. It usually brings in more completed requests, not fewer.

The false choice

The flawed assumption is that you have to choose between compliance and leads.

In practice they point in the same direction: fewer fields, clear language and visible care lower the barrier and raise trust.

That fits our broader approach to turning a B2B website into a reliable lead engine.

Build it in from the start

If you want to get it right from the ground up, build the forms into the design of the site, not as a bolted-on plugin afterwards.

That’s how we work on website development and in our broader B2B website guide.

Frequently asked questions about a GDPR contact form

Do I need consent to answer a contact request?

Usually not. Answering a request generally rests on pre-contract steps or legitimate interest under Article 6(1)(b) or (f). You need separate consent when you also want to use the data for marketing.

Can the marketing checkbox be ticked by default?

No. Recital 32 of the GDPR says pre-ticked boxes don’t constitute consent. Keep the box unticked and separate from the request itself.

How long can I keep contact form data?

The GDPR sets no fixed period. You define a reasonable period per purpose, document it and actually delete the data when it expires.

Does a short form hurt lead quality?

Not necessarily. Ask only what you need to respond, and qualify further in the conversation. Optional fields let keen visitors share more.

The short summary

A GDPR compliant contact form asks only for what’s needed and has a defensible legal basis.

It separates answering a request from marketing consent, refers visibly to your privacy statement and keeps data no longer than a period you actually enforce.

No single checkbox solves that: it’s the combination. The good news is that those same choices make your form convert better.

Want your contact forms and lead flow set up to be privacy friendly and conversion focused? Contact us and we’ll review your current form first.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.