Enquiry forms and UK GDPR: what a B2B website needs

A business-to-business enquiry form usually collects personal data. A person’s name with a work email address or direct line identifies them, so the UK GDPR applies even when the enquiry comes from a company. In practice that means asking only what you need, telling people at the form how you’ll use their details, choosing a lawful basis, knowing which services handle each enquiry, keeping files secure, deleting on a schedule and keeping marketing separate.

This guide is general information, not legal advice. If you’re unsure what applies to your business, check with an adviser.

Key takeaways

  • A name with a work email address is personal data. Information about a limited company on its own isn’t.
  • Ask only what you need to reply or quote, and put a short privacy line with a link next to the send button.
  • Where the enquirer works for a client company, the contract basis may not fit, because any contract would be with their employer. In our view, legitimate interests often fits better.
  • Know every service an enquiry passes through, and have a written contract with each one that processes it for you.
  • Set how long you keep enquiries, delete them on schedule, and keep any mailing list sign-up separate.
  • Since 19 June 2026, your privacy information must also tell people they can complain to you.

Is a B2B enquiry personal data?

Article 4 of the UK GDPR defines personal data as “any information relating to an identified or identifiable natural person”. Its examples of identifiers include “a name” and “an online identifier”.

Guidance from the ICO (the UK’s data protection regulator; since 30 September 2026 its legal name is the Information Commission) is direct about business contacts: “A name and a corporate email address clearly relates to a particular individual and is therefore personal data.” The same ICO page says information about “a limited company or another legal entity” is not personal data, but that the UK GDPR applies to “individuals acting as sole traders, employees, partners, and company directors wherever they are individually identifiable”.

So on a typical B2B form:

  • Personal data: the enquirer’s name, work email address, direct phone number, job title, and anything in the message about them.
  • Usually not personal data: the company’s name and registered details, a general address that doesn’t name anyone, and a description of the project.
  • Check the attachments: drawings and specifications often carry names, signatures and, on residential work, home addresses.

Many of the ICO pages quoted in this guide carry a note that they are “under review” after the Data (Use and Access) Act 2025, so check them again before you rely on a detail.

What should a B2B enquiry form ask?

Article 5 says personal data must be “adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed”. This is the data minimisation principle. The ICO adds: “You must not collect personal data on the off-chance that it might be useful in the future.”

For a quote request, that points to a short form. We designed and built the website for V&H Construction Group, a cladding company based in Dartford. Its form “asks for the type of work, where the project is and what it involves, with a name, a company and an email address or phone number to reply to.”

Field Our suggestion
Name and company Required
Work email or phone One required, the other optional
Type of work Required, from a short list
Project location A town or postcode area, if it affects whether you quote
Timescale or tender return date Only if it changes your reply
Drawings or files Optional, with type and size limits
Job title, how they found you Optional, never required
Home address, date of birth, personal mobile Leave off

A useful test, which is not a legal one: for each field, would you reply differently without it? If not, leave it off or make it optional. Our B2B website checklist covers what a quote form needs to capture for the work itself.

Which lawful basis applies?

Article 6 lists the lawful bases. Two usually come up for enquiry forms:

  • Contract, Article 6(1)(b): processing “necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract”. The ICO’s example of such a step is a request to “provide a quote”.
  • Legitimate interests, Article 6(1)(f): processing “necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject”.

The catch for B2B is who the contract would be with. The ICO’s guidance on the contract basis says “It does not apply if you need to process one person’s details but the contract is with someone else.” When an estimator at a main contractor asks for a price, any contract would usually be with the main contractor, not the estimator. In our view, legitimate interests is often the better fit there, while the contract basis can fit a sole trader asking for a quote for their own business.

Legitimate interests needs what the ICO calls a “three-part test”: a purpose test, a necessity test and a balancing test. It says “You should do this test before you start using the personal information”, and that you should record the outcome. In our view, for replying to an enquiry someone chose to send you, that record can be short. Whichever basis you choose, name it in your privacy notice.

The privacy line by the form

Article 13 says that when you collect personal data from the person, you must give them certain information “at the time when personal data are obtained”. The ICO puts it plainly: “You must provide privacy information to individuals at the time you collect their personal data from them.” It says this information “must be concise, transparent, intelligible, easily accessible, and it must use clear and plain language”, and that layering and “just-in-time notices” can help.

