AI Demystified

GDPR and AI: a practical guide for non-technical leaders

Practical Secure AI · 26 May 2026 · 7 min read

If you run a business in a regulated or data-sensitive sector, the question is not “is AI allowed?” It is “how do we use it lawfully and prove we did?” You do not need to be a lawyer or an engineer to get this right. You need to ask a short list of clear questions and insist on clear answers.

1. What is our lawful basis?

Under UK GDPR, every use of personal data needs a lawful basis. For most business AI, that is legitimate interests or contract. The point is not the legal label, it is that you can name it and justify it. If a vendor cannot tell you the lawful basis for what their tool does with your data, that is a red flag.

2. Where does the data go, and where does it stay?

When your data goes into an AI system, where does it physically sit, and who can reach it? Reputable secure AI keeps data inside the UK and EU and is explicit about it. Watch for tools that quietly ship data to third countries or use your inputs to train someone else’s model.

3. Are we minimising what the AI sees?

Data minimisation is one of the strongest and most overlooked protections. The less personal data the AI processes, the smaller your risk. A good build strips or masks what is not needed before the model ever sees it.

4. Can we explain a decision?

If your AI influences a decision about a person, you may need to explain it. That means provenance and logging: the system should be able to show what information it used. “The AI just said so” is not an answer you want to give a regulator or an unhappy customer.

5. Can people exercise their rights?

Individuals have rights: access, rectification, erasure and more. Your AI setup needs to support them. If someone asks what data you hold and how it was used, you should be able to answer without a fire drill.

6. Have we done a DPIA where needed?

For higher-risk processing, a Data Protection Impact Assessment is often required. It is not bureaucracy for its own sake. It is a structured way to spot problems before they become incidents, and it is exactly the document that shows you took data protection seriously.

The reassuring part

None of this stops you using AI. It shapes how. Teams that ask these six questions early move faster, because they are not constantly stopping to firefight. Teams that skip them tend to get a long way into a project before discovering they have to start again.

If you want help working through these questions for a specific use case, that is exactly what a discovery call is for.

Sources

  1. Guidance on AI and data protection — Information Commissioner's Office, 2025
  2. A guide to lawful basis — Information Commissioner's Office, 2025

Related reading

Want this for your business?

Book a free discovery call and we will map a practical, secure first AI project for your industry.

Book a discovery call