Are AI Bid Writing Tools GDPR Compliant? UK Tender Data Security in 2026

Yes, AI bid writing tools can be UK GDPR compliant. The deciding factors are narrow: where your data is processed, whether your input is used to train the model, and whether the tool has a written Data Processing Agreement (DPA) under UK GDPR and the Data Protection Act 2018. Most purpose-built UK tender tools meet all three. Generic consumer LLMs (the free tier of ChatGPT, the unpaid Claude tier) usually fail at least one.

Procurement Policy Note 017 (live 24 February 2025) adds a fourth layer when the tender is from a UK contracting authority. The buyer is required to put proportionate controls in place to make sure suppliers do not use confidential government tender documents as AI training data. That is a hard line, regardless of which tool you pick.

• AI bid tools can be UK GDPR compliant. The check is the contract, not the technology.
• Three questions decide it: where is data processed, is your input used to train the model, and is there a written UK GDPR Data Processing Agreement (DPA).
• PPN 017 explicitly forbids using confidential contracting authority documents as training data. The rule sits on the buyer's side but applies to your tool choice.
• ISO 27001 certification is increasingly listed as a tender requirement on contracts above £100k. Either the supplier holds it or the AI vendor does.
• Personal data inside a tender response (CVs, staff contact info, named referees) is processed under UK GDPR. Lawful basis is usually 'legitimate interests' for the bid, then erased after award.
• Generic consumer LLMs (free ChatGPT, free Claude) usually retain inputs for training by default. Use the paid Enterprise tier or a purpose-built tender tool with a DPA, or write that section by hand.
• If a buyer is concerned, expect a clarification question on data residency, encryption at rest and in transit, sub-processors, and incident response timelines.

Putting in place proportionate controls to ensure suppliers do not use confidential contracting authority information, or information not already in the public domain as training data for AI systems e.g. using confidential Government tender documents to train AI or Large Language Models (LLMs) to create future tender responses.

PPN 017 (live 24 February 2025)

What's in this guide¶

• The three GDPR checks that decide whether a tool is compliant for tender drafting
• PPN 017 confidentiality rule (verbatim) and what it means for tool choice
• ISO 27001 in tender packs and when it becomes mandatory
• Personal data in tender responses, lawful basis and retention
• ChatGPT free tier vs Enterprise vs purpose-built tender tools, on data handling
• What CleanTender does (in plain buyer-facing language)
• A 7-point procurement checklist before you sign up to any AI bid tool

The three checks that decide GDPR compliance¶

All three need to clear. Two out of three is not GDPR compliance, it is a partial defence. If the AI vendor cannot send you a DPA on request, walk.

The PPN 017 confidentiality rule¶

PPN 017 sits on top of UK GDPR. It is procurement guidance, not data protection law, but it sets a hard line on AI training data when the buyer is a UK central government department, executive agency, or non-departmental public body. The verbatim wording is in the quote box above. The practical translation:

1. If a buyer marks any annex of the tender pack as confidential, you must not paste that document into a public LLM where the input is used to train the foundation model. This is the rule most ChatGPT free-tier users fall foul of.
2. If you use a paid Enterprise LLM (ChatGPT Enterprise, Claude for Enterprise) or a purpose-built tender tool that contractually does not retain inputs for training, the rule is met.
3. The buyer can ask you in clarification to evidence which tool you used and how training data is handled. Be ready to send a one-page response with the tool name, vendor name, DPA reference, and a Yes/No on training-data retention.
4. PPN 017's illustrative example uses video conferencing transcription. The principle generalises: any AI processing of buyer-confidential data needs an explicit written agreement that the data is not used for training purposes.

The full PPN 017 disclosure rules (the three Annex B questions you will be asked, and what disqualifies vs what scores) are in the plain-English PPN 017 guide for cleaning SMEs.

ISO 27001 in tender packs¶

ISO 27001 is the international standard for information security management. UK public buyers list it as a hard requirement on contracts above £100,000 with increasing frequency. NHS Trust and central government tenders almost always ask for it on contracts handling patient data, staff data, or other sensitive categories.

There are two ways to satisfy this on a tender that uses AI bid drafting:

1. You hold ISO 27001 yourself (UKAS-accredited). Most cleaning and FM SMEs do not, and getting certified is a £6k-£15k first-year cost plus surveillance audits.
2. Your AI vendor holds ISO 27001 and you reference their certificate in your bid. Most purpose-built B2B tender tools have ISO 27001 (or SOC 2 Type II as a US-equivalent that UK buyers usually accept). Generic consumer LLMs in their free tier usually do not.

If the buyer asks for ISO 27001 and you do not hold it, ask them whether the certification of the underlying AI vendor satisfies the requirement. Most do, in our experience, especially for cleaning and FM contracts where the bidder's own systems are not the primary data store.

Personal data inside tender responses¶

A typical UK soft FM tender response contains personal data. Named directors with their CVs. Site supervisor qualifications. Two named referees with phone numbers and email addresses. Sometimes payslip data for TUPE liability calculation. All of this is personal data under UK GDPR and the Data Protection Act 2018.

When you use an AI tool to draft any of these sections, you are processing personal data. The AI vendor becomes a Data Processor under Article 28. That is why the DPA is non-negotiable. Without one, you are passing personal data to a processor with no contractual safeguards, which is itself a UK GDPR breach.

Free LLM vs Enterprise vs purpose-built tender tool¶

The cheapest defensible path for a UK soft FM SME doing 6+ bids a year is a purpose-built tool. Enterprise consumer LLMs cost the same or more once you add per-seat licensing. Free consumer LLMs are out for any bid touching confidential buyer information.

A 7-point procurement checklist before you sign up¶

1. Ask the AI vendor for their UK GDPR Data Processing Agreement. If they cannot send one in 24 hours, walk.
2. Confirm in writing that customer input is not used to train the model. Get this in the DPA, not just on a marketing page.
3. Confirm data residency. UK or EEA processing is the cleanest answer. If it is US, ask for the Standard Contractual Clauses or UK Extension to the EU-US Data Privacy Framework.
4. Ask whether the vendor holds ISO 27001 (or SOC 2 Type II). Get the certificate number and verify on the UKAS register or the vendor's audit portal.
5. Ask for the list of sub-processors. Cloud hosting, email delivery, analytics. Each one is a sub-processor and needs to be in the DPA.
6. Ask about incident response. What is the notification timeline if there is a personal data breach? UK GDPR sets the buyer's clock at 72 hours; your vendor should be tighter than that.
7. Test by uploading a non-confidential sample first. Confirm the output behaves the way the marketing page says. If a vendor refuses a free trial or sample interaction, that is a signal.

What to do this week¶

1. Check whatever AI tool you currently use against the 7-point checklist. If you are using a free consumer LLM, that is the gap to close first.
2. Request a UK GDPR DPA from your AI vendor. Read the training-data clause and the sub-processor list before signing.
3. Audit your last three submitted tender responses for personal data exposure. Were referees consent-confirmed? Were CVs anonymised where possible?
4. If a buyer has asked or might ask about ISO 27001, find your AI vendor's certificate (or note that you do not have one) and write a one-paragraph answer ready for the next clarification.
5. Pre-write your three PPN 017 Annex B disclosure answers (covered separately) so you have them ready alongside your data handling answer.