A practical way to do both is one line next to the send button, linked to a full privacy notice. For example, in our own wording, to adapt: We’ll use these details to reply to your enquiry and delete them after [period]. Our privacy notice explains who handles them and your rights.

For an enquiry form, Article 13 means the full notice should cover, among other things:

  • who you are and how to contact you;
  • why you use enquiry details and on what lawful basis, and if it’s legitimate interests, what those interests are;
  • “the recipients or categories of recipients of the personal data”, such as your email provider, form service or CRM;
  • whether you intend “to transfer personal data to a third country”, meaning outside the UK;
  • how long you keep enquiries;
  • people’s rights, such as access, erasure and objection;
  • their right to complain to you, and to the ICO.

The right to complain to you is new. The Data (Use and Access) Act 2025 added to Article 13 “the right to make a complaint to the controller under section 164A of the 2018 Act”, in force since 19 June 2026. The ICO’s complaints guidance says “You must tell people they can complain to you, as well as to us”, including at the point you collect their information. If your privacy notice is older than that, check it. Our guide to privacy policies and cookie banners covers the rest of the notice.

Where enquiries go, and who handles them

An enquiry rarely stays in one place. It may be emailed to a shared inbox, stored in the website’s dashboard, copied into a CRM, and pass through a form service or a spam check on the way. Map it before you write your privacy notice:

Where it goes Who handles it
Email inbox Your email provider
Website dashboard Your website host
A form run on another company’s system That company
CRM or quoting software Its provider
A spam check run by another company That company

Many of these act as processors, which the UK GDPR defines as a body “which processes personal data on behalf of the controller”. Article 28 says you must “use only processors providing sufficient guarantees to implement appropriate technical and organisational measures”, that their processing must be governed by a contract or other legal act that binds them, and that this “shall be in writing, including in electronic form”. Find each provider’s data processing terms and keep a copy. If a service also uses the data for its own purposes, read its terms closely and say so in your privacy notice.

On the V&H site, “Each enquiry goes to the company by email and is saved in the dashboard, then deleted after 12 months.” The case study adds: “Enquiries arrive by email and wait in the dashboard too, so nothing depends on one inbox.” A second copy helps if an inbox fails. In our view it also means two places to secure, search and clear, so a few habits help:

  • Send enquiries to a role address on your own domain, not to someone’s personal email.
  • Don’t auto-forward them to personal accounts.
  • Give dashboard access only to the people who answer enquiries, and remove it when they leave.

File uploads, drawings and security

B2B forms often take drawings, specifications or tender packs. We designed and built the websites for Express Group and Express Facades. On the Express Group tender form, “Drawings upload as PDF, DWG, DXF, IFC or ZIP files”, as the Express case study explains.

Article 32 requires “appropriate technical and organisational measures to ensure a level of security appropriate to the risk”. The ICO’s security guidance lists “the security of your website and any other online service or application that you use” among the things to consider, and says “A good starting point is to make sure that you’re in line with the requirements of Cyber Essentials”.

For uploads, our suggestions, which are not legal tests:

  • Accept only the file types you need, with a size limit.
  • Keep uploaded files out of public view, so nobody can open them by guessing a web address.
  • Limit who can open them, and remove access when people leave.
  • Delete uploads with the enquiry, on the same schedule.
  • Keep the website and its form software up to date.

Our guide to website security for businesses covers the wider picture.

How long should you keep enquiries?

Article 5 says personal data must be kept “for no longer than is necessary for the purposes for which the personal data are processed”. The ICO’s storage limitation guidance says “The UK GDPR does not set specific time limits for different types of data”, that you “should not keep data indefinitely ‘just in case’”, and that you need “a policy setting standard retention periods wherever possible”.

A workable approach, in our view:

  • Enquiries that go nowhere: choose a period that covers a realistic follow-up, then delete. V&H’s enquiries are deleted after 12 months; that is the company’s choice, not a legal rule.
  • Enquiries that become work: move what you need into the job file, where your normal records periods apply, and delete the form copy.
  • Every copy: the inbox, the dashboard, the CRM and any downloaded attachments. Automatic deletion in the dashboard doesn’t clear the inbox.

Put the period in your privacy notice: Article 13 asks for “the period for which the personal data will be stored, or if that is not possible, the criteria used to determine that period”.

Adding enquirers to a mailing list

