In this article9 sections
  1. Two rulebooks, one AI system
  2. GDPR-proof AI: what it actually means
  3. What each regulation actually governs
  4. Where the obligations genuinely overlap
  5. The DPIA and FRIA: two assessments, one shortcut
  6. Three high-stakes scenarios for SMEs
  7. Building a unified compliance approach
  8. Your next practical step
  9. References

Two rulebooks, one AI system

The eu ai act vs gdpr question is not academic. If your company uses an AI tool that processes employee data, customer profiles, or automated decisions, both regulations apply at the same time, right now. The GDPR has been enforceable since 2018. The AI Act entered into force on 1 August 2024. AI literacy (Article 4) and the prohibited practices have applied since 2 February 2025, the Act applies in general, including the transparency rules, from 2 August 2026, and the high-risk deployer framework follows on 2 December 2027 for Annex III systems. You cannot pick one and ignore the other.

Understanding where they overlap, and where they diverge, is the fastest way to avoid duplicating work or, worse, assuming one regulation covers what only the other addresses.

GDPR-proof AI: what it actually means

GDPR-proof AI is an AI system whose data flows, model training, and outputs demonstrably comply with the GDPR. In practice: for every piece of personal data the system touches, you can show the lawful basis it relies on, where the data goes, and how the output was produced. A GDPR-proof AI solution isn't a tool with a badge — it's a system where the whole chain, from input to output, is traceably compliant.

GDPR-compliant AI solutions: 5 requirements

A GDPR-compliant AI solution meets five concrete requirements:

  1. Lawful basis — every processing of personal data by the AI system has a documented GDPR basis (consent, legitimate interest, or a legal obligation).

  2. Data minimisation — the system only receives the personal data it strictly needs. Anonymise or pseudonymise wherever you can, especially in training and prompts.

  3. DPIA obligation — for AI that is high-risk to individuals (profiling, automated decisions), a Data Protection Impact Assessment is required before go-live.

  4. Sub-processor agreements with model providers — contractually lock in that the model provider and its sub-processors won't use your data for training and stay within GDPR limits.

  5. Right to explanation for automated decision-making — for decisions with legal effect, you must be able to explain how the AI reached its output, with human oversight as a backstop.

Making AI GDPR-compliant starts here — not with the technology, but with demonstrability. A GDPR-proof AI solution that covers these five points doesn't just survive a data-protection audit; it lays the groundwork for your EU AI Act compliance too, because both regimes overlap exactly here.

What each regulation actually governs

The GDPR governs how personal data is collected, stored, shared, and used. It applies whenever you process information that can identify a natural person. The legal basis sits in Article 6 GDPR, and special-category data triggers the stricter requirements of Article 9.

The AI Act governs AI systems themselves: how they are designed, tested, documented, and deployed. It applies regardless of whether personal data is involved. A pricing algorithm that never touches names still falls under the Act if it meets the definition of an AI system under Article 3, even if the only duty that follows is Article 4 AI literacy. A recruitment screening tool that ranks CVs is a high-risk AI system under Annex III, which triggers a full set of deployer obligations from 2 December 2027.

The short version: GDPR protects people's data. The AI Act protects people from AI. Most real-world deployments require both.

Where the obligations genuinely overlap

Lawful basis and purpose limitation. Under GDPR, you need a lawful basis before processing personal data. Under the AI Act, deployers of high-risk systems must use them in accordance with the provider's instructions for use (Article 26, from 2 December 2027 for Annex III systems). If you use a candidate-screening tool for employee performance monitoring, you are likely breaching GDPR's purpose limitation principle today, and the instructions-for-use duty once it applies.

Transparency and information obligations. GDPR Article 13 and 14 require you to tell data subjects how their data is used. AI Act Article 50, applicable since 2 August 2026, splits transparency by role: providers must design chatbots so people know they are dealing with AI and must mark synthetic content; deployers must disclose deepfakes and AI-generated text published to inform the public on matters of public interest. Separately, deployers of high-risk systems that make or assist decisions about people must inform those people (Article 26, from 2 December 2027). In practice, your privacy notice and your AI transparency statement need to align. They often do not.

Automated decision-making. GDPR Article 22 gives individuals the right not to be subject to solely automated decisions that produce legal or similarly significant effects. The AI Act classifies many of these same systems as high-risk under Annex III: providers must build in human oversight, logging and robustness, and deployers must assign competent human oversight and keep the logs (from 2 December 2027). Complying with one does not automatically satisfy the other. You need a human review process that is real, documented, and traceable.

Data subject rights vs. AI Act rights. GDPR grants rights to access, rectification, erasure, and objection. The AI Act grants a separate right in Article 86 to a clear and meaningful explanation of the role a high-risk AI system played in a decision taken by the deployer, to the extent other Union law does not already provide it. Since it is tied to high-risk systems, plan for it by 2 December 2027 at the latest. Both rights can be triggered by the same person about the same decision. You need a single workflow that can respond to both.

The DPIA and FRIA: two assessments, one shortcut

This is where compliance workload stacks up fast. The GDPR requires a Data Protection Impact Assessment (DPIA) under Article 35 when processing is likely to result in high risk to individuals. The AI Act requires a Fundamental Rights Impact Assessment (FRIA) under Article 27 only from a specific group of deployers of high-risk AI systems: bodies governed by public law, private entities providing public services, and deployers of AI for creditworthiness of natural persons or for life and health insurance pricing. It applies from 2 December 2027.

