AI and GDPR
A practical view of data protection obligations when AI processes personal data in enterprise environments.
GDPR applies to AI when personal data is processed; the presence of a model does not create an exemption or a completely separate legal regime. Purpose, lawful basis, minimisation, transparency and rights still matter.
AI systems can copy personal information into prompts, embeddings, logs and outputs. Understanding every processing stage is essential for privacy engineering and supplier assessment.
Map the data flow before debating the model. Most compliance questions become clearer when sources, purposes, recipients and retention are explicit.
There is rarely one universally correct architecture. The best decision is the one that fits the process, risk, people and operating capability of the organisation.
Why it matters
AI systems can copy personal information into prompts, embeddings, logs and outputs. Understanding every processing stage is essential for privacy engineering and supplier assessment.
In practice, value appears when the technology becomes part of a governed process: responsibilities are clear, evidence can be checked and the organisation can observe whether outcomes improve.
What it really means
GDPR applies to AI when personal data is processed; the presence of a model does not create an exemption or a completely separate legal regime. Purpose, lawful basis, minimisation, transparency and rights still matter.
The useful distinction is between a technical capability and a production service. Enterprise use requires identity, permissions, data handling, evaluation, monitoring and a clear owner for the result.
How it works in practice
The flow can be described in five steps. Each one needs an explicit purpose, an owner and a way to verify that it behaves as expected.
The exact architecture will vary. What matters is keeping the boundaries visible and making failures diagnosable rather than hiding them behind a fluent answer.
What this looks like in real work
An HR assistant answers policy questions without using employee records. A separate, tightly controlled workflow handles individual cases and records the legal basis, access and retention requirements.
The lesson is not that AI produced an answer. It is that the answer appears inside a controlled process, can be verified and is tied to a measurable outcome.
Common mistakes we see
Treating all embeddings as anonymous
Representations may still relate to identifiable individuals and require protection.
Sending data before supplier review
Contracts, sub-processors and international transfers need assessment.
Collecting prompts indefinitely
Operational value must be balanced with retention and purpose limitation.
Using disclaimers instead of design
Privacy needs technical and organisational controls, not only user notices.
When it makes sense
- The process has a clear owner and outcome
- The required information and permissions are understood
- Results can be checked or measured
- The organisation can operate the capability responsibly
When it probably does not
- The problem is still undefined
- A deterministic rule would be simpler and safer
- No one owns data quality or exceptions
- The consequence of failure cannot be controlled
Not using AI can be the right decision. Honest scope is usually more valuable than a technically impressive pilot without a real problem.
How we usually approach it
We work from engineering and operational experience. We do not believe in a universal recipe, but we consistently ask the same questions before building:
Once these answers are reasonably clear, choosing models, infrastructure and integration becomes much easier.
Useful enterprise AI is not defined by how impressive the demo looks, but by how reliably it improves a real process.
Technology evolves quickly and we do not claim to have final answers. These guides capture what we have learned while building and operating platforms, shared with the humility that tomorrow may require a better approach.