Nov 16, 2026 · CloudMount editorial
AI and Personal Data: Build the GDPR Case Before Launch

For Irish businesses, an AI deployment needs more than a supplier’s compliance assurance. Establish the lawful basis, assess risks and explain how personal data will be used before processing begins.
Match the lawful basis to the purpose
Start with the business purpose, not the software. Identify whose personal data enters the system, what the system produces and whether the supplier reuses inputs for its own purposes. Prompts, uploaded documents and AI-generated inferences can all contain personal data.
Choose and document a lawful basis for each processing purpose. Legitimate interests requires a necessity assessment and balancing against individuals’ rights; it is not blanket permission. Contractual necessity means more than convenience. Employee consent is often unsuitable because of the power imbalance. Special-category data, such as health information, requires an additional Article 9 condition.
Use the DPIA to shape the deployment
A data protection impact assessment is required where processing is likely to create a high risk to people’s rights and freedoms. AI does not automatically trigger one, but profiling, sensitive data and decisions affecting access to employment or services warrant careful screening.
Complete any required DPIA before processing starts. Examine necessity, proportionality, accuracy, access controls, retention, supplier arrangements and international transfers. Record safeguards and who owns them. If high residual risk cannot be reduced, consult the Data Protection Commission before proceeding. Revisit the assessment when purposes, data or system behaviour materially change.
Make transparency useful to the person affected
Explain purposes, lawful bases, recipients, retention and rights in clear privacy information. Where GDPR rules on automated decision-making apply, provide meaningful information about the logic involved and the significance and envisaged consequences. A nominal human sign-off is not meaningful oversight.
Practical takeaway: before launch, require a documented lawful-basis assessment, a recorded DPIA screening decision and privacy information that matches the actual data flow. This is general information, not legal advice.
General information only, not legal advice. Regulatory obligations depend on your role, context and the provisions in force.
Want to talk about your compliance?
Book a review