They sound similar because they are similar. Both require you to map the system, identify affected people, assess risks, and document mitigations. The FRIA is broader: it requires you to describe the categories of people and groups likely to be affected and the specific risks of harm to them, across fundamental rights such as non-discrimination, not only data protection.

Here is the practical shortcut. Article 27(4) of the AI Act, as amended by Regulation (EU) 2026/1744, says that where a FRIA obligation is already met through a DPIA, the deployer may include cross-references to the relevant sections of that DPIA, or include relevant parts of it, in the FRIA. The AI Office is also developing a questionnaire template to simplify the FRIA (Article 27(5)). This is not a loophole. It is a designed efficiency for organisations that have already invested in rigorous DPIAs.

To get the most out of it, your DPIA should already:

  • Identify affected individuals beyond just data subjects (e.g., third parties affected by a decision)

  • Assess risks to rights beyond data protection, including non-discrimination

  • Document human oversight mechanisms

  • Reference the specific AI system and its intended use case

If your current DPIAs are narrow, data-centric documents that stop at "risk to personal data", they will not carry over. You will need to expand them. But the expansion is far less work than starting a FRIA from scratch.

Three high-stakes scenarios for SMEs

HR and recruitment AI. CV screening tools, psychometric AI, and interview analysis software all land in Annex III as high-risk systems. Interview software that infers candidates' emotions goes further: that is prohibited under Article 5(1)(f). You have GDPR obligations now (lawful basis, a valid exception for any special-category data, Article 22 safeguards, usually a DPIA) and AI Act obligations (Article 4 now; Article 26 deployer duties, including human oversight and informing workers, from 2 December 2027). A private employer does not need a FRIA. The Dutch Autoriteit Persoonsgegevens supervises the GDPR today and is the intended supervisor for most AI Act topics, but it only gets AI Act powers once the Dutch implementing law is in force.

Credit and financial risk scoring. Any AI system that evaluates the creditworthiness of natural persons is Annex III high-risk (fraud detection excepted). GDPR Article 22 applies to automated credit decisions. The AI Act adds provider requirements on documentation, logging and accuracy, deployer duties, and a FRIA for the lender, all from 2 December 2027. Fines for breaches of deployer obligations run up to €15 million or 3% of global annual turnover under Article 99, with the lower figure as the maximum for SMEs; GDPR fines reach €20 million or 4% of global turnover. Supervisors under both regimes can look at the same incident.

Customer profiling and personalisation. Profiling under GDPR requires transparency and, for sensitive categories, explicit consent. AI Act rules on prohibited practices under Article 5 ban manipulative or deceptive techniques that materially distort behaviour and cause significant harm, and the exploitation of vulnerabilities due to age, disability or a specific social or economic situation with the same effect. If your personalisation engine exploits people's economic hardship to push them into harmful decisions, you may be in prohibited-practice territory regardless of whether you have a lawful basis under GDPR.

Building a unified compliance approach

The most efficient path for an SME is a single AI inventory that flags both GDPR and AI Act triggers simultaneously. For each AI system in use, record:

  1. Does it process personal data? (GDPR trigger)

  2. Does it meet the AI system definition under Article 3? (AI Act trigger)

  3. Is it Annex III high-risk? (escalated AI Act obligations)

  4. Does it make automated decisions with legal effect? (GDPR Article 22, plus AI Act Article 26 if high-risk)

  5. If you need a FRIA, is a DPIA already in place that it can cross-reference?

This five-question triage takes under an hour per system. It tells you immediately where you have gaps and where existing documentation can be repurposed.

Run your AI literacy measures under Article 4 alongside your staff data protection training, and keep a record of both. One training cycle, two frameworks covered.

The regulations are designed to coexist. The EU Commission's guidance on the AI Act confirms that the AI Act does not replace sector-specific legislation including GDPR; it layers on top. Treat them as a system, not as competing checklists.

🇳🇱 Liever in het Nederlands? Lees AVG en AI-verordening: zo werken ze samen voor Nederlandse deployers.

Your next practical step

Start with the inventory. List every AI tool your organisation uses, apply the five questions above to each one, and identify which need a DPIA and, for the few organisations in scope, a FRIA. That single exercise will surface your highest-risk exposure points and show you where the Article 27(4) shortcut applies.

If you want a structured starting point, run the free 2-minute compliance check at comply.khairos.ai. It maps your current AI tools against both the GDPR and AI Act frameworks and tells you where your gaps are.

References

  1. EU AI Act Article 3 – Definitions

  2. EU AI Act Article 26 – Deployer obligations

  3. EU AI Act Article 27 – Fundamental Rights Impact Assessment

  4. EU AI Act Article 50 – Transparency obligations

  5. EU AI Act Article 86 – Right to explanation

  6. EU AI Act Article 99 – Penalties

  7. EU AI Act Article 5 – Prohibited practices

  8. EU AI Act Annex III – High-risk AI systems

  9. EU AI Act Article 4 – AI literacy

  10. GDPR full text – EUR-Lex

  11. European Commission – AI regulatory framework

Not sure where your company stands?

Answer 15 questions about how your team uses AI. You get a compliance score and the gaps to close first, as a PDF.

Am I compliant? Check in 2 minHow Khairos Comply works