Replying to an enquiry isn’t marketing. Adding the person to your newsletter is, and two sets of rules apply:

  • PECR. Regulation 22 of the Privacy and Electronic Communications Regulations covers marketing by electronic mail “to individual subscribers”. The ICO’s business-to-business marketing guidance says companies, limited liability partnerships and Scottish partnerships are corporate subscribers, while sole traders and some other partnerships are individual subscribers, and “PECR treats them the same as individuals”.
  • UK GDPR. The same page says: “If you collect an individual’s contact details in their business capacity and you intend to send them direct marketing messages, you must tell them about this and have a lawful basis under the UK GDPR for the processing.”

On the form, our suggestion is to keep it separate: an unticked box, or a separate sign-up, worded for exactly what you’ll send, and never a condition of sending the enquiry.

Spam protection that sets cookies or calls another company

Spam checks broadly come in two kinds: ones that run on your own website, and services run by another company that the visitor’s browser contacts. The second kind raises two questions.

Cookies and device storage. Regulation 6 of PECR says “a person must not store information, or gain access to information stored, in the terminal equipment of a subscriber or user”, subject to the exceptions in its Schedule A1. One exception covers storage or access “strictly necessary for the provision of an information society service requested by the subscriber or user”, with examples that include “to prevent or detect fraud in connection with the provision of the service requested”. Whether a particular spam tool fits that exception isn’t something these sources settle. Our guide to adding a contact form sets out what the ICO’s cookie guidance says.

Data going to another company. A check that runs on another company’s servers receives at least the visitor’s IP address when the browser contacts it, and the UK GDPR lists “an online identifier” among the things that can identify a person. Name the service in your privacy notice and read its terms.

The V&H form “keeps spam out with hidden checks and a sending limit, with no outside service”, and “sets no cookies”. In our view, checks like these that run on your own site are the simplest route, and they don’t ask anyone to solve a puzzle.

Access requests and complaints

Anyone who has sent you an enquiry can ask for a copy of their data. The ICO’s guide to subject access says people “can make SARs verbally or in writing, including via social media”, and “You must respond without undue delay, and within one month of receipt of the request.” Keeping enquiries in a known set of places, with a deletion date, makes the search easier.

Complaints are newer. Section 164A of the Data Protection Act 2018, in force since 19 June 2026, says a controller “must facilitate the making of complaints under this section by taking steps such as providing a complaint form which can be completed electronically and by other means”. It must acknowledge a complaint “within the period of 30 days beginning when the complaint is received”. The ICO says “You’re not required to set up a separate tool for receiving complaints”, and its examples include a complaint form, an email address and a phone line. In our view an existing contact route can do the job, if your privacy notice explains it and someone knows what to do when a complaint arrives.

Common questions

Do we need a privacy notice if we only deal with companies?
If your form collects people’s names and work email addresses, yes. The ICO treats a name and a corporate email address as personal data, and Article 13 requires privacy information when you collect it.

Do we need consent to reply to an enquiry?
In our view, usually not: the person asked you to reply. Contract can fit a sole trader asking for a quote, and legitimate interests often fits staff of client companies. A consent box for the reply itself can confuse people about what they’re agreeing to.

Can we keep old enquiries in case they come back?
Not indefinitely. The ICO says you “should not keep data indefinitely ‘just in case’”. Set a period and delete on schedule.

Do we have to pay the ICO a fee?
Possibly. The ICO’s fee guidance says “Not all controllers must pay a fee. Many can rely on an exemption.” It also has an online self-assessment to help you work out which fee applies.

What if the drawings name other people?
Names of architects, engineers or homeowners in a drawing are usually personal data too. Handle them the same way: secure storage, limited access and deletion on schedule.

Free help

If you’d like help with your enquiry form

We’re Hintling Studio, an independent web design studio registered in London. We build websites for established businesses across the UK.

Every package includes a contact form and a booking-request or quote-request form, so buyers can tell you what they need before you price it. See our work and what’s in each package, or tell us about your business.

Sources checked on 18 November 2026: legislation.gov.uk and the ICO. Hintling Studio is not connected with the ICO (Information Commission), legislation.gov.uk or the Cyber Essentials scheme.

Is your website working for you?

A one-page checklist to score your website in about ten minutes. No sign-up and no email needed: just download it.

Preview of the one-page Is your website working for you? checklist

Let’s build yours.

Send us a short brief and we’ll reply with a fixed quote and a timeline. No calls needed unless you want one.