# AI and data protection under UK GDPR and the Data Protection (Jersey) Law 2018

Published 24 February 2026 by Spark · Governance and compliance · 5 min read
Canonical: https://hellospark.co.uk/writing/ai-data-protection-uk-gdpr-jersey

> Feeding client data to an AI tool is still processing personal data, and the same rules apply. Lawful basis, minimisation, and knowing where your prompts go. Here is what UK GDPR and the Jersey Law actually require.

Feeding client data into an AI tool is processing personal data, and every rule you already follow still applies. UK GDPR and the Data Protection (Jersey) Law 2018 do not have an AI exemption. If anything, AI raises the stakes, because you are often sending personal data to a third party, sometimes offshore, and getting back an output whose basis you may struggle to explain. The obligations are familiar. The failure modes are new.

The good news is that the two regimes are closely aligned. The Jersey Law tracks the GDPR structure deliberately, so a control built for one generally satisfies the other. You are not running two data protection projects. You are running one, applied carefully to a new kind of processing.

## Lawful basis comes first

Before you put personal data through an AI system, you need a lawful basis for that processing, and it has to cover the AI use specifically. Consent gathered for onboarding does not automatically extend to feeding the same data to a model for a purpose the client never saw. Where you rely on legitimate interests, do the balancing exercise properly and write it down. If the data is special category, the bar is higher again.

The question to answer, in one line, is: on what basis are we allowed to process this person’s data through this tool, for this purpose? If the honest answer is ‘we hadn’t thought about it that way’, stop and think about it before the data leaves your building.

## Data minimisation, applied to prompts

The habit that gets firms into trouble is oversharing with the model. It is tempting to paste an entire client file into a prompt because it is easy. Minimisation says send only what the task needs. If a summary requires three fields, do not send thirty. If a name is irrelevant to the analysis, redact it. Every extra field in a prompt is personal data you have exported, often to a system you do not control.

In practice this is a design decision, not a discipline you can rely on staff to remember under time pressure. Build the workflow so it only ever passes the minimum, and minimisation stops being a rule people break and becomes a property of the system.

## Where do your prompts and outputs actually go

This is the question most firms cannot answer, and the one a regulator will ask. When someone types into an AI tool, where does that text travel, where is it stored, for how long, and is it used to train the vendor’s models? The answers vary enormously between a consumer chatbot and an enterprise deployment with a data processing agreement and training switched off.

- **Residency.** Where is the data physically processed and stored? Transfers out of the UK or Jersey need a lawful transfer mechanism, and ‘the server is somewhere in the US’ is not one.
- **Retention.** How long does the vendor keep prompts and outputs, and can you delete them? Indefinite retention of client data by a third party is a problem you own.
- **Training.** Is your data used to improve the vendor’s models? For client data, the answer needs to be no, and you need it in writing.
- **Sub-processors.** Who else touches the data downstream? Your obligations follow the data even when a vendor hands it on.

## Vendor and contract questions

Where an AI vendor processes personal data on your behalf, they are your processor, and you need the same contractual controls you would demand of any material outsourcing. A data processing agreement, clear purpose limits, security commitments, breach notification, and the right to audit. The convenience of signing up with a corporate card does not remove the obligation to have the paperwork a supervisor expects.

Treat consumer-grade AI tools with particular care. The free tier that trains on your inputs is not somewhere client data should go, however useful it feels. Pick tools that offer an enterprise footing with the controls in writing, and reserve the consumer versions for non-personal, non-confidential work.

## DPIAs for high-risk use

Where an AI use is likely to result in a high risk to people’s rights, a Data Protection Impact Assessment is not optional, it is expected. That covers profiling, automated decisions with legal or similarly significant effects, and large-scale processing of sensitive data. The DPIA is where you set out what the system does, what could go wrong, and the controls that bring the risk down to acceptable.

Done well, a DPIA is not a hoop. It is the same thinking as a good AI risk assessment, written in the language a data protection regulator reads. Much of the evidence it needs, what the system does, who oversees it, what is logged, comes straight from your [AI audit trail](/writing/building-an-ai-audit-trail). Build the trail and the DPIA half writes itself.

Getting this right across a firm’s AI use is typically a four to six week piece of work. One caveat, stated plainly: this is our practical read, not legal advice, and you should check specific points against the primary legislation and your regulator’s guidance before you rely on them.

If you want a candid view of where your client data actually goes when your team uses AI, [book a review](/book-a-review). We will trace one live workflow end to end, flag the data protection gaps, and put a number on the fix. No deck, no hype.
