CNIL published first set of guidelines for developing privacy-friendly AI systems

 
 

Exciting developments from CNIL - Commission Nationale de l'Informatique et des Libertés:

The guidelines demonstrate that the principles of the General Data Protection Regulation (GDPR) can be applied effectively to AI, making innovation and responsibility go hand in hand.

Key insights include:

  1. AI systems can have a general purpose, even if future applications aren't fully defined during the training stage. No necessary conflict with the purpose limitation principle.

  2. Large datasets can fuel AI training, but unnecessary personal data should be avoided. Data minimisation and AI do not necessary contradict.

  3. Long-term retention of training data is acceptable, if justified.

  4. Re-use of datasets, including publicly available data, is permissible under certain conditions.

This publication affirms that privacy issues can coexist with AI development, paving the way for ethical AI tools that align with European privacy values.

For businesses using AI, this underlines the importance of a robust AI compliance program. Such a program can provide legal certainty, facilitate navigation through complex AI development, and help build public trust in AI technologies.

However, it's crucial to be aware that AI presents other legal challenges as well. These include potential issues related to bias and discrimination, intellectual property rights, transparency, accountability, and liability. For instance, using AI may not only violate the GDPR, but also IP and confidentiality rights. And how do we ensure that AI systems make decisions that are transparent and explainable?

These questions additionally emphasize on the need for an AI compliance program that not only ensures privacy and data protection but also addresses the broader spectrum of legal challenges associated with AI use. Feel free to reach out to LR29 if you'd like to chat.

For more details, check out the full article.

 
Next
Next

Use of Open-Source Software in Proprietary Software Products – Part 2